Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Wang <unicorn_wang@outlook.com>
To: Stephen Boyd <sboyd@kernel.org>, linux-clk@vger.kernel.org
Cc: linux-riscv@lists.infradead.org, sophgo@lists.linux.dev,
	Inochi Amaoto <inochiama@outlook.com>,
	Xiaoguang Xing <xiaoguang.xing@sophgo.com>,
	Chao Wei <chao.wei@sophgo.com>,
	unicorn_wang@outlook.com
Subject: [GIT PULL] RISC-V Sophgo SG2044 clock drivers for v6.15
Date: Mon, 10 Mar 2025 15:34:08 +0800	[thread overview]
Message-ID: <PN0PR01MB10393DBCE92A34489031BE9BEFED62@PN0PR01MB10393.INDPRD01.PROD.OUTLOOK.COM> (raw)

Hey, Stephen,

Please pull clock changes for RISC-V/Sophgo/SG2044.

I send this PR just want to expedite patches for this clock driver. The 
patches have gone through several rounds of review [v1], [v2], [v3].

Link: 
https://lore.kernel.org/linux-clk/20241209082132.752775-1-inochiama@gmail.com/ 
[v1]

Link: 
https://lore.kernel.org/linux-clk/20250204084439.1602440-1-inochiama@gmail.com/ 
[v2]

Link: 
https://lore.kernel.org/linux-clk/20250226232320.93791-1-inochiama@gmail.com/ 
[v3]

Thanks,
Chen.

The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:

   Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)

are available in the Git repository at:

   https://github.com/sophgo/linux.git tags/riscv-sg2044-clk-for-v6.15

for you to fetch changes up to 135418add3878dcd44483d0f2851f6f470a85395:

   clk: sophgo: Add clock controller support for SG2044 SoC (2025-03-10 
12:22:01 +0800)

----------------------------------------------------------------
RISC-V SG2044 clock driver changes for v6.15

Sophgo:
Added clock support for sg2044.

Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
Signed-off-by: Inochi Amaoto <inochiama@gmail.com>

----------------------------------------------------------------
Inochi Amaoto (2):
       dt-bindings: clock: sophgo: add clock controller for SG2044
       clk: sophgo: Add clock controller support for SG2044 SoC

  Documentation/devicetree/bindings/clock/sophgo,sg2044-clk.yaml |   40 ++
  drivers/clk/sophgo/Kconfig |   11 +
  drivers/clk/sophgo/Makefile |    1 +
  drivers/clk/sophgo/clk-sg2044.c                                | 2271 
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  drivers/clk/sophgo/clk-sg2044.h |   62 ++
  include/dt-bindings/clock/sophgo,sg2044-clk.h                  | 170 +++++
  6 files changed, 2555 insertions(+)
  create mode 100644 
Documentation/devicetree/bindings/clock/sophgo,sg2044-clk.yaml
  create mode 100644 drivers/clk/sophgo/clk-sg2044.c
  create mode 100644 drivers/clk/sophgo/clk-sg2044.h
  create mode 100644 include/dt-bindings/clock/sophgo,sg2044-clk.h


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2025-03-10  7:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10  7:34 Chen Wang [this message]
2025-03-11 23:21 ` [GIT PULL] RISC-V Sophgo SG2044 clock drivers for v6.15 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=PN0PR01MB10393DBCE92A34489031BE9BEFED62@PN0PR01MB10393.INDPRD01.PROD.OUTLOOK.COM \
    --to=unicorn_wang@outlook.com \
    --cc=chao.wei@sophgo.com \
    --cc=inochiama@outlook.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=sboyd@kernel.org \
    --cc=sophgo@lists.linux.dev \
    --cc=xiaoguang.xing@sophgo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox