From: Alex Helms <alexander.helms.jy@renesas.com>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Cc: robh+dt@kernel.org, sboyd@kernel.org, mturquette@baylibre.com,
geert+renesas@glider.be, alexander.helms.jy@renesas.com,
david.cater.jc@renesas.com
Subject: [PATCH 0/2] Renesas 8T49N241 device driver
Date: Thu, 1 Jul 2021 12:41:33 -0700 [thread overview]
Message-ID: <20210701194135.18847-1-alexander.helms.jy@renesas.com> (raw)
A common clock framework device driver for the Renesas 8T49N241 universal
frequency translator.
Alex Helms (2):
dt-bindings: Add binding for Renesas 8T49N241
clk: Add ccf driver for Renesas 8T49N241
.../bindings/clock/renesas,8t49n241.yaml | 183 ++++
MAINTAINERS | 7 +
drivers/clk/Kconfig | 21 +
drivers/clk/renesas/8t49n24x-core.c | 836 ++++++++++++++++++
drivers/clk/renesas/8t49n24x-core.h | 251 ++++++
drivers/clk/renesas/8t49n24x.c | 573 ++++++++++++
drivers/clk/renesas/Makefile | 4 +
7 files changed, 1875 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/renesas,8t49n241.yaml
create mode 100644 drivers/clk/renesas/8t49n24x-core.c
create mode 100644 drivers/clk/renesas/8t49n24x-core.h
create mode 100644 drivers/clk/renesas/8t49n24x.c
--
2.30.2
next reply other threads:[~2021-07-01 19:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 19:41 Alex Helms [this message]
2021-07-01 19:41 ` [PATCH 1/2] dt-bindings: Add binding for Renesas 8T49N241 Alex Helms
2021-07-01 19:41 ` [PATCH 2/2] clk: Add ccf driver " Alex Helms
2021-07-01 22:21 ` kernel test robot
2021-07-01 23:22 ` [PATCH v2 0/2] Renesas 8T49N241 device driver Alex Helms
2021-07-01 23:22 ` [PATCH v2 1/2] dt-bindings: Add binding for Renesas 8T49N241 Alex Helms
2021-07-02 6:52 ` Biju Das
2021-07-02 21:51 ` Alexander Helms
2021-07-03 10:15 ` Biju Das
2021-07-02 13:28 ` Rob Herring
2021-07-01 23:22 ` [PATCH v2 2/2] clk: Add ccf driver " Alex Helms
2021-07-02 0:57 ` [PATCH v2 0/2] Renesas 8T49N241 device driver Stephen Boyd
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=20210701194135.18847-1-alexander.helms.jy@renesas.com \
--to=alexander.helms.jy@renesas.com \
--cc=david.cater.jc@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).