From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: sashiko-bot@kernel.org, sashiko-reviews@lists.linux.dev,
conor+dt@kernel.org, linux-clk@vger.kernel.org,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 5/7] clk: nuvoton: ma35d1: Reparent SYSPLL correctly
Date: Wed, 14 Oct 2026 10:16:25 +0200 [thread overview]
Message-ID: <8733u81yue.fsf@bootlin.com> (raw)
In-Reply-To: <179191307176.266355.13493126045902473311.b4-reply@b4> (Jerome Brunet's message of "Tue, 13 Oct 2026 19:37:51 +0200")
On 13/10/2026 at 19:37:51 +02, Jerome Brunet <jbrunet@baylibre.com> wrote:
>> > So 2 possibilities:
>> > * You just need the .hw then I don't really get why you are doing it differently
>> > for this clock ?
>>
>> True.
>>
>> > * OR, this is one of the those clock where you want to check DT first then
>>
>> It is not.
>>
>> > fallback to a fixed clock, then yes you need parent_data. don't forget
>> > the fw_name (which I did not see here) and use a local variable for that,
>> > not a global
>> >
>> > Did I miss something ?
>>
>> You got it absolutely right, and while implementing the change I
>> remember why I used the name instead of the hw pointer:
>>
>> clk_hw_register_fixed_rate_parent_hw() exists, but
>> devm_clk_hw_register_fixed_rate_parent_hw() did not.
>>
>> So since it looks like most of these helpers have their devm_
>> counterpart, I will add this new helper in clk-provider.h. I plan on
>> doing that addition in this commit because I think that is what Boyd
>> used to prefer, but I can add it in a preparation patch that is your own
>> preference, I don't mind.
>
> Separate patch for the new helper please. Same series is fine.
Ack, thanks.
next prev parent reply other threads:[~2026-10-14 8:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 20:45 [PATCH v8 0/7] clk: nuvoton: ma35d1: Fix mux parenting and peripheral clock rates Miquel Raynal
2026-10-04 20:45 ` [PATCH v8 1/7] clk: nuvoton: ma35d1: Use clk_hw pointers as mux parents Miquel Raynal
2026-10-04 20:45 ` [PATCH v8 2/7] clk: nuvoton: ma35d1: Avoid possible error pointer dereferencing Miquel Raynal
2026-10-04 20:45 ` [PATCH v8 3/7] clk: nuvoton: ma35d1: Retrieve HXT/LXT from DT when possible Miquel Raynal
2026-10-04 20:59 ` sashiko-bot
2026-10-04 21:16 ` Miquel Raynal
2026-10-05 9:06 ` Jerome Brunet
2026-10-13 17:12 ` Miquel Raynal
2026-10-13 17:35 ` Jerome Brunet
2026-10-14 8:17 ` Miquel Raynal
2026-10-14 14:20 ` Miquel Raynal
2026-10-04 20:45 ` [PATCH v8 4/7] clk: nuvoton: ma35d1: Reparent the gates correctly Miquel Raynal
2026-10-04 20:45 ` [PATCH v8 5/7] clk: nuvoton: ma35d1: Reparent SYSPLL correctly Miquel Raynal
2026-10-04 20:55 ` sashiko-bot
2026-10-04 21:19 ` Miquel Raynal
2026-10-05 9:12 ` Jerome Brunet
2026-10-06 7:57 ` Miquel Raynal
2026-10-12 15:30 ` Jerome Brunet
2026-10-13 16:53 ` Miquel Raynal
2026-10-13 17:37 ` Jerome Brunet
2026-10-14 8:16 ` Miquel Raynal [this message]
2026-10-04 20:45 ` [PATCH v8 6/7] arm64: dts: nuvoton: ma35d1: Drop HXT clock output name Miquel Raynal
2026-10-04 20:45 ` [PATCH v8 7/7] arm64: dts: nuvoton: ma35d1: Add LXT crystal and clock-names Miquel Raynal
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=8733u81yue.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=linux-clk@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.