[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a4458673-b219-41c4-90f3-b089a8ef76ba@kernel.org>
Date: Mon, 22 Dec 2025 09:16:31 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Yixun Lan <dlan@...too.org>
Cc: Ulf Hansson <ulf.hansson@...aro.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Adrian Hunter <adrian.hunter@...el.com>,
Philipp Zabel <p.zabel@...gutronix.de>, Paul Walmsley <pjw@...nel.org>,
Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
Alexandre Ghiti <alex@...ti.fr>, Iker Pedrosa <ikerpedrosam@...il.com>,
linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
linux-riscv@...ts.infradead.org, spacemit@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: mmc: spacemit,sdhci: add reset support
On 22/12/2025 03:12, Yixun Lan wrote:
>>> required:
>>> - compatible
>>> - reg
>>> - interrupts
>>> - clocks
>>> - clock-names
>>> + - resets
>>> + - reset-names
>>
>> This is an ABI break without mentioning in commit msg and without any
>> justification.
>>
> Indeed, this will introduce a breakage when combining new kernel + old dtb
>
> Since in current case, the eMMC works fine without reset line operation,
> I then would make this property optional (drop it from 'required' section)
> and switch to use devm_reset_control_get_optional_xx() API in driver code
>
> Does this looks good to you?
>
Yes
Best regards,
Krzysztof
Powered by blists - more mailing lists