* [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding [not found] <20220224003421.3440124-1-jwerner@chromium.org> @ 2022-02-24 0:34 ` Julius Werner 2022-02-24 7:29 ` Krzysztof Kozlowski 0 siblings, 1 reply; 5+ messages in thread From: Julius Werner @ 2022-02-24 0:34 UTC (permalink / raw) To: Krzysztof Kozlowski Cc: Dmitry Osipenko, devicetree, linux-kernel, Julius Werner This patch updates the tegra20-asus-tf101 device tree to replace the deprecated `revision-id1` binding with the new `revision-id` binding in its "jedec,lpddr2"-compatible node. This was the only DTS in the tree using this binding. The revision-id2 (mode register 7) of this memory chip was not given in the existing device tree, so let's assume 0 for now until it becomes relevant. Signed-off-by: Julius Werner <jwerner@chromium.org> --- arch/arm/boot/dts/tegra20-asus-tf101.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/tegra20-asus-tf101.dts b/arch/arm/boot/dts/tegra20-asus-tf101.dts index 020172ee7340ec..c700f80e2a366e 100644 --- a/arch/arm/boot/dts/tegra20-asus-tf101.dts +++ b/arch/arm/boot/dts/tegra20-asus-tf101.dts @@ -756,7 +756,7 @@ emc-tables@3 { lpddr2 { compatible = "elpida,B8132B2PB-6D-F", "jedec,lpddr2-s4"; - revision-id1 = <1>; + revision-id = <1 0>; density = <2048>; io-width = <16>; }; -- 2.31.0 ^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding 2022-02-24 0:34 ` [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding Julius Werner @ 2022-02-24 7:29 ` Krzysztof Kozlowski 2022-02-24 12:38 ` Thierry Reding 0 siblings, 1 reply; 5+ messages in thread From: Krzysztof Kozlowski @ 2022-02-24 7:29 UTC (permalink / raw) To: Julius Werner Cc: Dmitry Osipenko, devicetree, linux-kernel, Jonathan Hunter, Thierry Reding, linux-tegra On 24/02/2022 01:34, Julius Werner wrote: > This patch updates the tegra20-asus-tf101 device tree to replace the > deprecated `revision-id1` binding with the new `revision-id` binding in > its "jedec,lpddr2"-compatible node. This was the only DTS in the tree > using this binding. > > The revision-id2 (mode register 7) of this memory chip was not given in > the existing device tree, so let's assume 0 for now until it becomes > relevant. > > Signed-off-by: Julius Werner <jwerner@chromium.org> > --- > arch/arm/boot/dts/tegra20-asus-tf101.dts | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Please use scripts/get_maintainer.pl to get the list of people/lists to CC. You skipped here Tegra maintainers, so no one would pick up this patch. I bounced the mail to Jonathan, Thierry and linux-tegra (+Cc), so hopefully they will get it. If not, series might need resend with proper addresses. Best regards, Krzysztof ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding 2022-02-24 7:29 ` Krzysztof Kozlowski @ 2022-02-24 12:38 ` Thierry Reding 2022-02-25 1:41 ` Julius Werner 0 siblings, 1 reply; 5+ messages in thread From: Thierry Reding @ 2022-02-24 12:38 UTC (permalink / raw) To: Krzysztof Kozlowski Cc: Julius Werner, Dmitry Osipenko, devicetree, linux-kernel, Jonathan Hunter, linux-tegra [-- Attachment #1: Type: text/plain, Size: 1083 bytes --] On Thu, Feb 24, 2022 at 08:29:27AM +0100, Krzysztof Kozlowski wrote: > On 24/02/2022 01:34, Julius Werner wrote: > > This patch updates the tegra20-asus-tf101 device tree to replace the > > deprecated `revision-id1` binding with the new `revision-id` binding in > > its "jedec,lpddr2"-compatible node. This was the only DTS in the tree > > using this binding. > > > > The revision-id2 (mode register 7) of this memory chip was not given in > > the existing device tree, so let's assume 0 for now until it becomes > > relevant. > > > > Signed-off-by: Julius Werner <jwerner@chromium.org> > > --- > > arch/arm/boot/dts/tegra20-asus-tf101.dts | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > Please use scripts/get_maintainer.pl to get the list of people/lists to > CC. You skipped here Tegra maintainers, so no one would pick up this patch. > > I bounced the mail to Jonathan, Thierry and linux-tegra (+Cc), so > hopefully they will get it. If not, series might need resend with proper > addresses. Thanks for the bounce. Applied. Thierry [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 833 bytes --] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding 2022-02-24 12:38 ` Thierry Reding @ 2022-02-25 1:41 ` Julius Werner 2022-02-25 7:08 ` Krzysztof Kozlowski 0 siblings, 1 reply; 5+ messages in thread From: Julius Werner @ 2022-02-25 1:41 UTC (permalink / raw) To: Thierry Reding Cc: Krzysztof Kozlowski, Julius Werner, Dmitry Osipenko, devicetree, LKML, Jonathan Hunter, linux-tegra > > I bounced the mail to Jonathan, Thierry and linux-tegra (+Cc), so > > hopefully they will get it. If not, series might need resend with proper > > addresses. > > Thanks for the bounce. Applied. Sorry, I wasn't sure how this was supposed to work for interdependent patches, I thought they would all go through the same maintainer tree. If you do split them up please be aware of the dependency, i.e. this patch should not be applied anywhere without patch 1 and 2 of this series landing first. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding 2022-02-25 1:41 ` Julius Werner @ 2022-02-25 7:08 ` Krzysztof Kozlowski 0 siblings, 0 replies; 5+ messages in thread From: Krzysztof Kozlowski @ 2022-02-25 7:08 UTC (permalink / raw) To: Julius Werner, Thierry Reding Cc: Dmitry Osipenko, devicetree, LKML, Jonathan Hunter, linux-tegra On 25/02/2022 02:41, Julius Werner wrote: >>> I bounced the mail to Jonathan, Thierry and linux-tegra (+Cc), so >>> hopefully they will get it. If not, series might need resend with proper >>> addresses. >> >> Thanks for the bounce. Applied. > > Sorry, I wasn't sure how this was supposed to work for interdependent > patches, I thought they would all go through the same maintainer tree. > If you do split them up please be aware of the dependency, i.e. this > patch should not be applied anywhere without patch 1 and 2 of this > series landing first. DTS changes never go with driver changes. Even if within the same tree, these will be different branches, so you cannot maintain dependency. The cover letter therefore should mention such dependency, so DTS won't get applied too fast. Best regards, Krzysztof ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2022-02-25 7:08 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20220224003421.3440124-1-jwerner@chromium.org>
2022-02-24 0:34 ` [PATCH 3/3] ARM: dts: Update jedec,lpddr2 revision-id binding Julius Werner
2022-02-24 7:29 ` Krzysztof Kozlowski
2022-02-24 12:38 ` Thierry Reding
2022-02-25 1:41 ` Julius Werner
2022-02-25 7:08 ` Krzysztof Kozlowski
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox