linux-kernel - Re: [PATCH v4 2/2] clk: Add ccf driver for Renesas 8T49N241

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 19 Jul 2021 11:10:12 +0200
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Alex Helms <alexander.helms.jy@...esas.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>,
        linux-clk <linux-clk@...r.kernel.org>,
        Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Stephen Boyd <sboyd@...nel.org>,
        Michael Turquette <mturquette@...libre.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        david.cater.jc@...esas.com, Michal Simek <michal.simek@...inx.com>,
        kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v4 2/2] clk: Add ccf driver for Renesas 8T49N241

Hi Alex,

On Tue, Jul 13, 2021 at 11:41 PM Alex Helms
<alexander.helms.jy@...esas.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@...esas.com>

Thanks for your patch!

> Reported-by: kernel test robot <lkp@...el.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@...esas.com>
>  M:     David Cater <david.cater.jc@...esas.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@...der.be>

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-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