linux-kernel - [PATCH v1 0/7] JH7100 Audio Clocks

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20220126173953.1016706-1-kernel@esmil.dk>
Date:   Wed, 26 Jan 2022 18:39:46 +0100
From:   Emil Renner Berthing <kernel@...il.dk>
To:     linux-clk@...r.kernel.org, devicetree@...r.kernel.org
Cc:     Emil Renner Berthing <kernel@...il.dk>,
        Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Andy Shevchenko <andy.shevchenko@...il.com>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Arnd Bergmann <arnd@...db.de>,
        Michael Zhu <michael.zhu@...rfivetech.com>,
        Fu Wei <tekkamanninja@...il.com>, linux-kernel@...r.kernel.org
Subject: [PATCH v1 0/7] JH7100 Audio Clocks

This series add support for the audio clocks on the StarFive JH7100
RISC-V SoC, although the first two patches are fixes to the original
addition of the basic clock driver. At least the first fix may be
considered for 5.17.

It turns out the SoC has several memory ranges for different clocks, but
they all share the layout of the control registers. This could be
modelled in 3 ways:

1) Model all the clocks as a single peripheral with multiple memory
   ranges and have a single driver for them all. 
2) Model each memory range as different, but related peripherals with a
   single driver handling all of them.
3) Model each memory range as different peripherals with separate
   drivers that can share most code.

Although the first option would require less code this series implements
the 3rd option. The basic clock driver has to be built-in to boot the
SoC, so separate drivers for the other registers means less code needs
to be built-in and can be left as loadable modules.

Emil Renner Berthing (7):
  clk: starfive: jh7100: Don't round divisor up twice
  clk: starfive: jh7100: Handle audio_div clock properly
  dt-bindings: clock: Add JH7100 audio clock definitions
  dt-bindings: clock: Add starfive,jh7100-audclk bindings
  clk: starfive: jh7100: Make hw clock implementation reusable
  clk: starfive: jh7100: Support more clock types
  clk: starfive: Add JH7100 audio clock driver

 .../clock/starfive,jh7100-audclk.yaml         |  57 ++++++
 MAINTAINERS                                   |   8 +-
 drivers/clk/starfive/Kconfig                  |   8 +
 drivers/clk/starfive/Makefile                 |   1 +
 .../clk/starfive/clk-starfive-jh7100-audio.c  | 170 +++++++++++++++++
 drivers/clk/starfive/clk-starfive-jh7100.c    | 176 +++++++++---------
 drivers/clk/starfive/clk-starfive-jh7100.h    | 112 +++++++++++
 .../dt-bindings/clock/starfive-jh7100-audio.h |  41 ++++
 8 files changed, 482 insertions(+), 91 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/clock/starfive,jh7100-audclk.yaml
 create mode 100644 drivers/clk/starfive/clk-starfive-jh7100-audio.c
 create mode 100644 drivers/clk/starfive/clk-starfive-jh7100.h
 create mode 100644 include/dt-bindings/clock/starfive-jh7100-audio.h

-- 
2.34.1