[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <EE11001F9E5DDD47B7634E2F8A612F2E1EC17CAC@lhreml503-mbb>
Date: Tue, 22 Dec 2015 09:29:02 +0000
From: Gabriele Paoloni <gabriele.paoloni@...wei.com>
To: Jon Masters <jcm@...hat.com>, Arnd Bergmann <arnd@...db.de>
CC: Tomasz Nowicki <tn@...ihalf.com>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"will.deacon@....com" <will.deacon@....com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>,
"Lorenzo.Pieralisi@....com" <Lorenzo.Pieralisi@....com>,
"okaya@...eaurora.org" <okaya@...eaurora.org>,
"jiang.liu@...ux.intel.com" <jiang.liu@...ux.intel.com>,
"Stefano.Stabellini@...citrix.com" <Stefano.Stabellini@...citrix.com>,
"robert.richter@...iumnetworks.com"
<robert.richter@...iumnetworks.com>,
"mw@...ihalf.com" <mw@...ihalf.com>,
"Liviu.Dudau@....com" <Liviu.Dudau@....com>,
"ddaney@...iumnetworks.com" <ddaney@...iumnetworks.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
Wangyijing <wangyijing@...wei.com>,
"Suravee.Suthikulpanit@....com" <Suravee.Suthikulpanit@....com>,
"msalter@...hat.com" <msalter@...hat.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linaro-acpi@...ts.linaro.org" <linaro-acpi@...ts.linaro.org>,
"jchandra@...adcom.com" <jchandra@...adcom.com>
Subject: RE: [PATCH V2 22/23] pci, acpi: Match PCI config space accessors
against platfrom specific quirks.
Hi Jon, thanks for replying
> -----Original Message-----
> From: Jon Masters [mailto:jcm@...hat.com]
> Sent: 21 December 2015 23:11
> To: Arnd Bergmann
> Cc: Gabriele Paoloni; Tomasz Nowicki; bhelgaas@...gle.com;
> will.deacon@....com; catalin.marinas@....com; rjw@...ysocki.net;
> hanjun.guo@...aro.org; Lorenzo.Pieralisi@....com; okaya@...eaurora.org;
> jiang.liu@...ux.intel.com; Stefano.Stabellini@...citrix.com;
> robert.richter@...iumnetworks.com; mw@...ihalf.com; Liviu.Dudau@....com;
> ddaney@...iumnetworks.com; tglx@...utronix.de; Wangyijing;
> Suravee.Suthikulpanit@....com; msalter@...hat.com; linux-
> pci@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; linux-
> acpi@...r.kernel.org; linux-kernel@...r.kernel.org; linaro-
> acpi@...ts.linaro.org; jchandra@...adcom.com
> Subject: Re: [PATCH V2 22/23] pci, acpi: Match PCI config space
> accessors against platfrom specific quirks.
>
> Sorry for top-posting. A quick note that SMBIOS3 is required by SBBR so
> it can be presumed that compliant platforms will provide quirks via DMI.
Ok so you completely clarified my question 1). Many Thanks for this
Gab
>
> --
> Computer Architect | Sent from my 64-bit #ARM Powered phone
>
> > On Dec 21, 2015, at 09:11, Arnd Bergmann <arnd@...db.de> wrote:
> >
> > On Monday 21 December 2015, Gabriele Paoloni wrote:
> >>> -----Original Message-----
> >>> From: linux-kernel-owner@...r.kernel.org [mailto:linux-kernel-
> >>> owner@...r.kernel.org] On Behalf Of Tomasz Nowicki
> >
> >>> Some platforms may not be fully compliant with generic set of PCI
> >>> config accessors. For these cases we implement the way to overwrite
> >>> accessors set before PCI buses enumeration. Algorithm that
> overwrite
> >>> accessors matches against platform ID (DMI), domain and bus number,
> >>> hopefully enough for all cases. All quirks can be defined using:
> >>> DECLARE_ACPI_MCFG_FIXUP() and keep self contained.
> >>
> >> I've got a couple of comments/questions about this patch..
> >>
> >> 1) So according to this mechanism quirks would be supported only by
> >> vendors whose BIOS are SMBIOS compliant. Now personally I am ok
> >> with this but I don't know if this is OK in general as it would
> >> narrow down the number of platforms that would be able to define
> >> the quirks...
> >> Lorenzo, Arnd what is your opinion here?
> >
> > I'd rather not see the quirks in mainline at all, and only support
> > SBSA compliant machines, or require the BIOS to work around the
> > hardware quirks differently (e.g. by trapping config space access
> > through secure firmware, or going through an AML method to be
> > defined). I'm certainly ok with making it depend on SMBIOS if we are
> going to use something like this.
> >
> > Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists