linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: <Ryan.Wanner@microchip.com>
To: <mturquette@baylibre.com>, <sboyd@kernel.org>,
	<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
	<claudiu.beznea@tuxon.dev>
Cc: <linux-clk@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <mripard@kernel.org>,
	Ryan Wanner <Ryan.Wanner@microchip.com>
Subject: [PATCH 0/2] AT91 Clock Adjustments
Date: Thu, 6 Feb 2025 11:14:41 -0700	[thread overview]
Message-ID: <cover.1738864727.git.Ryan.Wanner@microchip.com> (raw)

From: Ryan Wanner <Ryan.Wanner@microchip.com>

This set has clock system adjustments for the AT91 clock system.

The first is to adjust the slow clock driver to account for the updated
DT node-naming for clocks and xtals and ensuring the driver is still
backwards compatible.

The second is a adding a missing clk_hw struct that is not added into
parent_data struct causing a incorrect parent for main_osc.

Ryan Wanner (2):
  clk: at91: sckc: Fix parent_data struct for slow osc
  clk: at91: sama7d65: Add missing clk_hw to parent_data

 drivers/clk/at91/sama7d65.c |  1 +
 drivers/clk/at91/sckc.c     | 12 ++++++------
 2 files changed, 7 insertions(+), 6 deletions(-)

-- 
2.43.0



             reply	other threads:[~2025-02-06 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 18:14 Ryan.Wanner [this message]
2025-02-06 18:14 ` [PATCH 1/2] clk: at91: sckc: Fix parent_data struct for slow osc Ryan.Wanner
2025-02-06 18:14 ` [PATCH 2/2] clk: at91: sama7d65: Add missing clk_hw to parent_data Ryan.Wanner
2025-02-26  9:06 ` [PATCH 0/2] AT91 Clock Adjustments Claudiu Beznea
     [not found]   ` <b76108c1-3282-4b98-a210-b350e8ec0ec2@microchip.com>
2025-03-18 17:33     ` Ryan Wanner
2025-03-19 17:50       ` 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=cover.1738864727.git.Ryan.Wanner@microchip.com \
    --to=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=mripard@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=nicolas.ferre@microchip.com \
    --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).