public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea della Porta <andrea.porta@suse.com>
To: Lee Jones <lee@kernel.org>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Phil Elwell <phil@raspberrypi.com>,
	Stanimir Varbanov <svarbanov@suse.de>
Cc: Andrea della Porta <andrea.porta@suse.com>
Subject: [PATCH 0/2] Add Power Management support for BCM2712
Date: Sat,  7 Mar 2026 00:41:20 +0100	[thread overview]
Message-ID: <cover.1772839224.git.andrea.porta@suse.com> (raw)

Hi all,

This patchset adds support for the BCM2712 Power Management (PM) block,
which is necessary to power the domain of the V3D graphic block.

The implementation is done in two steps:
  - Patch 1: Adds the SoC identifier to distinguish between hardware
    variants.
  - Patch 2: Adds the specific PM support for the BCM2712.

Many thanks,
Andrea

Phil Elwell (2):
  mfd: bcm2835-pm: Introduce SoC-specific type identifier
  mfd: bcm2835-pm: Add BCM2712 PM device support

 drivers/mfd/bcm2835-pm.c       | 9 +++++----
 include/linux/mfd/bcm2835-pm.h | 7 +++++++
 2 files changed, 12 insertions(+), 4 deletions(-)

-- 
2.35.3


             reply	other threads:[~2026-03-06 23:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 23:41 Andrea della Porta [this message]
2026-03-06 23:41 ` [PATCH 1/2] mfd: bcm2835-pm: Introduce SoC-specific type identifier Andrea della Porta
2026-03-06 23:42   ` Florian Fainelli
2026-03-06 23:41 ` [PATCH 2/2] mfd: bcm2835-pm: Add BCM2712 PM device support Andrea della Porta
2026-03-06 23:43   ` Florian Fainelli
2026-03-19  9:10 ` [PATCH 0/2] Add Power Management support for BCM2712 Lee Jones

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=cover.1772839224.git.andrea.porta@suse.com \
    --to=andrea.porta@suse.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=lee@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=phil@raspberrypi.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=svarbanov@suse.de \
    /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