From: Rob Herring <robh@kernel.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Peter Robinson <pbrobinson@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Florian Fainelli <f.fainelli@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, Phil Elwell <phil@raspberrypi.com>,
Maxime Ripard <maxime@cerno.tech>,
Lee Jones <lee.jones@linaro.org>,
Scott Branden <sbranden@broadcom.com>,
Melissa Wen <melissa.srw@gmail.com>, Ray Jui <rjui@broadcom.com>
Subject: Re: [PATCH V3 03/11] dt-bindings: soc: bcm: bcm2835-pm: Add support for bcm2711
Date: Thu, 9 Jun 2022 14:42:32 -0600 [thread overview]
Message-ID: <20220609204232.GA66804-robh@kernel.org> (raw)
In-Reply-To: <20220607204226.8703-4-stefan.wahren@i2se.com>
On Tue, 07 Jun 2022 22:42:18 +0200, Stefan Wahren wrote:
> Add a new compatible string for BCM2711 and the option to provide a
> third reg property for the board's new RPiVid ASB.
>
> In BCM2711 the new RPiVid ASB took over V3D, which is our only consumer
> of this driver so far. The old ASB is still be present with ISP and H264
> bits but no V3D.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> Reviewed-by: Peter Robinson <pbrobinson@gmail.com>
> ---
> .../devicetree/bindings/soc/bcm/brcm,bcm2835-pm.yaml | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-06-09 20:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 20:42 [PATCH V3 00/11] soc: bcm2835-power: Prepare BCM2711 V3D support Stefan Wahren
2022-06-07 20:42 ` [PATCH V3 01/11] dt-bindings: soc: bcm: bcm2835-pm: Convert bindings to DT schema Stefan Wahren
2022-06-07 20:42 ` [PATCH V3 02/11] dt-bindings: soc: bcm: bcm2835-pm: Introduce reg-names Stefan Wahren
2022-06-07 20:42 ` [PATCH V3 03/11] dt-bindings: soc: bcm: bcm2835-pm: Add support for bcm2711 Stefan Wahren
2022-06-09 20:42 ` Rob Herring [this message]
2022-06-07 20:42 ` [PATCH V3 04/11] ARM: dts: bcm2835/bcm2711: Introduce reg-names in watchdog node Stefan Wahren
2022-06-07 20:42 ` [PATCH V3 05/11] ARM: dts: bcm2711: Use proper compatible in PM/Watchdog node Stefan Wahren
2022-06-07 20:42 ` [PATCH V3 06/11] mfd: bcm2835-pm: Use 'reg-names' to get resources Stefan Wahren
2022-06-23 8:27 ` Lee Jones
2022-06-07 20:42 ` [PATCH V3 07/11] mfd: bcm2835-pm: Add support for BCM2711 Stefan Wahren
2022-06-23 8:41 ` Lee Jones
2022-06-07 20:42 ` [PATCH V3 08/11] soc: bcm: bcm2835-power: Refactor ASB control Stefan Wahren
2022-06-07 20:42 ` [PATCH V3 09/11] soc: bcm: bcm2835-power: Resolve ASB register macros Stefan Wahren
2022-06-07 20:42 ` [PATCH V3 10/11] soc: bcm: bcm2835-power: Add support for BCM2711's RPiVid ASB Stefan Wahren
2022-06-07 20:42 ` [PATCH V3 11/11] soc: bcm: bcm2835-power: Bypass power_on/off() calls Stefan Wahren
2022-06-08 9:27 ` [PATCH V3 00/11] soc: bcm2835-power: Prepare BCM2711 V3D support Florian Fainelli
2022-06-15 17:38 ` Florian Fainelli
2022-06-23 2:02 ` Florian Fainelli
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=20220609204232.GA66804-robh@kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=melissa.srw@gmail.com \
--cc=pbrobinson@gmail.com \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
/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).