linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: arm@kernel.org
Cc: soc@kernel.org, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Rockchip driver changes for 6.12 #1
Date: Mon, 02 Sep 2024 00:13:40 +0200	[thread overview]
Message-ID: <23316481.ssLaC8jLEa@diego> (raw)

The following changes since commit 8400291e289ee6b2bf9779ff1c83a291501f017b:

  Linux 6.11-rc1 (2024-07-28 14:19:55 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.12-rockchip-drivers-1

for you to fetch changes up to e1aaecacfa135cd264a0db331d3ab8b2a04a54a3:

  soc: rockchip: grf: Add rk3576 default GRF values (2024-08-23 12:33:58 +0200)

----------------------------------------------------------------
rk3308 io-domains, and some default settings for bits in the general
register files for rk3128 and the new rk3576 soc.

----------------------------------------------------------------
Alex Bee (1):
      soc: rockchip: grf: Set RK3128's vpu main clock

David Wu (1):
      soc: rockchip: io-domain: Add RK3308 IO voltage domains

Detlev Casanova (2):
      dt-bindings: soc: rockchip: Add rk3576 syscon compatibles
      soc: rockchip: grf: Add rk3576 default GRF values

Jonas Karlman (1):
      dt-bindings: power: rockchip: Document RK3308 IO voltage domains

 .../bindings/power/rockchip-io-domain.yaml         | 24 +++++++++++++
 .../devicetree/bindings/soc/rockchip/grf.yaml      | 16 +++++++++
 drivers/soc/rockchip/grf.c                         | 32 ++++++++++++++++-
 drivers/soc/rockchip/io-domain.c                   | 40 ++++++++++++++++++++++
 4 files changed, 111 insertions(+), 1 deletion(-)





                 reply	other threads:[~2024-09-01 22:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=23316481.ssLaC8jLEa@diego \
    --to=heiko@sntech.de \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=soc@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).