Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH v1] ARM: dts: elpida_ecb240abacn: Change Elpida compatible
From:   Dmitry Osipenko <digetx@gmail.com>
To:     Rob Herring <robh+dt@kernel.org>, Tony Lindgren <tony@atomide.com>
Cc:     linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
        linux-omap@vger.kernel.org
References: <20211019234059.29877-1-digetx@gmail.com>
Message-ID: <a584428e-99f7-986e-90d5-7e81ca213158@gmail.com>
Date:   Wed, 27 Oct 2021 15:19:02 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <20211019234059.29877-1-digetx@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

20.10.2021 02:40, Dmitry Osipenko пишет:
> Vendor prefix shouldn't start with capital letter. The Elpida Memory
> compatible was never used in practice, hence just correct the compatible.
> 
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
>  arch/arm/boot/dts/elpida_ecb240abacn.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/elpida_ecb240abacn.dtsi b/arch/arm/boot/dts/elpida_ecb240abacn.dtsi
> index d87ee4794f83..9698801cbcfb 100644
> --- a/arch/arm/boot/dts/elpida_ecb240abacn.dtsi
> +++ b/arch/arm/boot/dts/elpida_ecb240abacn.dtsi
> @@ -5,7 +5,7 @@
>  
>  / {
>  	elpida_ECB240ABACN: lpddr2 {
> -		compatible	= "Elpida,ECB240ABACN","jedec,lpddr2-s4";
> +		compatible	= "elpida,ECB240ABACN","jedec,lpddr2-s4";
>  		density		= <2048>;
>  		io-width	= <32>;
>  
> 

This patch should go via OMAP tree since there is only OMAP board which
uses this dtsi. To make it more clear, "elpida" variant is now
documented in the bindings [1][2].

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9e17f71e9c334f14ad6a8ec3edc09c7a4244e12f

[2]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=001b8b2594db4ea24fbea4c161e665f858917fce

If there is no interest in taking the patch via OMAP tree, then it may
go via the DT git tree. Rob, you should pick it up then.

Thanks!