Linux clock framework development
 help / color / mirror / Atom feed
From: Gabriel FERNANDEZ <gabriel.fernandez@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH v9 2/4] dt-bindings: stm32: update DT bingding for stm32mp25
Date: Fri, 5 Apr 2024 14:54:37 +0200	[thread overview]
Message-ID: <285f2f64-58b0-4dd0-9f1a-89306a79d572@foss.st.com> (raw)
In-Reply-To: <e70dc513-df9f-4b99-b9d9-7ebaf83e8f3e@linaro.org>


On 4/5/24 09:12, Krzysztof Kozlowski wrote:
> On 02/04/2024 14:53, gabriel.fernandez@foss.st.com wrote:
>> From: Gabriel Fernandez <gabriel.fernandez@foss.st.com>
>>
>> Now RCC driver use '.index' of clk_parent_data struct to define a parent.
>> The majority of parents are SCMI clocks, then dt-bindings must be fixed.
>>
>> Fixes: b5be49db3d47 ("dt-bindings: stm32: add clocks and reset binding for stm32mp25 platform")
> And except what Rob said, this does not look as a fix. How ABI break
> could be a fix and what is even to fix here? Please describe the
> observable bug, how it manifests itself and what is exactly the fix for
> that bug.
As I replied to Rob, there are no RCC STM32MP25 drivers already upstreamed.

However, in my series, the DT binding was merged even though Stephen 
made some

important remarks that needed to be taken into account.

That's why I proposed a fix to update the documentation.

To be sure, how would you like me to proceed?

Best Regards,

Gabriel

>
> Best regards,
> Krzysztof
>

  reply	other threads:[~2024-04-05 12:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 12:53 [RESEND PATCH v9 0/4] Introduce STM32MP257 clock driver gabriel.fernandez
2024-04-02 12:53 ` [RESEND PATCH v9 1/4] clk: stm32mp13: use platform device APIs gabriel.fernandez
2024-04-02 12:53 ` [RESEND PATCH v9 2/4] dt-bindings: stm32: update DT bingding for stm32mp25 gabriel.fernandez
2024-04-04 13:52   ` Rob Herring
2024-04-05 12:54     ` Gabriel FERNANDEZ
2024-04-05  7:12   ` Krzysztof Kozlowski
2024-04-05 12:54     ` Gabriel FERNANDEZ [this message]
2024-04-05 18:22       ` Krzysztof Kozlowski
2024-04-02 12:53 ` [RESEND PATCH v9 3/4] clk: stm32: introduce clocks for STM32MP257 platform gabriel.fernandez
2024-04-02 12:53 ` [RESEND PATCH v9 4/4] arm64: dts: st: add rcc support for STM32MP25 gabriel.fernandez

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=285f2f64-58b0-4dd0-9f1a-89306a79d572@foss.st.com \
    --to=gabriel.fernandez@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@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