pinctrl: freescale: add ZERO_OFFSET_VALID flag for vf610 pinctrl
Subsystems (2)
PATCH 1/1 pinctrl: freescale: add ZERO_OFFSET_VALID flag for vf610 pinctrl
To support i.MX7D Low Power State Retention IOMUXC, commit e7b37a522aa9 ("pinctrl: freescale: imx: allow mux_reg offset zero") changes the way of zero mux_reg offset support with a new flag ZERO_OFFSET_VALID. But, unfortunately, it forgot to add this flag for vf610 pinctrl which has zero mux_reg offset be valid as well, and hence breaks the vf610 support.
Fix the regression by adding flag ZERO_OFFSET_VALID for vf610 pinctrl driver.
--- drivers/pinctrl/freescale/pinctrl-vf610.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/pinctrl/freescale/pinctrl-vf610.c +1 -1
@@ -299,7 +299,7 @@ static const struct pinctrl_pin_desc vf610_pinctrl_pads[] = {static struct imx_pinctrl_soc_info vf610_pinctrl_info = { .pins = vf610_pinctrl_pads, .npins =ARRAY_SIZE (vf610_pinctrl_pads), - .flags =SHARE_MUX_CONF_REG , + .flags =SHARE_MUX_CONF_REG |ZERO_OFFSET_VALID , };static const struct of_device_id vf610_pinctrl_of_match[] = {
Signature · 1 line
1.9.1
PATCH 1/1 pinctrl: freescale: add ZERO_OFFSET_VALID flag for vf610 pinctrl
Quoted 7 lines · Shawn Guo
To support i.MX7D Low Power State Retention IOMUXC, commit
e7b37a522aa9("pinctrl: freescale: imx: allowmux_regoffset zero") changes the way of zeromux_regoffset support with a new flagZERO_OFFSET_VALID. But, unfortunately, it forgot to add this flag for vf610 pinctrl which has zeromux_regoffset be valid as well, and hence breaks the vf610 support.
Quoted 8 lines
Fix the regression by adding flag
ZERO_OFFSET_VALIDfor vf610 pinctrl driver.Signed-off-by Shawn Guo <[email protected]>Fixes e7b37a522aa9 ("pinctrl: freescale: imx: allow mux_reg offset zero")Reported-by Andrew Lunn <[email protected]>Tested-by Andrew Lunn <[email protected]>Acked-by Stefan Agner <[email protected]>
Linus,
Can you help apply the fix for v4.4-rc?
Shawn
Quoted 21 lines
--- drivers/pinctrl/freescale/pinctrl-vf610.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/pinctrl/freescale/pinctrl-vf610.c +1
-1@@ -299,7 +299,7 @@ static const struct pinctrl_pin_desc vf610_pinctrl_pads[] = {static struct imx_pinctrl_soc_info vf610_pinctrl_info = { .pins = vf610_pinctrl_pads, .npins =ARRAY_SIZE (vf610_pinctrl_pads), - .flags =SHARE_MUX_CONF_REG , + .flags =SHARE_MUX_CONF_REG |ZERO_OFFSET_VALID , };static const struct of_device_id vf610_pinctrl_of_match[] = {Signature · 1 line
1.9.1
PATCH 1/1 pinctrl: freescale: add ZERO_OFFSET_VALID flag for vf610 pinctrl
In reply to Shawn GuoQuoted 7 lines · Shawn Guo
To support i.MX7D Low Power State Retention IOMUXC, commit
e7b37a522aa9("pinctrl: freescale: imx: allowmux_regoffset zero") changes the way of zeromux_regoffset support with a new flagZERO_OFFSET_VALID. But, unfortunately, it forgot to add this flag for vf610 pinctrl which has zeromux_regoffset be valid as well, and hence breaks the vf610 support.
Quoted 8 lines
Fix the regression by adding flag
ZERO_OFFSET_VALIDfor vf610 pinctrl driver.Signed-off-by Shawn Guo <[email protected]>Fixes e7b37a522aa9 ("pinctrl: freescale: imx: allow mux_reg offset zero")Reported-by Andrew Lunn <[email protected]>Tested-by Andrew Lunn <[email protected]>Acked-by Stefan Agner <[email protected]>
Patch applied for fixes.
Sorry for the delay.
Yours,
Linus Walleij