From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Jacky Huang <ychuang570808@gmail.com>
Cc: Jacky Huang <ychuang3@nuvoton.com>,
Shan-Chun Hung <schung@nuvoton.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Steam Lin <STLin2@winbond.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] clk: nuvoton: ma35d1: Use clk_hw pointers as mux parents
Date: Sun, 20 Sep 2026 15:48:55 +0200 [thread overview]
Message-ID: <87o6ds8248.fsf@bootlin.com> (raw)
In-Reply-To: <b8a8a65b-e302-4747-bc90-4920fc48795a@gmail.com> (Jacky Huang's message of "Tue, 15 Sep 2026 13:26:39 +0800")
Hi Jacky,
> For example:
>
> static const struct clk_parent_data wdt1_sel_clks[] = {
> { .index = -1, },
> { .fw_name = "lxt", },
> { .fw_name = "pclk3_div4096", },
> { .fw_name = "lirc", },
> };
>
> The TRM lists PCLK3/4096 and PCLK4/4096 as valid selectable parent
> clocks for the WDT/WWDT blocks.
>
> However, the new conversion changes these entries to -1:
>
> static const int wdt1_parent_idx[] = {
> -1, LXT, -1, LIRC
> };
That's indeed correct. Thanks for the proposal below, I will include it
in the next iteration.
[...]
> I have also tested this version on an MA35D1 board, and the clock
> parent conversion appears to work correctly for the peripherals I
> tested.
Nice! If you're happy with v2, don't hesitate to send a formal
Tested-by!
Thanks,
Miquèl
prev parent reply other threads:[~2026-09-20 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 7:28 [PATCH] clk: nuvoton: ma35d1: Use clk_hw pointers as mux parents Miquel Raynal
2026-08-14 7:28 ` sashiko-bot
2026-09-04 14:21 ` Miquel Raynal
2026-09-14 13:14 ` Miquel Raynal
2026-09-15 5:26 ` Jacky Huang
2026-09-20 13:48 ` Miquel Raynal [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=87o6ds8248.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=STLin2@winbond.com \
--cc=arnd@arndb.de \
--cc=bmasney@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=sboyd@kernel.org \
--cc=schung@nuvoton.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=ychuang3@nuvoton.com \
--cc=ychuang570808@gmail.com \
/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.