diff options
author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2015-09-06 01:44:50 +0900 |
---|---|---|
committer | Simon Glass <sjg@chromium.org> | 2015-09-19 15:42:15 -0600 |
commit | 8a5f6129d1450f5ff92a55cfcfd7b96ee019e303 (patch) | |
tree | 570037dd6b2c7dd79c3bba22cc0e489629a7db29 /drivers/pinctrl/Kconfig | |
parent | 1fb8d7933924aa5deb7e722d64c1d9fc7f0b2b82 (diff) | |
download | u-boot-imx-8a5f6129d1450f5ff92a55cfcfd7b96ee019e303.zip u-boot-imx-8a5f6129d1450f5ff92a55cfcfd7b96ee019e303.tar.gz u-boot-imx-8a5f6129d1450f5ff92a55cfcfd7b96ee019e303.tar.bz2 |
pinctrl: move dm_scan_fdt_node() out of pinctrl uclass
Commit c5acf4a2b3c6 ("pinctrl: Add the concept of peripheral IDs")
added some additional change that was not mentioned in the git-log.
That commit added dm_scan_fdt_node() in the pinctrl uclass binding.
It should be handled by the simple-bus driver or the low-level
driver, not by the pinctrl framework.
I guess Simon's motivation was to bind GPIO banks located under the
Rockchip pinctrl device. It is true some chips have sub-devices
under their pinctrl devices, but it is basically SoC-specific matter.
This commit partly reverts commit c5acf4a2b3c6 to keep the only
pinctrl-generic features in the uclass. The dm_scan_fdt_node()
should be called from the rk3288_pinctrl driver.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Simon Glass <sjg@chromium.org>
Tested-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'drivers/pinctrl/Kconfig')
0 files changed, 0 insertions, 0 deletions