[Ksummit-discuss] [TECH TOPIC] Driver model/resources, ACPI, DT, etc (sigh)

[Rafael J. Wysocki]

On Friday, May 02, 2014 07:02:42 PM Mark Brown wrote:
> 
> --sXc4Kmr5FA7axrvy
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> 
> On Sat, May 03, 2014 at 02:05:21AM +0200, Rafael J. Wysocki wrote:
> > On Friday, May 02, 2014 02:42:07 PM Olof Johansson wrote:
> 
> > > Some of the ideas I have heard discussed are:
> > > * Adding a new common API for resource management which will have
> > > backends for ACPI or DT depending on platform
> 
> > I would like to do this, personally, because I believe that drivers
> > should not need to add support for any particular firmware interfaces
> > directly (except for listing matching device IDs).
> 
> The trouble with this is that the different firmware interfaces have
> rather different ideas about how things should work.  Basic things like
> interrupts are generally fine but more complex things like the way that
> devices integrate with system power management are much more up in the
> air.

In my opinion, device drivers should not be concerned about that really.
The layers of code above them (bus types etc.) should, but not drivers
themselves, because that makes it difficult to use the same driver
for the same piece of hardware on two systems with different firmware
interfaces.

Thanks!


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.