Commit d5d9a818 authored by Laurent Pinchart's avatar Laurent Pinchart Committed by Simon Horman
parent d2a31bdd
...@@ -107,4 +107,10 @@ config PINCTRL_PFC_SH7786 ...@@ -107,4 +107,10 @@ config PINCTRL_PFC_SH7786
depends on GENERIC_GPIO depends on GENERIC_GPIO
select PINCTRL_SH_PFC select PINCTRL_SH_PFC
config PINCTRL_PFC_SHX3
def_bool y
depends on CPU_SUBTYPE_SHX3
depends on GENERIC_GPIO
select PINCTRL_SH_PFC
endif endif
...@@ -18,3 +18,4 @@ obj-$(CONFIG_PINCTRL_PFC_SH7734) += pfc-sh7734.o ...@@ -18,3 +18,4 @@ obj-$(CONFIG_PINCTRL_PFC_SH7734) += pfc-sh7734.o
obj-$(CONFIG_PINCTRL_PFC_SH7757) += pfc-sh7757.o obj-$(CONFIG_PINCTRL_PFC_SH7757) += pfc-sh7757.o
obj-$(CONFIG_PINCTRL_PFC_SH7785) += pfc-sh7785.o obj-$(CONFIG_PINCTRL_PFC_SH7785) += pfc-sh7785.o
obj-$(CONFIG_PINCTRL_PFC_SH7786) += pfc-sh7786.o obj-$(CONFIG_PINCTRL_PFC_SH7786) += pfc-sh7786.o
obj-$(CONFIG_PINCTRL_PFC_SHX3) += pfc-shx3.o
...@@ -600,6 +600,9 @@ static const struct platform_device_id sh_pfc_id_table[] = { ...@@ -600,6 +600,9 @@ static const struct platform_device_id sh_pfc_id_table[] = {
#endif #endif
#ifdef CONFIG_PINCTRL_PFC_SH7786 #ifdef CONFIG_PINCTRL_PFC_SH7786
{ "pfc-sh7786", (kernel_ulong_t)&sh7786_pinmux_info }, { "pfc-sh7786", (kernel_ulong_t)&sh7786_pinmux_info },
#endif
#ifdef CONFIG_PINCTRL_PFC_SHX3
{ "pfc-shx3", (kernel_ulong_t)&shx3_pinmux_info },
#endif #endif
{ "sh-pfc", 0 }, { "sh-pfc", 0 },
{ }, { },
......
...@@ -66,5 +66,6 @@ extern struct sh_pfc_soc_info sh7734_pinmux_info; ...@@ -66,5 +66,6 @@ extern struct sh_pfc_soc_info sh7734_pinmux_info;
extern struct sh_pfc_soc_info sh7757_pinmux_info; extern struct sh_pfc_soc_info sh7757_pinmux_info;
extern struct sh_pfc_soc_info sh7785_pinmux_info; extern struct sh_pfc_soc_info sh7785_pinmux_info;
extern struct sh_pfc_soc_info sh7786_pinmux_info; extern struct sh_pfc_soc_info sh7786_pinmux_info;
extern struct sh_pfc_soc_info shx3_pinmux_info;
#endif /* __SH_PFC_CORE_H__ */ #endif /* __SH_PFC_CORE_H__ */
This diff is collapsed.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment