Hi Laurent,
On Sat, Apr 4, 2015 at 2:46 PM, Laurent Pinchart
<[email protected]> wrote:
>> + for (i = 0; i < dev->ngpios; i++)
>> + gpio_request_one(dev->gpios[i].gpio, dev->gpios[i].flags,
>> + pdev->name);
>
> Aren't GPIO numbers dynamic too in DT-based systems ? Beside, shouldn't it be
Apparently not, as the old legacy number still works, and it doesn't work
without.
> the responsibility of the drievr to request the GPIOs it needs ?
As far as I understand it, on Armadillo this is used more for platform
configuration than for device configuration, as it affects multiple devices
(the comment says DBGMD/LCDC0/FSIA MUX).
I guess I could use a "gpio-hog" subnode in DT instead, but then we're already
implementing the conversion to DT ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
