lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fbe025c9-2688-49f1-bd94-2cb0a1bbc8d2@kernel.org>
Date: Thu, 24 Jul 2025 08:56:36 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ivaylo Ivanov <ivo.ivanov.ivanov1@...il.com>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Alim Akhtar <alim.akhtar@...sung.com>,
 Sam Protsenko <semen.protsenko@...aro.org>, Rob Herring <robh@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, linux-samsung-soc@...r.kernel.org,
 devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: soc: samsung: usi: allow 64-bit
 address space

On 23/07/2025 10:21, Ivaylo Ivanov wrote:
> 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

I do not understand your "I don't", because you do. You change the child
address space to 64 bit and switch to 36/64 bit DMA. That's the meaning
of address cells 2.


Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ