From: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Sam Protsenko <semen.protsenko@linaro.org>,
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 v1 1/2] dt-bindings: soc: samsung: usi: allow 64-bit address space
Date: Wed, 23 Jul 2025 11:21:35 +0300 [thread overview]
Message-ID: <3e1d7be9-e99f-41c3-8b0d-aaa426aa9de8@gmail.com> (raw)
In-Reply-To: <20250723-hypnotic-malkoha-of-trust-9efdb6@kuoka>
On 7/23/25 11:15, Krzysztof Kozlowski wrote:
> On Tue, Jul 22, 2025 at 03:10:36PM +0300, Ivaylo Ivanov wrote:
>> Some device trees, like the exynos2200 one, configure the root node
>> with #address-cells and #size-cells set to 2. However, the usi binding
>> expects 32 bit address space only. Allow these determining properties to
> So if USI expects 32 bit, then why do we allow 64?
>
> Switching this to 2 means you use 64-bit addressing for children
I don't, but the main point was to avoid defining ranges for every single usi
node, because they are a lot.
Best regards,
Ivaylo
> and
> allowing DMA for >32 bit. This should be the true reason - what is the
> address space and DMA range for children?
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2025-07-23 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 12:10 [PATCH v1 1/2] dt-bindings: soc: samsung: usi: allow 64-bit address space Ivaylo Ivanov
2025-07-22 12:10 ` [PATCH v1 2/2] dt-bindings: soc: samsung: usi: add samsung,exynos2200-usi compatible Ivaylo Ivanov
2025-07-24 2:24 ` Sam Protsenko
2025-07-23 8:15 ` [PATCH v1 1/2] dt-bindings: soc: samsung: usi: allow 64-bit address space Krzysztof Kozlowski
2025-07-23 8:21 ` Ivaylo Ivanov [this message]
2025-07-24 3:02 ` Sam Protsenko
2025-07-24 7:24 ` Ivaylo Ivanov
2025-07-24 6:56 ` Krzysztof Kozlowski
2025-07-24 7:02 ` Ivaylo Ivanov
2025-07-25 7:37 ` Krzysztof Kozlowski
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=3e1d7be9-e99f-41c3-8b0d-aaa426aa9de8@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=krzk@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).