public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: mturquette@baylibre.com, Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: [GIT PULL] Rockchip clock changes for 6.4 #1
Date: Tue, 18 Apr 2023 01:46:35 +0200	[thread overview]
Message-ID: <3292931.atdPhlSkOF@phil> (raw)

Hi Mike, Stephen,

please find below a pull-request with some small Rockchip stuff.

Please pull.

Thanks
Heiko


The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:

  Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.4-rockchip-clk1

for you to fetch changes up to 64042c28c3bb6729df8e2fda89bc7ebbe3790907:

  clk: rockchip: rk3588: make gate linked clocks critical (2023-04-18 00:54:04 +0200)

----------------------------------------------------------------
Reparenting fix for the clock supplying camera modules on the rk3399
and more critical (bus-)clocks on the rk3588.

----------------------------------------------------------------
Quentin Schulz (1):
      clk: rockchip: rk3399: allow clk_cifout to force clk_cifout_src to reparent

Sebastian Reichel (1):
      clk: rockchip: rk3588: make gate linked clocks critical

 drivers/clk/rockchip/clk-rk3399.c |  2 +-
 drivers/clk/rockchip/clk-rk3588.c | 42 ++++++++++++++++++++++++---------------
 2 files changed, 27 insertions(+), 17 deletions(-)




             reply	other threads:[~2023-04-17 23:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 23:46 Heiko Stuebner [this message]
2023-04-18 19:52 ` [GIT PULL] Rockchip clock changes for 6.4 #1 Stephen Boyd

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=3292931.atdPhlSkOF@phil \
    --to=heiko@sntech.de \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mturquette@baylibre.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