From: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <lee@kernel.org>, <ukleinek@kernel.org>,
<alexandre.torgue@foss.st.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <wbg@kernel.org>,
<jic23@kernel.org>, <daniel.lezcano@linaro.org>,
<tglx@linutronix.de>, <catalin.marinas@arm.com>,
<will@kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<linux-pwm@vger.kernel.org>, <olivier.moysan@foss.st.com>
Subject: Re: [PATCH 1/8] dt-bindings: mfd: stm32-lptimer: add support for stm32mp25
Date: Wed, 26 Feb 2025 19:17:24 +0100 [thread overview]
Message-ID: <4010c7b7-f285-40e6-a032-055c4252ecb7@foss.st.com> (raw)
In-Reply-To: <8b42f0ad-2993-43b8-9055-6d74dc3bafbe@kernel.org>
On 2/26/25 08:51, Krzysztof Kozlowski wrote:
> On 25/02/2025 15:57, Fabrice Gasnier wrote:
>> On 2/25/25 13:02, Krzysztof Kozlowski wrote:
>>> On Mon, Feb 24, 2025 at 07:01:43PM +0100, Fabrice Gasnier wrote:
>>>> pwm:
>>>> type: object
>>>> additionalProperties: false
>>>>
>>>> properties:
>>>> compatible:
>>>> - const: st,stm32-pwm-lp
>>>> + enum:
>>>> + - st,stm32-pwm-lp
>>>> + - st,stm32mp25-pwm-lp
>>>>
>>>> "#pwm-cells":
>>>> const: 3
>>>> @@ -69,7 +76,9 @@ properties:
>>>>
>>>> properties:
>>>> compatible:
>>>> - const: st,stm32-lptimer-counter
>>>> + enum:
>>>> + - st,stm32-lptimer-counter
>>>> + - st,stm32mp25-lptimer-counter
>>>
>>> Driver changes suggest many of these are compatible. Why isn't this expressed?
>>
>> Hi Krzysztof,
>>
>> The Low Power Timer (LPTIM) hardware isn't fully backward compatible.
>>
>> At driver level, as indicated in the cover-letter, same feature list as
>> on STM32MP1x is supported currently. This is probably what makes it look
>> like it's compatible, but it's not fully compatible.
>
> I don't understand. Same feature list is supported means fully
> compatible, but you say not fully compatible. You are aware that
> compatible means not the same?
>
>>
>> The hardware controller is a bit different. Some registers/bits has been
>> revisited among other things. This is the purpose for these new compatibles.
>
> We do not discuss new compatibles. We discuss lack of compatibility. If
> registers/bits are changed, how existing driver can work with same ID table?
Hi Krzysztof,
To summarize on dt-bindings side, here is my view, following your
comments on per driver basis of the compatible usage.
Let's keep these new compatibles:
- "st,stm32mp25-lptimer-trigger"
- "st,stm32mp25-lptimer-counter"
Both reflect not only LPTimer hardware update, but also specific
interconnect to other hardware blocks throughout all the STM32MP25 SoC.
Other compatible strings may be dropped. Reading the
revision/identification register of the LPTimer should be enough for
compatibility in the related drivers.
I'll update this in next revision of the series.
Thanks for reviewing,
Best Regards,
Fabrice
>
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-02-26 20:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 18:01 [PATCH 0/8] Add STM32MP25 LPTIM support: MFD, PWM, IIO, counter, clocksource Fabrice Gasnier
2025-02-24 18:01 ` [PATCH 1/8] dt-bindings: mfd: stm32-lptimer: add support for stm32mp25 Fabrice Gasnier
2025-02-25 12:02 ` Krzysztof Kozlowski
2025-02-25 14:57 ` Fabrice Gasnier
2025-02-26 7:51 ` Krzysztof Kozlowski
2025-02-26 18:17 ` Fabrice Gasnier [this message]
2025-02-24 18:01 ` [PATCH 2/8] " Fabrice Gasnier
2025-02-24 18:01 ` [PATCH 3/8] iio: trigger: " Fabrice Gasnier
2025-03-05 14:38 ` Jonathan Cameron
2025-02-24 18:01 ` [PATCH 4/8] clocksource: stm32-lptimer: add stm32mp25 support Fabrice Gasnier
2025-02-25 12:02 ` Krzysztof Kozlowski
2025-02-25 14:57 ` Fabrice Gasnier
2025-02-26 18:14 ` Fabrice Gasnier
2025-02-24 18:01 ` [PATCH 5/8] pwm: stm32-lp: add support for stm32mp25 Fabrice Gasnier
2025-02-25 12:04 ` Krzysztof Kozlowski
2025-02-25 14:58 ` Fabrice Gasnier
2025-02-26 7:54 ` Krzysztof Kozlowski
2025-02-26 18:14 ` Fabrice Gasnier
2025-02-24 18:01 ` [PATCH 6/8] counter: stm32-lptimer-cnt: " Fabrice Gasnier
2025-02-25 12:02 ` Krzysztof Kozlowski
2025-02-25 14:58 ` Fabrice Gasnier
2025-02-26 7:49 ` Krzysztof Kozlowski
2025-02-26 18:16 ` Fabrice Gasnier
2025-02-24 18:01 ` [PATCH 7/8] arm64: defconfig: enable STM32 LP timers drivers Fabrice Gasnier
2025-02-25 7:48 ` Krzysztof Kozlowski
2025-02-25 8:43 ` Fabrice Gasnier
2025-02-25 12:00 ` Krzysztof Kozlowski
2025-02-24 18:01 ` [PATCH 8/8] arm64: dts: st: add low-power timer nodes on stm32mp251 Fabrice Gasnier
2025-02-25 20:12 ` [PATCH 0/8] Add STM32MP25 LPTIM support: MFD, PWM, IIO, counter, clocksource Rob Herring (Arm)
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=4010c7b7-f285-40e6-a032-055c4252ecb7@foss.st.com \
--to=fabrice.gasnier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=olivier.moysan@foss.st.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=ukleinek@kernel.org \
--cc=wbg@kernel.org \
--cc=will@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