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

[Darren Hart <darren@dvhart.com>]

On Mon, May 5, 2014 at 9:58 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> On this topic I need to add:
>
> how are the ACPI HW descriptions really happening?
>
> I as subsystem maintainer have no real contact with these people,
> I can only get a *vague* feeling that sometimes, they live in an ancient
> world of assumptions that do not hold.
>
> Specifically I am worried when seeing some ACPI stuff that their idea
> of pin control is "some sort of fancy GPIO-bolt on" and I fear they will
> attempt to model and implement this with an ugly interface that we
> will have to account for later, instead of reading say
> Documentation/pinctrl.txt and learn something about how software
> engineers go about handling such hardware.

I was talking with someone just last week about how this might be
done. I'll see if I can get the person looking into it to reach out to
you.

> Where is the communication entry port for a driver subsystem
> maintainer that want to bring a message to the ACPI HW bindings
> people?

Rafael and I would be a good start. He and I, along with others, have
been spending some time lately in the ACPI Specification Working Group
and have some idea of how this stuff works. Matthew Garrett is another
good contact for how to get involved.


-- 
Darren Hart