public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Jian Hu via B4 Relay <devnull+jian.hu.amlogic.com@kernel•org>
To: Neil Armstrong <neil.armstrong@linaro•org>,
	 Jerome Brunet <jbrunet@baylibre•com>,
	 Michael Turquette <mturquette@baylibre•com>,
	 Stephen Boyd <sboyd@kernel•org>, Rob Herring <robh@kernel•org>,
	 Krzysztof Kozlowski <krzk+dt@kernel•org>,
	 Conor Dooley <conor+dt@kernel•org>,
	Xianwei Zhao <xianwei.zhao@amlogic•com>,
	 Kevin Hilman <khilman@baylibre•com>,
	 Martin Blumenstingl <martin.blumenstingl@googlemail•com>
Cc: linux-amlogic@lists•infradead.org, linux-clk@vger•kernel.org,
	 devicetree@vger•kernel.org, linux-kernel@vger•kernel.org,
	 linux-arm-kernel@lists•infradead.org,
	Jian Hu <jian.hu@amlogic•com>
Subject: [PATCH v2 0/2] clk: amlogic: Add A9 peripherals clock controller
Date: Wed, 03 Jun 2026 20:03:55 +0800	[thread overview]
Message-ID: <20260603-a9_peripherals-v2-0-ee1b8c0a1e6c@amlogic.com> (raw)

This series adds Amlogic A9 peripherals clock support,
including dt-binding and peripherals clock driver.

Signed-off-by: Jian Hu <jian.hu@amlogic•com>
---
Changes in v2:
- Split the A9 clock driver and send the peripherals clock separately.
- Add COMPILE_TEST in Kconfig
- Drop the 'optional'
- Rename apb4 to soc
- Sort the header file
- Rename hifi to hifi0
- Use CLK_HW_INIT_PARENTS_DATA to describe clk_init_data
- Use CLK_HW_INIT_HW to describe clk_init_data
- Use CLK_HW_INIT_PARENTS_HW to describe clk_init_data
- Link to v1: https://lore.kernel.org/all/20260511-b4-a9_clk-v1-0-41cb4071b7c9@amlogic.com/

---
Jian Hu (2):
      dt-bindings: clock: Add Amlogic A9 peripherals clock controller
      clk: amlogic: Add A9 peripherals clock controller driver

 .../clock/amlogic,a9-peripherals-clkc.yaml         |  160 ++
 drivers/clk/meson/Kconfig                          |   15 +
 drivers/clk/meson/Makefile                         |    1 +
 drivers/clk/meson/a9-peripherals.c                 | 1927 ++++++++++++++++++++
 .../clock/amlogic,a9-peripherals-clkc.h            |  352 ++++
 5 files changed, 2455 insertions(+)
---
base-commit: ca89c88bcf69daca829044c638a8163d5ce47af0
change-id: 20260603-a9_peripherals-4214e79705dc

Best regards,
-- 
Jian Hu <jian.hu@amlogic•com>




             reply	other threads:[~2026-06-03 12:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 12:03 Jian Hu via B4 Relay [this message]
2026-06-03 12:03 ` [PATCH v2 1/2] dt-bindings: clock: Add Amlogic A9 peripherals clock controller Jian Hu via B4 Relay
2026-06-03 15:52   ` Conor Dooley
2026-06-03 12:03 ` [PATCH v2 2/2] clk: amlogic: Add A9 peripherals clock controller driver Jian Hu via B4 Relay

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=20260603-a9_peripherals-v2-0-ee1b8c0a1e6c@amlogic.com \
    --to=devnull+jian.hu.amlogic.com@kernel$(echo .)org \
    --cc=conor+dt@kernel$(echo .)org \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=jbrunet@baylibre$(echo .)com \
    --cc=jian.hu@amlogic$(echo .)com \
    --cc=khilman@baylibre$(echo .)com \
    --cc=krzk+dt@kernel$(echo .)org \
    --cc=linux-amlogic@lists$(echo .)infradead.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-clk@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=martin.blumenstingl@googlemail$(echo .)com \
    --cc=mturquette@baylibre$(echo .)com \
    --cc=neil.armstrong@linaro$(echo .)org \
    --cc=robh@kernel$(echo .)org \
    --cc=sboyd@kernel$(echo .)org \
    --cc=xianwei.zhao@amlogic$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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