Re: [PATCH] arm64: dts: st: stm32mp2xxx: Remove undocumented, unapproved eeprom0wl alias

From: Krzysztof Kozlowski

Date: Tue Nov 17 2026 - 10:13:43 EST


On 17/11/2026 14:41, Marek Vasut wrote:
> On 11/17/26 2:37 PM, Krzysztof Kozlowski wrote:
>> The eeprom0wl alias was never approved by Devicetree maintainers,
>> because it was never documented as actual ABI. There is no in-kernel
>> user of it, although there might be U-Boot. External DTS users cannot
>> rely on undocumented ABI, thus these are pretty safe to drop.
>>
>> No new custom aliases are allowed for years now.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxxxxx>
>> ---
>> arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi b/arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi
>> index bcf63e2ea989..5795b352fccf 100644
>> --- a/arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi
>> +++ b/arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi
>> @@ -10,7 +10,6 @@ aliases {
>> serial0 = &usart6;
>> serial1 = &uart8;
>> eeprom0 = &eeprom0;
>> - eeprom0wl = &eeprom0wl;
>> rtc0 = &rv3032;
>> rtc1 = &rtc;
>> };
>
> U-Boot depends on the alias, so please don't drop this one.

As explained, U-Boot CANNOT depend on undocumented ABI. U-Boot is not a
user as understood in Linux kernel policy "we do not break users".
Especially that U-Boot does not even consume that DTS! We do not break
U-Boot as long as it is about documented ABI.

Here U-Boot won't be really affected, because updating DTB in the
kernel, does not update the one in bootloader. It does not go that way.
It could go opposite, so from bootloader -> kernel, but not the other
way around.

Best regards,
Krzysztof