Linux clock framework development
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>, mturquette@baylibre.com
Cc: linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [GIT PULL] Rockchip clock changes for 6.9 #1
Date: Wed, 28 Feb 2024 13:59:30 -0800	[thread overview]
Message-ID: <6ef4172aeae6ea47b56fd012de653932.sboyd@kernel.org> (raw)
In-Reply-To: <4130821.6PsWsQAL7t@diego>

Quoting Heiko Stuebner (2024-02-28 00:33:17)
> Hi Mike, Stephen,
> 
> please find below a pull-request with some Rockchip clock changes for 6.9
> 
> I guess the most interesting change is the removal of the CLK_NR_CLKS
> constant from the rk3588 binding. While it was nice to define the upper
> limit of clocks for array-search purposes, it was noted that changing this
> when adding new clocks actually breaks the ABI.
> 
> Thankfully Sebastian invested the time to find a solution to not need that
> constant in the driver anymore.
> 
> That change also got the needed review by dt-maintainers and people
> also checked the usage in i.e. u-boot, so it's better to do this now than
> later :-) .
> 
> 
> Please pull.
> 
> Thanks
> Heiko
> 
> 
> The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
> 
>   Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.9-rockchip-clk1
> 
> for you to fetch changes up to 1361d75503fccc0e6b3ecbcd5bb53bbdfdc52f0a:
> 
>   clk: rockchip: rk3399: Allow to set rate of clk_i2s0_frac's parent (2024-02-27 23:45:53 +0100)
> 
> ----------------------------------------------------------------

Thanks. Pulled into clk-next

      reply	other threads:[~2024-02-28 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  8:33 [GIT PULL] Rockchip clock changes for 6.9 #1 Heiko Stuebner
2024-02-28 21:59 ` Stephen Boyd [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=6ef4172aeae6ea47b56fd012de653932.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=heiko@sntech.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.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