From: Inochi Amaoto <inochiama@gmail.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Richard Cochran <richardcochran@gmail.com>,
Vinod Koul <vkoul@kernel.org>,
Alexander Sverdlin <alexander.sverdlin@gmail.com>,
Nikita Shubin <nikita.shubin@maquefel.me>,
Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Inochi Amaoto <inochiama@gmail.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Yixun Lan <dlan@gentoo.org>,
Longbin Li <looong.bin@gmail.com>
Subject: Re: (subset) [PATCH v5 0/5] clk: sophgo: add SG2044 clock controller support
Date: Wed, 7 May 2025 07:45:54 +0800 [thread overview]
Message-ID: <174657514016.201370.7208767895794181355.b4-ty@gmail.com> (raw)
In-Reply-To: <20250418020325.421257-1-inochiama@gmail.com>
On Fri, 18 Apr 2025 10:03:19 +0800, Inochi Amaoto wrote:
> The clock controller of SG2044 provides multiple clocks for various
> IPs on the SoC, including PLL, mux, div and gates. As the PLL and
> div have obvious changed and do not fit the framework of SG2042,
> a new implement is provided to handle these.
>
> Changed from v4:
> 1. patch 1,3: Applied Krzysztof's tag.
> 2. patch 1: fix header path in description.
> 3. patch 4: drop duplicated module alias.
> 4. patch 5: make sg2044_clk_desc_data const.
>
> [...]
Applied to sophgo-clk-for-6.16-rc1, thanks!
[1/5] dt-bindings: soc: sophgo: Add SG2044 top syscon device
https://github.com/sophgo/linux/commit/e4b700d38957526fbcec6d7bb5890ad4c1192241
[3/5] dt-bindings: clock: sophgo: add clock controller for SG2044
https://github.com/sophgo/linux/commit/1a215904986e48ce04ac8f24ecb5b18cb6beaf43
[4/5] clk: sophgo: Add PLL clock controller support for SG2044 SoC
https://github.com/sophgo/linux/commit/ff5240793b0484187a836f6e1b7f0e376e0776ed
Thanks,
Inochi
next prev parent reply other threads:[~2025-05-06 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 2:03 [PATCH v5 0/5] clk: sophgo: add SG2044 clock controller support Inochi Amaoto
2025-04-18 2:03 ` [PATCH v5 1/5] dt-bindings: soc: sophgo: Add SG2044 top syscon device Inochi Amaoto
2025-04-18 2:03 ` [PATCH v5 2/5] soc: sophgo: sg2044: Add support for SG2044 TOP " Inochi Amaoto
2025-04-18 2:03 ` [PATCH v5 3/5] dt-bindings: clock: sophgo: add clock controller for SG2044 Inochi Amaoto
2025-04-18 2:03 ` [PATCH v5 4/5] clk: sophgo: Add PLL clock controller support for SG2044 SoC Inochi Amaoto
2025-04-18 2:03 ` [PATCH v5 5/5] clk: sophgo: Add " Inochi Amaoto
2025-04-30 0:58 ` [PATCH v5 0/5] clk: sophgo: add SG2044 clock controller support Inochi Amaoto
2025-05-06 23:45 ` Inochi Amaoto [this message]
2025-05-06 23:48 ` (subset) " Inochi Amaoto
2025-05-07 0:01 ` Inochi Amaoto
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=174657514016.201370.7208767895794181355.b4-ty@gmail.com \
--to=inochiama@gmail.com \
--cc=alexander.sverdlin@gmail.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=looong.bin@gmail.com \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=unicorn_wang@outlook.com \
--cc=vkoul@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