Thread (4 messages) 4 messages, 4 authors, 2021-02-10

Re: linux-next: manual merge of the gpio-brgl tree with the arm-soc tree

flat view

From: Arnd Bergmann <arnd@kernel.org>
Date: 2021-02-09 11:44:07
Also in: linux-arm-kernel, lkml

On Tue, Feb 9, 2021 at 11:01 AM Geert Uytterhoeven [off-list ref] wrote:
On Thu, Jan 28, 2021 at 7:05 AM Stephen Rothwell [off-list ref] wrote:
quoted
diff --cc arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts
index 37da418393e0,950010a290f0..000000000000
--- a/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts
+++ b/arch/arm64/boot/dts/toshiba/tmpv7708-rm-mbrc.dts
@@@ -42,7 -42,6 +42,11 @@@
        clock-names = "apb_pclk";
  };

 +&wdt {
 +      status = "okay";
 +      clocks = <&wdt_clk>;
 +};
++
+ &gpio {
+       status = "okay";
+ };
Probably some sort order should be taken into account (gpio before uart0),
also avoidng the conflict?
We normally do this by asking everyone to send the dts changes for
inclusion through the soc tree rather than the subsystem that contains
the driver. Why is this one in the gpio-brgl tree?

       Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help