From: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] arm64: dts: exynos2200: increase peric1 and cmgp syscon sizes
Date: Wed, 6 Aug 2025 17:05:40 +0300 [thread overview]
Message-ID: <adca090e-27ba-40db-bf99-54d27069415c@gmail.com> (raw)
In-Reply-To: <CAPLW+4=QwTv96KMdJ7tcWd+Swh-fC7+h9bo22e2aZMeRbg4wKQ@mail.gmail.com>
On 8/2/25 01:11, Sam Protsenko wrote:
> On Wed, Jul 30, 2025 at 2:43 AM Ivaylo Ivanov
> <ivo.ivanov.ivanov1@gmail.com> wrote:
>> Some USI instances have swconfig offsets that reside over the currently
>> defined syscon ranges for peric1 and cmgp. Increase their sizes.
>>
>> Signed-off-by: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
>> ---
> Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org>
>
>> arch/arm64/boot/dts/exynos/exynos2200.dtsi | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/exynos/exynos2200.dtsi b/arch/arm64/boot/dts/exynos/exynos2200.dtsi
>> index 943e83851..bab77b442 100644
>> --- a/arch/arm64/boot/dts/exynos/exynos2200.dtsi
>> +++ b/arch/arm64/boot/dts/exynos/exynos2200.dtsi
>> @@ -328,7 +328,7 @@ cmu_peric1: clock-controller@10700000 {
>>
>> syscon_peric1: syscon@10720000 {
>> compatible = "samsung,exynos2200-peric1-sysreg", "syscon";
>> - reg = <0x10720000 0x2000>;
>> + reg = <0x10720000 0x3000>;
> Exynos850 TRM says that all System Register instances (in Exynos850
> SoC) use 16 KiB (0x4000) of address space for their registers. And I
> can see some SYSREG registers actually have offsets over 0x3000. In
> reality though all IP cores are aligned by 0x10000. I have a feeling
> Samsung does the IP cores integration in the same way for all their
> modern Exynos SoCs. It can be actually deduced by looking at the
> starting addresses of the nodes in the device tree, they are always
> aligned by 0x10000.
>
> Hence I'd recommend doing this:
> 1. Use either 0x4000 or 0x10000 size (not 0x3000). For the
> reference, Exynos850 and gs101 use 0x10000 value.
> 2. Replace the size values for all sysreg nodes in your device tree
> (not only peric1 and cmgp), for consistency and to prevent possible
> issues in future.
Alright, thanks.
>
> Also, maybe it'd be better to use "sysreg_" prefix for these node
> labels (not "syscon_"), as it's called System Register in TRM. But
> that's minor, and probably out of scope for this patch.
Does not matter that much imo, just a label. You could make a patch to
rename it on other trees too.
Best regards,
Ivaylo
>
>> };
>>
>> pinctrl_peric1: pinctrl@10730000 {
>> @@ -471,7 +471,7 @@ cmu_cmgp: clock-controller@14e00000 {
>>
>> syscon_cmgp: syscon@14e20000 {
>> compatible = "samsung,exynos2200-cmgp-sysreg", "syscon";
>> - reg = <0x14e20000 0x2000>;
>> + reg = <0x14e20000 0x3000>;
>> };
>>
>> pinctrl_cmgp: pinctrl@14e30000 {
>> --
>> 2.43.0
>>
>>
next prev parent reply other threads:[~2025-08-06 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 7:42 [PATCH v2 0/5] arm64: dts: exynos2200: introduce serial busses, except spi Ivaylo Ivanov
2025-07-30 7:42 ` [PATCH v2 1/5] arm64: dts: exynos2200: fix typo in hsi2c23 bus pins label Ivaylo Ivanov
2025-08-01 20:59 ` Sam Protsenko
2025-07-30 7:42 ` [PATCH v2 2/5] arm64: dts: exynos2200: use 32-bit address space for /soc Ivaylo Ivanov
2025-08-01 21:16 ` Sam Protsenko
2025-07-30 7:42 ` [PATCH v2 3/5] arm64: dts: exynos2200: increase peric1 and cmgp syscon sizes Ivaylo Ivanov
2025-08-01 22:11 ` Sam Protsenko
2025-08-06 14:05 ` Ivaylo Ivanov [this message]
2025-07-30 7:42 ` [PATCH v2 4/5] arm64: dts: exynos2200: add serial_0/1 nodes Ivaylo Ivanov
2025-08-01 23:12 ` Sam Protsenko
2025-08-06 14:03 ` Ivaylo Ivanov
2025-07-30 7:42 ` [PATCH v2 5/5] arm64: dts: exynos2200: define all usi nodes Ivaylo Ivanov
2025-08-02 0:29 ` Sam Protsenko
2025-08-06 13:57 ` Ivaylo Ivanov
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=adca090e-27ba-40db-bf99-54d27069415c@gmail.com \
--to=ivo.ivanov.ivanov1@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).