mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Marek Vasut <marex@nabladev.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org, kernel@dh-electronics.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: st: stm32mp2xxx: Remove undocumented, unapproved eeprom0wl alias
Date: Fri, 20 Nov 2026 09:55:12 +0100	[thread overview]
Message-ID: <b5138676-fbd0-4922-9200-2ae600613c0b@oss.qualcomm.com> (raw)
In-Reply-To: <77bbefd5-3e05-45e4-9e0a-02063ebf3e06@nabladev.com>

On 20/11/2026 08:41, Marek Vasut wrote:
>>>> 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.
>>> U-Boot does consume Linux DTs via its CONFIG_OF_UPSTREAM .
>>
>> Cannot, otherwise it would have document that ABI. That is the
>> requirement of using OF_UPSTREAM - you also use upstream ABI. You cannot
>> use upstream DTS with downstream ABI.
> What option do I have here that does not break existing use case ? (I 
> can patch the U-Boot board code which depends on this, that is a non-issue)

Yes, please fix U-Boot.

> 
> Is there a schema which lists approved aliases now ?

Every device schema which requires custom aliases lists them. Another
point is that custom aliases are not allowed.

Best regards,
Krzysztof

      reply	other threads:[~2026-11-20  8:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 13:37 Krzysztof Kozlowski
2026-11-17 13:41 ` Marek Vasut
2026-11-17 15:13   ` Krzysztof Kozlowski
2026-11-17 16:24     ` Marek Vasut
2026-11-18 12:07       ` Krzysztof Kozlowski
2026-11-20  7:41         ` Marek Vasut
2026-11-20  8:55           ` Krzysztof Kozlowski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b5138676-fbd0-4922-9200-2ae600613c0b@oss.qualcomm.com \
    --to=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=cniedermaier@dh-electronics.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@dh-electronics.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=marex@nabladev.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®