diff options
author | Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> | 2019-08-08 09:19:02 +0300 |
---|---|---|
committer | Geert Uytterhoeven <geert+renesas@glider.be> | 2019-08-12 16:55:26 +0300 |
commit | b13431ed6eab808affbd796a7c8caf05c7ae4cdd (patch) | |
tree | eb710d50ca6429c3afe865748e4b21c8f4fbbcbd /drivers/pinctrl/pinctrl-ingenic.c | |
parent | 1d4ba593d02e8ec41c2baaabdce9f62b71062dc7 (diff) | |
download | linux-b13431ed6eab808affbd796a7c8caf05c7ae4cdd.tar.xz |
pinctrl: sh-pfc: Remove incomplete flag "cfg->type"
The old commit c58d9c1b26e3 ("sh-pfc: Implement generic pinconf
support") broke the cfg->type flag to PINMUX_TYPE_FUNCTION because
sh_pfc_pinconf_set() didn't call sh_pfc_reconfig_pin().
Now if we fix the cfg->type condition, it gets worse because:
- Some drivers might be deferred so that .set_mux() will be called
multiple times.
- In such the case, the sh-pfc driver returns -EBUSY even if
the group is the same, and then that driver fails to probe.
Since the pinctrl subsystem already has such conditions according
to @set_mux and @gpio_request_enable, this patch just remove
the incomplete flag from sh-pfc/pinctrl.c.
Fixes: c58d9c1b26e3 ("sh-pfc: Implement generic pinconf support")
Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Diffstat (limited to 'drivers/pinctrl/pinctrl-ingenic.c')
0 files changed, 0 insertions, 0 deletions