public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexey Klimov <alexey.klimov@linaro.org>,
	Sam Protsenko <semen.protsenko@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Alim Akhtar <alim.akhtar@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: exynos850: Add SRAM node
Date: Tue, 14 Apr 2026 11:08:21 +0200	[thread overview]
Message-ID: <4c6a92e0-15a1-4f82-afc9-542f5ad9d2df@kernel.org> (raw)
In-Reply-To: <DHSR70EGYY4N.2EA2HWIXJR7QR@linaro.org>

On 14/04/2026 11:00, Alexey Klimov wrote:
> On Mon Apr 13, 2026 at 4:23 PM BST, Krzysztof Kozlowski wrote:
>> On 13/04/2026 16:52, Alexey Klimov wrote:
>>> SRAM is used by the ACPM protocol to retrieve the ACPM channels
>>> information and configuration data. Add the SRAM node.
>>>
>>> Signed-off-by: Alexey Klimov <alexey.klimov@linaro.org>
>>> ---
>>>  arch/arm64/boot/dts/exynos/exynos850.dtsi | 8 ++++++++
>>>  1 file changed, 8 insertions(+)
>>>
>>> diff --git a/arch/arm64/boot/dts/exynos/exynos850.dtsi b/arch/arm64/boot/dts/exynos/exynos850.dtsi
>>> index cb55015c8dce..cf4a6168846c 100644
>>> --- a/arch/arm64/boot/dts/exynos/exynos850.dtsi
>>> +++ b/arch/arm64/boot/dts/exynos/exynos850.dtsi
>>> @@ -910,6 +910,14 @@ spi_2: spi@11d20000 {
>>>  			};
>>>  		};
>>>  	};
>>> +
>>> +	apm_sram: sram@2039000 {
>>> +		compatible = "mmio-sram";
>>> +		reg = <0x0 0x2039000 0x40000>;
>>> +		#address-cells = <1>;
>>> +		#size-cells = <1>;
>>> +		ranges = <0x0 0x0 0x2039000 0x40000>;
>>
>> You miss here children.
> 
> Thank you! I guess I should convert it to smth like this:
> 
> apm_sram: sram@2039000 {
> 		compatible = "mmio-sram";
> 		reg = <0x0 0x2039000 0x40000>;
> 		ranges = <0x0 0x0 0x2039000 0x40000>;
> 		#address-cells = <1>;
> 		#size-cells = <1>;
> 
> 		acpm_sram_region: sram-section@0 {
> 			reg = <0x0 0x40000>;

This covers entire block, so feels pointless. Maybe requirement of
children should be dropped. What's the point of having children? Why
does the driver need them?

> 		};
> 	};
> 
> And then later reference shmem = &acpm_sram_region from acpm node.
> 
>> Also, 'ranges' should be after 'reg'.
> 
> Thanks, will fix this.
> 
> FWIW this commit is a copy of commit 48e7821b26904
> https://lore.kernel.org/r/20250207-gs101-acpm-dt-v4-1-230ba8663a2d@linaro.org


Huh, we should fix that one as well.


Best regards,
Krzysztof


  reply	other threads:[~2026-04-14  9:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 14:52 [PATCH] arm64: dts: exynos850: Add SRAM node Alexey Klimov
2026-04-13 15:23 ` Krzysztof Kozlowski
2026-04-14  9:00   ` Alexey Klimov
2026-04-14  9:08     ` Krzysztof Kozlowski [this message]
2026-04-14 10:20       ` Tudor Ambarus

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=4c6a92e0-15a1-4f82-afc9-542f5ad9d2df@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexey.klimov@linaro.org \
    --cc=alim.akhtar@samsung.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=semen.protsenko@linaro.org \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox