* Tero Kristo <t-kristo@xxxxxx> [170213 05:24]:
> @@ -304,6 +339,8 @@
> #gpio-cells = <2>;
> interrupt-controller;
> #interrupt-cells = <2>;
> + clocks = <&cm_l4per_clkctrl OMAP4_GPIO2_CLKCTRL 0>;
> + clock-names = "clkctrl";
> };
>
> gpio3: gpio@48057000 {
> @@ -315,6 +352,8 @@
> #gpio-cells = <2>;
> interrupt-controller;
> #interrupt-cells = <2>;
> + clocks = <&cm_l4per_clkctrl OMAP4_GPIO3_CLKCTRL 0>;
> + clock-names = "clkctrl";
> };
>
> gpio4: gpio@48059000 {
> @@ -384,6 +423,8 @@
> interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>;
> ti,hwmods = "uart1";
> clock-frequency = <48000000>;
> + clocks = <&cm_l4per_clkctrl OMAP4_UART1_CLKCTRL 0>;
> + clock-names = "clkctrl";
> };
BTW, one thing you might want to test also is that the opt clocks
can be mapped here properly for gpios to reset. That can be easily
tested by kexec booting on beagle-x15 where we currently get warnings
on kexec boot about GPIOs failing to reset.
Regards,
Tony
--
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
