linux-kernel - Re: [PATCH v2 07/13] arm64: dts: ti: k3-am64: Enable OSPI nodes at the board level

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]

Date:   Tue, 8 Aug 2023 09:19:04 -0500
From:   Andrew Davis <afd@...com>
To:     Nishanth Menon <nm@...com>
CC:     Vignesh Raghavendra <vigneshr@...com>,
        Tero Kristo <kristo@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Dhruva Gole <d-gole@...com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 07/13] arm64: dts: ti: k3-am64: Enable OSPI nodes at
 the board level

On 8/8/23 9:17 AM, Nishanth Menon wrote:
> On 09:13-20230808, Andrew Davis wrote:
>> On 8/8/23 8:34 AM, Andrew Davis wrote:
>>> OSPI nodes defined in the top-level AM64 SoC dtsi files are incomplete
>>> and may not be functional unless they are extended with pinmux and
>>> device information.
>>>
>>> As the attached OSPI device is only known about at the board integration
>>> level, these nodes should only be enabled when provided with this
>>> information.
>>>
>>> Disable the OSPI nodes in the dtsi files and only enable the ones that
>>> are actually pinned out on a given board.
>>>
>>> Signed-off-by: Andrew Davis <afd@...com>
>>> Reviewed-by: Dhruva Gole <d-gole@...com>
>>> ---
>>
>> Oops, I see we have a new AM64 board in -next (tqma64xxl), I can either
>> rebase this again and enable the nodes in there. Or you can skip this
>> and the other AM64 patch in this series and I'll resend them next cycle
>> when that new board is settled.
> 
> we should respin this series taking the new boards into consideration -
> am64 and am62 both have new boards.
> 

No problem, v3 on the way.

Andrew