[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201512212342.18960.arnd@arndb.de>
Date: Mon, 21 Dec 2015 23:42:18 +0100
From: Arnd Bergmann <arnd@...db.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: David Daney <ddaney@...iumnetworks.com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
Gabriele Paoloni <gabriele.paoloni@...wei.com>,
"linaro-acpi@...ts.linaro.org" <linaro-acpi@...ts.linaro.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"will.deacon@....com" <will.deacon@....com>,
"okaya@...eaurora.org" <okaya@...eaurora.org>,
Wangyijing <wangyijing@...wei.com>,
"Lorenzo.Pieralisi@....com" <Lorenzo.Pieralisi@....com>,
Tomasz Nowicki <tn@...ihalf.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"robert.richter@...iumnetworks.com"
<robert.richter@...iumnetworks.com>,
"msalter@...hat.com" <msalter@...hat.com>,
"jcm@...hat.com" <jcm@...hat.com>,
"Stefano.Stabellini@...citrix.com" <Stefano.Stabellini@...citrix.com>,
"Liviu.Dudau@....com" <Liviu.Dudau@....com>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mw@...ihalf.com" <mw@...ihalf.com>,
"jchandra@...adcom.com" <jchandra@...adcom.com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>,
"Suravee.Suthikulpanit@....com" <Suravee.Suthikulpanit@....com>,
"jiang.liu@...ux.intel.com" <jiang.liu@...ux.intel.com>
Subject: Re: [PATCH V2 22/23] pci, acpi: Match PCI config space accessors against platfrom specific quirks.
On Monday 21 December 2015, David Daney wrote:
> On 12/21/2015 06:10 AM, Arnd Bergmann wrote:
> > On Monday 21 December 2015, Gabriele Paoloni wrote:
>
> > 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).
>
> Some systems don't seem to have this capability. For example, in ARMv8
> (A.K.A. arm64), I haven't been able to figure out how to trap these
> accesses to EL3 for emulation. The specification is 5700 pages long
> though, so perhaps I missed that bit.
How about using AML then? This would be similar to what CHRP used with
RTAS calls to do PCI config space access.
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