linux-kernel - Re: [PATCH 2/7] arm64: dts: ls1028a: move Mali DP500 node into /soc

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] [day] [month] [year] [list]

Message-ID: <ad65d1782c051a51534ad0197cc374d8@walle.cc>
Date:   Thu, 20 Jan 2022 09:17:37 +0100
From:   Michael Walle <michael@...le.cc>
To:     Leo Li <leoyang.li@....com>
Cc:     linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Shawn Guo <shawnguo@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Vladimir Oltean <vladimir.oltean@....com>
Subject: Re: [PATCH 2/7] arm64: dts: ls1028a: move Mali DP500 node into /soc

Am 2022-01-20 09:06, schrieb Leo Li:
>> -----Original Message-----
>> From: Michael Walle <michael@...le.cc>
>> Sent: Tuesday, August 31, 2021 9:40 PM
>> To: linux-arm-kernel@...ts.infradead.org; devicetree@...r.kernel.org; 
>> linux-
>> kernel@...r.kernel.org
>> Cc: Shawn Guo <shawnguo@...nel.org>; Leo Li <leoyang.li@....com>; Rob
>> Herring <robh+dt@...nel.org>; Vladimir Oltean 
>> <vladimir.oltean@....com>;
>> Michael Walle <michael@...le.cc>
>> Subject: [PATCH 2/7] arm64: dts: ls1028a: move Mali DP500 node into 
>> /soc
>> 
>> Move it inside the /soc subnode because it is part of the CCSR space.
> 
> I just noticed that the dp0_out label has been changed to dpi0_out
> besides the move.  Is this an intentional change or a typo?  If
> intentional we probably should mention it, otherwise we should change
> it back as it is breaking build for off-tree patch that uses the
> label.

It's intentional, because dp0_out might sound like displayport. And
from what I've found the output is a display pixel interface, hence dpi.

I agree, that this should have been two patches, must have slipped.
But this series was merged months ago, so we can't change anything
anymore.

Besides, given the fact that there is no support for the DisplayPort
PHY in upstream (yet, I'm working on that), I doubt there are any
out-of-tree device trees, which don't use the proprietary NXP
driver.

Also, if there is an out-of-tree device tree, it should be easy
enough for NXP to change that :)

-michael