> This is a general query about what is the preferred method of allocating
> gpios.
> The gpiod* family of functions provided similar functionality and
> automatically
> deal with active low / high outputs, direction, inital value etc...
> I raise this more for knowledge on what method I should use for my patches.
I first tried using gpiod, but failed. The API requires that the gpios
be in the root of the device's subtree in the DT blob. But here the
gpios are associated to a switch, and the switch part of the subtree
is one level down. gpiod has no way to get them from there.
> Other than that the concept looks good and something I has been
> looking at adding.
Please feel free to test it on your hardware and send a Tested-by :-)
> Would it be worth considering placing the chip in reset on driver
> remove? I have an battery powered hardware platform using one of
> this marvell devices and for certain configurations we don't need
> the switch active. So unloading the module to place the device in
> reset and would save power. Reloading would reinitialise the port.
I think we first need to get module unload/load working reliably.
This is being worked on. But i'm not against this in principle. Power
saving in general needs working on for Marvall devices. There is no
suspend/resume support for example. It would also be good to ensure
the PHYs are powered off when not needed, etc.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
