From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Andrea della Porta <andrea.porta@suse.com>,
Lee Jones <lee@kernel.org>,
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>
Subject: Re: [PATCH 2/2] mfd: bcm2835-pm: Add BCM2712 PM device support
Date: Fri, 6 Mar 2026 15:43:40 -0800 [thread overview]
Message-ID: <cfa04fd5-6736-4077-b6fb-61d32f13f17f@broadcom.com> (raw)
In-Reply-To: <c0b5793868f138bf5c928a12b2763d3e183e2e59.1772839224.git.andrea.porta@suse.com>
On 3/6/26 15:41, Andrea della Porta wrote:
> From: Phil Elwell <phil@raspberrypi.com>
>
> The BCM2712 SoC includes a power management block that serves as the
> power domain for the V3D graphics block. Unlike other PM blocks in
> the BCM2835 family, it does not feature an ASB register space.
>
> Conditionally register the PM device depending on the SoC variant.
>
> Signed-off-by: Phil Elwell <phil@raspberrypi.com>
> Co-developed-by: Stanimir Varbanov <svarbanov@suse.de>
> Signed-off-by: Stanimir Varbanov <svarbanov@suse.de>
> Signed-off-by: Andrea della Porta <andrea.porta@suse.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
next prev parent reply other threads:[~2026-03-06 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 23:41 [PATCH 0/2] Add Power Management support for BCM2712 Andrea della Porta
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 [this message]
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=cfa04fd5-6736-4077-b6fb-61d32f13f17f@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrea.porta@suse.com \
--cc=bcm-kernel-feedback-list@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