Tero,
* H. Nikolaus Schaller <hns@xxxxxxxxxxxxx> [160418 11:23]:
> OMAP5 has a register to control if the ckobuffer is enabled
> and defines the polarity. ckobuffer is required to drive a twl6040
> with the system clock. Hence, add the pinctrl,single to the
> OMAP5 SoC description so that omap5-board-common can
> set up the ckobuffer as required.
Is this really a mux or should it be a mux clock?
Regards,
Tony
> Signed-off-by: H. Nikolaus Schaller <hns@xxxxxxxxxxxxx>
> ---
> arch/arm/boot/dts/omap5.dtsi | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
> index 120b6b8..1d9050f 100644
> --- a/arch/arm/boot/dts/omap5.dtsi
> +++ b/arch/arm/boot/dts/omap5.dtsi
> @@ -277,6 +277,16 @@
> pinctrl-single,register-width = <16>;
> pinctrl-single,function-mask = <0x7fff>;
> };
> +
> + omap5_control_ckobuffer: pinmux@cdb4 {
> + compatible = "ti,omap5-padconf",
> + "pinctrl-single";
> + reg = <0xcdb4 4>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + pinctrl-single,register-width = <32>;
> + pinctrl-single,function-mask = <0xf0000000>;
> + };
> };
>
> ocmcram: ocmcram@40300000 {
> --
> 2.7.3
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
