From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alex Helms <alexander.helms.jy@renesas.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
david.cater.jc@renesas.com,
Michal Simek <michal.simek@xilinx.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v4 2/2] clk: Add ccf driver for Renesas 8T49N241
Date: Mon, 19 Jul 2021 11:10:12 +0200 [thread overview]
Message-ID: <CAMuHMdW5cYfc39pHWavW84ftjBAvyaSVCeLPtMB4o_8L6msW2Q@mail.gmail.com> (raw)
In-Reply-To: <20210713214126.2278-3-alexander.helms.jy@renesas.com>
Hi Alex,
On Tue, Jul 13, 2021 at 11:41 PM Alex Helms
<alexander.helms.jy@renesas.com> wrote:
> This is a common clock framework driver that supports the 8T49N241 chip.
> No other chips in the family are currently supported. The driver
> supports setting the rate for all four outputs on the chip and
> automatically calculating/setting the appropriate VCO value.
>
> The driver can read a full register map from the device tree
> and will use that register map to initialize the attached device
> (via I2C) when the system boots. Any configuration not supported by
> the common clock framework must be done via the full register map,
> including optimized settings.
>
> All outputs are currently assumed to be LVDS unless overridden in
> the full register map in the DT.
>
> Signed-off-by: Alex Helms <alexander.helms.jy@renesas.com>
Thanks for your patch!
> Reported-by: kernel test robot <lkp@intel.com>
I don't think that line belongs here (lkp requesting 8T49N241
support? ;-)
> ---
> MAINTAINERS | 1 +
> drivers/clk/Kconfig | 21 +
> drivers/clk/renesas/8t49n24x-core.c | 836 ++++++++++++++++++++++++++++
> drivers/clk/renesas/8t49n24x-core.h | 250 +++++++++
> drivers/clk/renesas/8t49n24x.c | 572 +++++++++++++++++++
> drivers/clk/renesas/Makefile | 4 +
> 6 files changed, 1684 insertions(+)
> 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
As this is a driver for a discrete part originally from IDT, not a
clock generator integrated on a Renesas SoC, I think it belongs under
drivers/clk/ instead of drivers/clk/renesas/. That would align
nicely with the Kconfig symbol already residing in drivers/clk/Kconfig.
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15580,6 +15580,7 @@ M: Alex Helms <alexander.helms.jy@renesas.com>
> M: David Cater <david.cater.jc@renesas.com>
> S: Odd Fixes
> F: Documentation/devicetree/bindings/clock/renesas,8t49n241.yaml
> +F: drivers/clk/renesas/8t49n24x*
>
> RENESAS CLOCK DRIVERS
> M: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2021-07-19 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 21:41 [PATCH v4 0/2] Renesas 8T49N241 device driver Alex Helms
2021-07-13 21:41 ` [PATCH v4 1/2] dt-bindings: Add binding for Renesas 8T49N241 Alex Helms
2021-07-15 17:32 ` Rob Herring
2021-07-13 21:41 ` [PATCH v4 2/2] clk: Add ccf driver " Alex Helms
2021-07-19 9:10 ` Geert Uytterhoeven [this message]
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=CAMuHMdW5cYfc39pHWavW84ftjBAvyaSVCeLPtMB4o_8L6msW2Q@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=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=lkp@intel.com \
--cc=michal.simek@xilinx.com \
--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).