ACPI vs DT at runtime

Grant Likely grant.likely at secretlab.ca
Thu Nov 21 11:00:28 EST 2013


On Fri, 15 Nov 2013 23:21:09 +0000, Russell King - ARM Linux <linux at arm.linux.org.uk> wrote:
> On Fri, Nov 15, 2013 at 08:56:47PM +0100, Arnd Bergmann wrote:
> > On Friday 15 November 2013, Russell King - ARM Linux wrote:
> > > On Fri, Nov 15, 2013 at 09:52:41AM -0800, Olof Johansson wrote:
> > > > If we knew exactly what we wanted, it'd be a different story. _We
> > > > don't_. We're into year FOUR of the device tree conversion and we're just
> > > > now reaching a point where we think we know what a good solution looks
> > > > like. The first two years were easy -- they were the trivial devices we're
> > > > now talking about on ACPI. After that it got harder. Going through all
> > > > of that again with ACPI? No. No way. Microsoft gets to do it and while
> > > > they're busy sorting it out, we'll boot with device tree.
> > > 
> > > However, there's a very big danger here.  I disagree with the stance
> > > you're taking.
> > > 
> > > It seems that under ACPI and DT, we refer to properties by string names.
> > > That's good, but do we really want to have different string names for the
> > > same property.
> > 
> > For all I know, doing this in ACPI is something that is only now being
> > discussed as Intel wants to be able to reuse the existing features from
> > DT enabled drivers in the kernel and share the implementation between
> > embedded x86 SoCs and embedded ARM/PowerPC/MIPS/... SoCs. That part actually
> > isn't as crazy.
> > 
> > The existing ACPI usage however is basically all binary and cannot be
> > shared with DT, in particular it won't help for the orthogonal problem of
> > using ACPI to get "enterprise server" features on ARM64.
> 
> That's strange, because the patches I've seen from people who want to
> add ACPI support to AMBA are all based around very similar strings to
> those in DT to lookup the same data in ACPI.
> 
> What's been done there is the function which reads from DT has been
> duplicated, and instead of reading the information from DT, it reads it
> from ACPI instead using string names without the vendor prefix.

The fact that they are using different strings is a problem though. Push
back on that. As much as possible the property formats between DT and
ACPI should be identical. This is entirely new territory for ACPI and we
have significant influence over it.

g.




More information about the linux-arm-kernel mailing list