public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: <Ryan.Wanner@microchip.com>, <mturquette@baylibre.com>,
	<sboyd@kernel.org>, <alexandre.belloni@bootlin.com>,
	<claudiu.beznea@tuxon.dev>
Cc: <varshini.rajendran@microchip.com>,
	<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/3]clk: at91: add sama7d65 clock support
Date: Thu, 5 Sep 2024 17:21:23 +0200	[thread overview]
Message-ID: <1da0abbb-94e5-42fd-a2d2-71d5d7d253fb@microchip.com> (raw)
In-Reply-To: <cover.1725392645.git.Ryan.Wanner@microchip.com>

On 04/09/2024 at 17:54, Ryan.Wanner@microchip.com wrote:
> From: Ryan Wanner <Ryan.Wanner@microchip.com>
> 
> Hello,
> 
> This series adds clock support for the SAMA7D65 SoC. There are also
> changes to the master clock driver and PLL driver in order to account for
> the increased amount of clocks being supported in this new SoC.
> 
> Trying to account for all the updates happening in this system, this
> patch set is based off of the most recent updates to at91-next branch.
> 
> Changes in v2:
> - Correct PLL ID from PLL_ID_IMG to PLL_ID_GPU in the description.
> - Adjust master clock description to match amount of master clocks 0-9.
> - Correct bad spacing and bad alignment.
> - Remove double variable definition.
> - Add missing kfree() at end of function.
> - Reorganize clk and pll driver changes in patch set.

To the whole series:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>

> Ryan Wanner (3):
>    clk: at91: clk-master: increase maximum number of clocks
>    clk: at91: clk-sam9x60-pll: increase maximum amount of plls
>    clk: at91: sama7d65: add sama7d65 pmc driver

For the record, additions to the DT binding are posed here:
https://lore.kernel.org/lkml/20240829-sama7d65-next-v1-1-53d4e50b550d@microchip.com/

Best regards,
   Nicolas

>   drivers/clk/at91/Makefile          |    1 +
>   drivers/clk/at91/clk-master.c      |    2 +-
>   drivers/clk/at91/clk-sam9x60-pll.c |    2 +-
>   drivers/clk/at91/pmc.c             |    1 +
>   drivers/clk/at91/sama7d65.c        | 1373 ++++++++++++++++++++++++++++
>   5 files changed, 1377 insertions(+), 2 deletions(-)
>   create mode 100644 drivers/clk/at91/sama7d65.c
> 


  parent reply	other threads:[~2024-09-05 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 15:54 [PATCH v2 0/3]clk: at91: add sama7d65 clock support Ryan.Wanner
2024-09-04 15:54 ` [PATCH v2 1/3] clk: at91: clk-master: increase maximum number of clocks Ryan.Wanner
2024-09-09  9:30   ` Dharma.B
2024-09-04 15:54 ` [PATCH v2 2/3] clk: at91: clk-sam9x60-pll: increase maximum amount of plls Ryan.Wanner
2024-09-04 15:54 ` [PATCH v2 3/3] clk: at91: sama7d65: add sama7d65 pmc driver Ryan.Wanner
2024-09-05 15:21 ` Nicolas Ferre [this message]
2024-10-10 18:13 ` [PATCH v2 0/3]clk: at91: add sama7d65 clock support 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=1da0abbb-94e5-42fd-a2d2-71d5d7d253fb@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=Ryan.Wanner@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=varshini.rajendran@microchip.com \
    /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