linux-kernel - Re: [PATCH v2 6/6] of: of_cpu_phandle_to

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c2ace0e9-6565-44c3-84eb-555707f84509@kernel.org>
Date: Sun, 4 May 2025 19:52:34 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Alireza Sanaee <alireza.sanaee@...wei.com>
Cc: devicetree@...r.kernel.org, robh@...nel.org, jonathan.cameron@...wei.com,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 linuxarm@...wei.com, mark.rutland@....com,
 shameerali.kolothum.thodi@...wei.com
Subject: Re: [PATCH v2 6/6] of: of_cpu_phandle_to_id to support SMT threads

On 04/05/2025 19:51, Krzysztof Kozlowski wrote:
>> In the CPU map, there are two cases that only one occurs at at time.
>>     1) "cpu" = <phandle>
>>     2) "cpus" = <phandle> <index>
>>
>> The first case addresses non-SMTs and the second case addresses SMTs
>> that the variable must be cpu(s) with an index where we later look up
>> the reg array with that.
>>
>>     core0 {
>>       thread0 {
>>         cpus = <&cpu0 0>;
> 
> Not so sure, dtschema says only one item is allowed in the phandle and I
> do not see here binding change.
> 
> Although this wasn't even sent to me, so I'll just ignore your patchset.

Ah, there was no binding in the patchset, so that's why I did not get
it. Makes sense now, but question about missing binding change stays.

Best regards,
Krzysztof