From: Torsten Duwe <duwe@lst.de>
To: Hal Feng <hal.feng@starfivetech.com>
Cc: Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
"Rick Chen" <rick@andestech.com>, Leo <ycliang@andestech.com>,
Conor Dooley <conor@kernel.org>,
Yanhong Wang <yanhong.wang@starfivetech.com>,
Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Xingyu Wu <xingyu.wu@starfivetech.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH v1 0/5] Make the clock dt-bindings and DT nodes consistent with Linux
Date: Tue, 11 Jul 2023 11:09:23 +0200 [thread overview]
Message-ID: <20230711110923.08b32183@blackhole.lan> (raw)
In-Reply-To: <20230707105011.129241-1-hal.feng@starfivetech.com>
On Fri, 7 Jul 2023 18:50:06 +0800
Hal Feng <hal.feng@starfivetech.com> wrote:
> The clock dt-bindings and DT nodes are not consistent with Linux now.
> Let's sync them with Linux, so the same dtb can work for Linux & U-Boot.
>
> To achieve this goal, the PLL clock driver is separated and some clock
> IDs conversion is needed in clock drivers.
>
> For the motivation, please see the discussion in the link below.
>
> [1] https://patchwork.kernel.org/project/linux-riscv/patch/20230512022036.97987-2-xingyu.wu@starfivetech.com/
>
> Xingyu Wu (5):
> clk: starfive: jh7110: Separate the PLL driver
> riscv: dts: jh7110: Add PLL clock controller node
> riscv: dts: jh7110: Add clock source from PLL
> dt-bindings: clock: jh7110: Modify clock id to be same with Linux
> clk: starfive: jh7110: Add of_xlate ops and macros for clock id
> conversion
For better bisectability, I would have put patch 2 first, then merged 1&3,
then merged 4&5. This way U-Boot should compile and boot after each patch
(I think, untested ;) But given the rapid development of the platform,
I'm fine with inclusion of the series as-is; as it does not affect other
targets.
I'm also wondering whether the symbolic clock number constants should be
synced, too. But that's also a minor issue, as long as they expand to yield
the same numbers.
For the series:
Reviewed-by: Torsten Duwe <duwe@suse.de>
Torsten
next prev parent reply other threads:[~2023-07-11 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 10:50 [PATCH v1 0/5] Make the clock dt-bindings and DT nodes consistent with Linux Hal Feng
2023-07-07 10:50 ` [PATCH v1 1/5] clk: starfive: jh7110: Separate the PLL driver Hal Feng
2023-07-24 5:14 ` Leo Liang
2023-07-07 10:50 ` [PATCH v1 2/5] riscv: dts: jh7110: Add PLL clock controller node Hal Feng
2023-07-24 5:15 ` Leo Liang
2023-07-07 10:50 ` [PATCH v1 3/5] riscv: dts: jh7110: Add clock source from PLL Hal Feng
2023-07-24 5:15 ` Leo Liang
2023-07-07 10:50 ` [PATCH v1 4/5] dt-bindings: clock: jh7110: Modify clock id to be same with Linux Hal Feng
2023-07-24 5:15 ` Leo Liang
2023-07-07 10:50 ` [PATCH v1 5/5] clk: starfive: jh7110: Add of_xlate ops and macros for clock id conversion Hal Feng
2023-07-24 5:16 ` Leo Liang
2023-07-11 9:09 ` Torsten Duwe [this message]
2023-07-12 7:13 ` [PATCH v1 0/5] Make the clock dt-bindings and DT nodes consistent with Linux Hal Feng
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=20230711110923.08b32183@blackhole.lan \
--to=duwe@lst.de \
--cc=conor@kernel.org \
--cc=emil.renner.berthing@canonical.com \
--cc=hal.feng@starfivetech.com \
--cc=lukma@denx.de \
--cc=rick@andestech.com \
--cc=seanga2@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=xingyu.wu@starfivetech.com \
--cc=yanhong.wang@starfivetech.com \
--cc=ycliang@andestech.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.