diff options
author | Simon Glass | 2022-12-21 07:27:39 -0700 |
---|---|---|
committer | Simon Glass | 2023-01-18 11:49:13 -0700 |
commit | 85d87112cb0abedf0d6f1a14422e89d335533157 (patch) | |
tree | 5b28f9a4a7a7b69b3c463ce8213d243ac5ef61f8 | |
parent | ebc1d50ab51bd08f3adc19de37e81d23d655f9f4 (diff) |
dm: pinctrl: Revert "pinctrl: probe pinctrl drivers during post-bind"
This breaks chromebook_coral and it is also not how things should work. If
a board needs to bind GPIOs as part of a pinctrl driver this can be done
during the bind step, if needed.
We cannot probe pinctrl devices when binding as a rule, since it cannot be
supported on some platforms.
The bind and probe steps are separate in U-Boot and they should remain
separate.
This reverts commit f9ec791b5e24378b71590877499f8683d5f54dac.
Signed-off-by: Simon Glass <sjg@chromium.org>
-rw-r--r-- | drivers/pinctrl/pinctrl-uclass.c | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/drivers/pinctrl/pinctrl-uclass.c b/drivers/pinctrl/pinctrl-uclass.c index ce2d5ddf6d9..a1b85ca87e5 100644 --- a/drivers/pinctrl/pinctrl-uclass.c +++ b/drivers/pinctrl/pinctrl-uclass.c @@ -403,13 +403,6 @@ static int __maybe_unused pinctrl_post_bind(struct udevice *dev) { const struct pinctrl_ops *ops = pinctrl_get_ops(dev); - /* - * Make sure that the pinctrl driver gets probed after binding - * as some pinctrl drivers also register the GPIO driver during - * probe, and if they are not probed GPIO-s are not registered. - */ - dev_or_flags(dev, DM_FLAG_PROBE_AFTER_BIND); - if (!ops) { dev_dbg(dev, "ops is not set. Do not bind.\n"); return -EINVAL; |