Linux-Rockchip Archive on lore.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.18 #1
Date: Sun, 21 Sep 2025 22:59:39 +0200	[thread overview]
Message-ID: <1897877.QZUTf85G27@diego> (raw)

Hi Mike, Stephen,

please find below a pull-request with Rockchip clock change for 6.18
Just a single newly exported clock for an older SoC.


Please pull.

Thanks
Heiko


The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

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

for you to fetch changes up to 77111b2c22ef5b368da5c833175b6f7806b39ccb:

  clk: rockchip: rk3368: use clock ids for SCLK_MIPIDSI_24M (2025-09-03 14:17:54 +0200)

----------------------------------------------------------------
Export the dsi-24MHz clock on the RK3368, which seems to get some
attention to enable DSI support there.

----------------------------------------------------------------
WeiHao Li (2):
      dt-bindings: clock: rk3368: Add SCLK_MIPIDSI_24M
      clk: rockchip: rk3368: use clock ids for SCLK_MIPIDSI_24M

 drivers/clk/rockchip/clk-rk3368.c      | 2 +-
 include/dt-bindings/clock/rk3368-cru.h | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)




_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

             reply	other threads:[~2025-09-21 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-21 20:59 Heiko Stuebner [this message]
2025-09-21 22:29 ` [GIT PULL] Rockchip clock changes for 6.18 #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=1897877.QZUTf85G27@diego \
    --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