[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a9a023233f9a096cc215203bb6ef41d7@manjaro.org>
Date: Tue, 11 Feb 2025 14:55:53 +0100
From: Dragan Simic <dsimic@...jaro.org>
To: Quentin Schulz <quentin.schulz@...rry.de>
Cc: Jagan Teki <jagan@...eble.ai>, Quentin Schulz <foss+kernel@...il.net>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>, Niklas
Cassel <cassel@...nel.org>, Michael Riesch <michael.riesch@...fvision.net>,
Jonas Karlman <jonas@...boo.se>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org, Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v5 2/4] arm64: dts: rockchip: add overlay test for Edgeble
NCM6A
Hello Quentin,
On 2025-02-11 13:59, Quentin Schulz wrote:
> On 2/10/25 7:29 PM, Dragan Simic wrote:
>> On 2025-02-10 18:57, Quentin Schulz wrote:
>>> On 2/10/25 3:11 PM, Jagan Teki wrote:
>>>> On Fri, 7 Feb 2025 at 20:50, Quentin Schulz <foss+kernel@...il.net>
>>>> wrote:
>>>>>
>>>>> From: Quentin Schulz <quentin.schulz@...rry.de>
>>>>>
>>>>> The Edgeble NCM6A can have WiFi modules connected and this is
>>>>> handled
>>>>> via an overlay (commit 951d6aaa37fe ("arm64: dts: rockchip: Add
>>>>> Edgeble
>>>>> NCM6A WiFi6 Overlay")).
>>>>>
>>>>> In order to make sure the overlay is still valid in the future,
>>>>> let's
>>>>> add a validation test by applying the overlay on top of the main
>>>>> base
>>>>> at build time.
>>>>>
>>>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
>>>>> Signed-off-by: Quentin Schulz <quentin.schulz@...rry.de>
>>>>> ---
>>>>> arch/arm64/boot/dts/rockchip/Makefile | 4 ++++
>>>>> 1 file changed, 4 insertions(+)
>>>>>
>>>>> diff --git a/arch/arm64/boot/dts/rockchip/Makefile b/arch/arm64/
>>>>> boot/dts/rockchip/Makefile
>>>>> index
>>>>> 534e70a649eeada7f9b6f12596b83f5c47b184b4..02f98abe1df10f44f2ac27ea5f6c6e6c6334724e
>>>>> 100644
>>>>> --- a/arch/arm64/boot/dts/rockchip/Makefile
>>>>> +++ b/arch/arm64/boot/dts/rockchip/Makefile
>>>>> @@ -192,3 +192,7 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3568-
>>>>> wolfvision-pf5-vz-2-uhd.dtb
>>>>> rk3568-wolfvision-pf5-vz-2-uhd-dtbs := rk3568-wolfvision-pf5.dtb
>>>>> \
>>>>> rk3568-wolfvision-pf5-display-vz.dtbo \
>>>>> rk3568-wolfvision-pf5-io-expander.dtbo
>>>>> +
>>>>> +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3588-edgeble-neu6a-wifi.dtb
>>>>> +rk3588-edgeble-neu6a-wifi-dtbs := rk3588-edgeble-neu6a-io.dtb \
>>>>> + rk3588-edgeble-neu6a-wifi.dtbo
>>>>
>>>> Please add neu6b-io as well, wifi dtbo is similar for it as well.
>>>
>>> Similar or identical :)?
>>>
>>> Should the overlay be renamed if it applies to neu6b AND neu6a
>>> instead
>>> of implying it's only for neu6a based on the name of the overlay?
>>
>> I'm afraid it's a bit too late for renaming the .dtso file. :/
>
> How is it too late? Is there some rule somewhere about renaming I
> missed?
The way I see it, names of the .dts and .dtso files become part of
the "extended ABI", so to speak, once they've been accepted upstream
for a while, because renaming them may break boot configurations.
Powered by blists - more mailing lists