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.1 #1
Date: Sat, 10 Sep 2022 03:22:41 +0200	[thread overview]
Message-ID: <2252399.ElGaqSPkdT@phil> (raw)

The following changes since commit 1c23f9e627a7b412978b4e852793c5e3c3efc555:

  Linux 6.0-rc2 (2022-08-21 17:32:54 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 6541b424ce1dda616d3946e839f015c984df7a99:

  soc: rockchip: power-domain: add power domain support for rk3588 (2022-09-09 19:06:41 +0200)

----------------------------------------------------------------
Powerdomain drivers for rv1126 and rk3588 socs, keep current state of
power-domains instead of always enabling when adding them, add rv1126
io domains and add binding for another "general register files" syscon.

----------------------------------------------------------------
Elaine Zhang (1):
      soc: rockchip: power-domain: do not enable domain when adding it

Finley Xiao (2):
      dt-bindings: power: add power-domain header for rk3588
      soc: rockchip: power-domain: add power domain support for rk3588

Frank Wunderlich (1):
      dt-bindings: soc: grf: add pcie30-{phy,pipe}-grf

Heiko Stuebner (2):
      Merge branch 'v6.1-shared/powerdomain' into v6.1-armsoc/drivers
      Merge branch 'v6.1-shared/powerdomain' into v6.1-armsoc/drivers

Jagan Teki (4):
      dt-bindings: power: Add power-domain header for RV1126
      dt-bindings: power: rockchip: Document RV1126 power-controller
      soc: rockchip: power-domain: Add RV1126 power domains
      dt-bindings: power: rockchip: Document RV1126 PMU IO domains

Jianqun Xu (1):
      soc: rockchip: io-domain: Add RV1126 IO domains

Sebastian Reichel (2):
      dt-bindings: arm: rockchip: add rk5388 compatible string to pmu.yaml
      dt-bindings: power: rockchip: Add bindings for rk3588

 .../devicetree/bindings/arm/rockchip/pmu.yaml      |   2 +
 .../bindings/power/rockchip,power-controller.yaml  |   4 +
 .../bindings/power/rockchip-io-domain.yaml         |  30 +++++
 .../devicetree/bindings/soc/rockchip/grf.yaml      |   3 +
 drivers/soc/rockchip/io-domain.c                   |  20 ++++
 drivers/soc/rockchip/pm_domains.c                  | 130 ++++++++++++++++++---
 include/dt-bindings/power/rk3588-power.h           |  69 +++++++++++
 include/dt-bindings/power/rockchip,rv1126-power.h  |  35 ++++++
 8 files changed, 280 insertions(+), 13 deletions(-)
 create mode 100644 include/dt-bindings/power/rk3588-power.h
 create mode 100644 include/dt-bindings/power/rockchip,rv1126-power.h




_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2022-09-10  1:23 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=2252399.ElGaqSPkdT@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).