lkml.org 
[lkml]   [2013]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: ACPI vs Device Tree - moving forward
On Fri, Aug 23, 2013 at 09:45:10PM -0700, Guenter Roeck wrote:

> "What happens when you have an ACPI device that contains an interrupt in
> _CRS and contains a different interrupt in an embedded FDT block?"
>
> Does the situation occur today, ie does it ever happen that one interrupt
> for a device is specified (if that is the correct term) in _CRS and
> another by some other means ?

The only case I can think of is PCI, where we ignored the ACPI-provided
resources until fairly recently. That was a somewhat reasonable thing to
do, since the hardware still had to support pre-ACPI operating systems
and so the non-ACPI information sources were typically correct.

Other than that, I think we always trust the ACPI data.

--
Matthew Garrett | mjg59@srcf.ucam.org


\
 
 \ /
  Last update: 2013-08-24 07:01    [W:0.118 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site