From: Nishanth Menon <nm@ti.com> To: "Kumar, Udit" <u-kumar1@ti.com> Cc: Conor Dooley <conor+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Rob Herring <robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, Tero Kristo <kristo@kernel.org>, Vignesh Raghavendra <vigneshr@ti.com>, Robert Nelson <robertcnelson@gmail.com> Subject: Re: [PATCH 03/12] arm64: dts: ti: k3-j721e-beagleboneai64: Fixup reference to phandles array Date: Mon, 5 Jun 2023 15:49:30 -0500 [thread overview] Message-ID: <20230605204930.3hlg3d36zwtbkal7@scone> (raw) In-Reply-To: <f1e54167-15bd-8a0b-454d-53b90b18a343@ti.com> On 22:31-20230605, Kumar, Udit wrote: [...] > > diff --git a/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts b/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts > > index 37c24b077b6a..c13246a9ed8f 100644 > > --- a/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts > > +++ b/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts [...] > > @@ -639,7 +639,7 @@ &main_i2c6 { > > &wkup_i2c0 { > > status = "okay"; > > pinctrl-names = "default"; > > - pinctrl-0 = <&wkup_i2c0_pins_default &eeprom_wp_pins_default>; > > + pinctrl-0 = <&wkup_i2c0_pins_default>, <&eeprom_wp_pins_default>; > > clock-frequency = <400000>; > > Why we need more than 2 pio lines for i2c node , pio lines? I am not sure I understand. If you are suggesting eeprom_wp_pins to be moved to the eeprom node, It is probably un-related to this series, but OK, i think it is probably a valid change (unless Robert sees a reason why he did it the way he did). -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com> To: "Kumar, Udit" <u-kumar1@ti.com> Cc: Conor Dooley <conor+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Rob Herring <robh+dt@kernel.org>, <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, Tero Kristo <kristo@kernel.org>, Vignesh Raghavendra <vigneshr@ti.com>, Robert Nelson <robertcnelson@gmail.com> Subject: Re: [PATCH 03/12] arm64: dts: ti: k3-j721e-beagleboneai64: Fixup reference to phandles array Date: Mon, 5 Jun 2023 15:49:30 -0500 [thread overview] Message-ID: <20230605204930.3hlg3d36zwtbkal7@scone> (raw) In-Reply-To: <f1e54167-15bd-8a0b-454d-53b90b18a343@ti.com> On 22:31-20230605, Kumar, Udit wrote: [...] > > diff --git a/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts b/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts > > index 37c24b077b6a..c13246a9ed8f 100644 > > --- a/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts > > +++ b/arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dts [...] > > @@ -639,7 +639,7 @@ &main_i2c6 { > > &wkup_i2c0 { > > status = "okay"; > > pinctrl-names = "default"; > > - pinctrl-0 = <&wkup_i2c0_pins_default &eeprom_wp_pins_default>; > > + pinctrl-0 = <&wkup_i2c0_pins_default>, <&eeprom_wp_pins_default>; > > clock-frequency = <400000>; > > Why we need more than 2 pio lines for i2c node , pio lines? I am not sure I understand. If you are suggesting eeprom_wp_pins to be moved to the eeprom node, It is probably un-related to this series, but OK, i think it is probably a valid change (unless Robert sees a reason why he did it the way he did). -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-06-05 20:49 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-01 15:26 [PATCH 00/12] arm64: dts: ti: Fix up references to phandles Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 01/12] arm64: dts: ti: k3-j721e-sk: Fixup reference to phandles array Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 02/12] arm64: dts: ti: k3-j721e-som-p0/common-proc-board: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 03/12] arm64: dts: ti: k3-j721e-beagleboneai64: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-05 17:01 ` Kumar, Udit 2023-06-05 17:01 ` Kumar, Udit 2023-06-05 20:49 ` Nishanth Menon [this message] 2023-06-05 20:49 ` Nishanth Menon 2023-06-06 4:26 ` Kumar, Udit 2023-06-06 4:26 ` Kumar, Udit 2023-06-06 11:41 ` Nishanth Menon 2023-06-06 11:41 ` Nishanth Menon 2023-06-06 14:27 ` Robert Nelson 2023-06-06 14:27 ` Robert Nelson 2023-06-01 15:26 ` [PATCH 04/12] arm64: dts: ti: k3-am642-phyboard-electra-rdk: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 05/12] arm64: dts: ti: k3-j7200-som/common-proc-board: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 06/12] arm64: dts: ti: k3-j721s2-common-proc-board: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 07/12] arm64: dts: ti: k3-am625-sk: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 08/12] arm64: dts: ti: k3-am64-evm: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-05 17:02 ` Kumar, Udit 2023-06-05 17:02 ` Kumar, Udit 2023-06-05 20:50 ` Nishanth Menon 2023-06-05 20:50 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 09/12] arm64: dts: ti: k3-am64-sk: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 10/12] arm64: dts: ti: k3-am65-iot*: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-03 16:41 ` Jan Kiszka 2023-06-03 16:41 ` Jan Kiszka 2023-06-01 15:26 ` [PATCH 11/12] arm64: dts: ti: k3-am654-base-board: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon 2023-06-01 15:26 ` [PATCH 12/12] arm64: dts: ti: k3-am68-sk-base-board: " Nishanth Menon 2023-06-01 15:26 ` Nishanth Menon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20230605204930.3hlg3d36zwtbkal7@scone \ --to=nm@ti.com \ --cc=conor+dt@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=kristo@kernel.org \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=robertcnelson@gmail.com \ --cc=robh+dt@kernel.org \ --cc=u-kumar1@ti.com \ --cc=vigneshr@ti.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.