On 21 January 2016 at 19:43, Simon Glass <s...@chromium.org> wrote: > GPIO drivers want to be able to show if a pin is enabled for input, output, > or is being used by another function. Some drivers can easily find this > and the code is included in the driver. For some SoCs this is more complex. > Conceptually this should be handled by pinctrl rather than GPIO. Most > pinctrl drivers will have this feature anyway. > > Add a method by which a GPIO driver can obtain the pin mux value given a > GPIO reference. This avoids repeating the code in two places. > > Signed-off-by: Simon Glass <s...@chromium.org> > --- > > Changes in v9: None > Changes in v2: None > > drivers/pinctrl/pinctrl-uclass.c | 10 ++++++++++ > include/dm/pinctrl.h | 32 ++++++++++++++++++++++++++++++++ > 2 files changed, 42 insertions(+)
Applied to u-boot-rockchip. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
