devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Machon <daniel.machon@microchip.com>
To: 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>,
	Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>,
	Steen Hegelund <Steen.Hegelund@microchip.com>,
	Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: <linux-clk@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] clk: lan966x: add support for lan969x SoC clock driver
Date: Mon, 16 Sep 2024 11:49:18 +0200	[thread overview]
Message-ID: <20240916-lan969x-clock-v1-0-0e150336074d@microchip.com> (raw)

Add support for the lan969x SoC clock driver in the existing lan966x
driver. The lan969x clock controller contains 3 PLLs - cpu_clk, ddr_clk
and sys_clk which generates and supplies the clock to various
peripherals within the SoC.

Patch #1 adds compatible strings for lan969x SKU's in the dt-bindings

Patch #2 makes the clk_names var const char * const

Patch #3 prepares the lan966x driver for lan969x, by adding private
         match data.

Patch #4 adds support for lan969x

Signed-off-by: Daniel Machon <daniel.machon@microchip.com>

Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
---
Daniel Machon (4):
      dt-bindings: clock: add support for lan969x
      clk: lan966x: make clk_names const char * const
      clk: lan966x: prepare driver for lan969x support
      clk: lan966x: add support for lan969x SoC clock driver

 .../bindings/clock/microchip,lan966x-gck.yaml      | 13 +++-
 drivers/clk/clk-lan966x.c                          | 79 +++++++++++++++++-----
 2 files changed, 75 insertions(+), 17 deletions(-)
---
base-commit: 3cfb5aa10cb78571e214e48a3a6e42c11d5288a1
change-id: 20240912-lan969x-clock-ac4bc920869c

Best regards,
-- 
Daniel Machon <daniel.machon@microchip.com>


             reply	other threads:[~2024-09-16  9:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  9:49 Daniel Machon [this message]
2024-09-16  9:49 ` [PATCH 1/4] dt-bindings: clock: add support for lan969x Daniel Machon
2024-09-16 15:33   ` Conor Dooley
2024-09-16  9:49 ` [PATCH 2/4] clk: lan966x: make clk_names const char * const Daniel Machon
2024-09-16  9:49 ` [PATCH 3/4] clk: lan966x: prepare driver for lan969x support Daniel Machon
2024-09-16  9:49 ` [PATCH 4/4] clk: lan966x: add support for lan969x SoC clock driver Daniel Machon
2024-10-17 22:59 ` [PATCH 0/4] " Stephen Boyd
2024-10-18  8:34   ` claudiu beznea
2024-10-19  6:01     ` Stephen Boyd
2024-10-20 15:39 ` Claudiu Beznea

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=20240916-lan969x-clock-v1-0-0e150336074d@microchip.com \
    --to=daniel.machon@microchip.com \
    --cc=Steen.Hegelund@microchip.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=horatiu.vultur@microchip.com \
    --cc=kavyasree.kotagiri@microchip.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@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).