linux-rockchip.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.5 #1
Date: Sun, 11 Jun 2023 23:12:12 +0200	[thread overview]
Message-ID: <10286366.nUPlyArG6x@phil> (raw)

The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:

  Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.5-rockchip-drivers1

for you to fetch changes up to a10b3841f901714dbe16a8f9b0f2bbe1034e6454:

  soc: rockchip: dtpm: use C99 array init syntax (2023-06-11 22:38:04 +0200)

----------------------------------------------------------------
An addition to the rk3588 power-domains, some new syscon compatibles for
rk3588-based "General-register-files" register areas and a move to
C99 array inits for the dtpm driver to fix sparse warnings.

----------------------------------------------------------------
Boris Brezillon (1):
      soc: rockchip: power-domain: add rk3588 mem module support

Randy Dunlap (1):
      soc: rockchip: dtpm: use C99 array init syntax

Sebastian Reichel (2):
      dt-bindings: soc: rockchip: add rk3588 usb2phy syscon
      dt-bindings: soc: rockchip: add rk3588 pipe-phy syscon

 .../devicetree/bindings/soc/rockchip/grf.yaml      |   3 +
 drivers/soc/rockchip/dtpm.c                        |  54 +++----
 drivers/soc/rockchip/pm_domains.c                  | 160 ++++++++++++++++-----
 3 files changed, 155 insertions(+), 62 deletions(-)




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

                 reply	other threads:[~2023-06-11 21:12 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=10286366.nUPlyArG6x@phil \
    --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).