From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Stephen Boyd <sboyd@kernel.org>, linux-clk@vger.kernel.org
Cc: nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com
Subject: Re: [GIT PULL] Microchip clock updates for v6.12
Date: Wed, 4 Sep 2024 10:21:23 +0300 [thread overview]
Message-ID: <b76f5e26-3d75-4c8a-b7e7-18d9e7327eed@tuxon.dev> (raw)
In-Reply-To: <50577525a098bd1e39b8eed1c8053872.sboyd@kernel.org>
On 03.09.2024 23:55, Stephen Boyd wrote:
> Quoting Claudiu Beznea (2024-09-01 06:34:25)
>> The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:
>>
>> Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)
>>
>> are available in the Git repository at:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git tags/clk-microchip-6.12
>>
>> for you to fetch changes up to 2d6e9ee7cb3e79b1713783c633b13af9aeffc90c:
>>
>> clk: at91: sama7g5: Allocate only the needed amount of memory for PLLs (2024-08-24 17:44:11 +0300)
>>
>> ----------------------------------------------------------------
>
> Thanks. Pulled into clk-next
Thanks!
>
> Please get rid of the clk.h include in sam9x7.c though. Looks like you
> can use struct clk_parent_data and use fw_name for that.
It's on my todo list. I have something prepared but didn't managed to
publish something.
> Also, could it
> be a simple platform driver instead? That would be ideal.
I'm not sure at the moment as there are clocks that feed the timer. I'll
have to explore this.
Thank you,
Claudiu Beznea
prev parent reply other threads:[~2024-09-04 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 13:34 [GIT PULL] Microchip clock updates for v6.12 Claudiu Beznea
2024-09-03 20:55 ` Stephen Boyd
2024-09-04 7:21 ` claudiu beznea [this message]
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=b76f5e26-3d75-4c8a-b7e7-18d9e7327eed@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-clk@vger.kernel.org \
--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