From: David Yang <mmyangfl@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: David Yang <mmyangfl@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/5] Add CRG driver for Hi3798MV100 SoC
Date: Tue, 21 Mar 2023 04:40:33 +0800 [thread overview]
Message-ID: <20230320204042.980708-1-mmyangfl@gmail.com> (raw)
This series adds CRG driver for Hi3798MV100 SoC.
v2: move bindings to a separate patch
v3: fix bindings commit message, reorganize patches
v4: add ethernet and gpu clocks
v5: add complex clock
David Yang (5):
clk: hisilicon: Rename Hi3798CV200 to Hi3798
clk: hisilicon: Extract common functions
clk: hisilicon: Add complex clock for Hi3798
dt-bindings: clock: Add Hi3798MV100 CRG
clk: hisilicon: Add CRG driver for Hi3798MV100 SoC
.../devicetree/bindings/clock/hisi-crg.txt | 2 +
drivers/clk/hisilicon/Kconfig | 6 +-
drivers/clk/hisilicon/Makefile | 2 +-
drivers/clk/hisilicon/crg-hi3798.c | 742 ++++++++++++++++++
drivers/clk/hisilicon/crg-hi3798cv200.c | 401 ----------
include/dt-bindings/clock/histb-clock.h | 13 +
6 files changed, 761 insertions(+), 405 deletions(-)
create mode 100644 drivers/clk/hisilicon/crg-hi3798.c
delete mode 100644 drivers/clk/hisilicon/crg-hi3798cv200.c
--
2.39.2
next reply other threads:[~2023-03-20 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 20:40 David Yang [this message]
2023-03-20 20:40 ` [PATCH v5 1/5] clk: hisilicon: Rename Hi3798CV200 to Hi3798 David Yang
2023-03-20 20:40 ` [PATCH v5 2/5] clk: hisilicon: Extract common functions David Yang
2023-03-21 17:34 ` Stephen Boyd
2023-03-20 20:40 ` [PATCH v5 3/5] clk: hisilicon: Add complex clock for Hi3798 David Yang
2023-03-21 17:31 ` Stephen Boyd
2023-03-20 20:40 ` [PATCH v5 4/5] dt-bindings: clock: Add Hi3798MV100 CRG David Yang
2023-03-20 20:40 ` [PATCH v5 5/5] clk: hisilicon: Add CRG driver for Hi3798MV100 SoC David Yang
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=20230320204042.980708-1-mmyangfl@gmail.com \
--to=mmyangfl@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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