From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com
Cc: linux-rpi-kernel@lists.infradead.org, phil@raspberrypi.com,
wahrenst@gmx.net, mripard@kernel.org, eric@anholt.net,
robh@kernel.org, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: [PATCH v3 03/15] dt-bindings: soc: bcm: bcm2835-pm: Add support for bcm2711
Date: Wed, 17 Feb 2021 12:47:58 +0100 [thread overview]
Message-ID: <20210217114811.22069-4-nsaenzjulienne@suse.de> (raw)
In-Reply-To: <20210217114811.22069-1-nsaenzjulienne@suse.de>
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: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Reviewed-by: Rob Herring <robh@kernel.org>
---
Changes since v2:
- Correct names s/argon/rpivid/
.../devicetree/bindings/soc/bcm/brcm,bcm2835-pm.yaml | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-pm.yaml b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-pm.yaml
index 837963e9f219..0dd264f80fb3 100644
--- a/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-pm.yaml
+++ b/Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-pm.yaml
@@ -19,19 +19,22 @@ allOf:
properties:
compatible:
items:
- - const: brcm,bcm2835-pm
+ - enum:
+ - brcm,bcm2835-pm
+ - brcm,bcm2711-pm
- const: brcm,bcm2835-pm-wdt
reg:
minItems: 1
- maxItems: 2
+ maxItems: 3
reg-names:
minItems: 1
- maxItems: 2
+ maxItems: 3
items:
- const: pm
- const: asb
+ - const: rpivid_asb
"#power-domain-cells":
const: 1
@@ -74,7 +77,7 @@ examples:
#reset-cells = <1>;
reg = <0x7e100000 0x114>,
<0x7e00a000 0x24>;
- reg-names = "pm", "asb";
+ reg-names = "pm", "asb", "rpivid_asb";
clocks = <&clocks BCM2835_CLOCK_V3D>,
<&clocks BCM2835_CLOCK_PERI_IMAGE>,
<&clocks BCM2835_CLOCK_H264>,
--
2.30.0
next prev parent reply other threads:[~2021-02-17 11:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 11:47 [PATCH v3 00/15] Raspberry PI 4 V3D enablement Nicolas Saenz Julienne
2021-02-17 11:47 ` [PATCH v3 01/15] dt-bindings: soc: bcm: bcm2835-pm: Convert bindings to DT schema Nicolas Saenz Julienne
2021-03-05 22:28 ` Rob Herring
2021-02-17 11:47 ` [PATCH v3 02/15] dt-bindings: soc: bcm: bcm2835-pm: Introduce reg-names Nicolas Saenz Julienne
2021-03-05 22:28 ` Rob Herring
2021-02-17 11:47 ` Nicolas Saenz Julienne [this message]
2021-02-17 11:47 ` [PATCH v3 04/15] ARM: dts: bcm2835/bcm2711: Introduce reg-names in watchdog node Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 05/15] ARM: dts: bcm2711: Use proper compatible in PM/Watchdog node Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 06/15] mfd: bcm2835-pm: Use 'reg-names' to get resources Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 07/15] mfd: bcm2835-pm: Add support for BCM2711 Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 08/15] soc: bcm: bcm2835-power: Add support for BCM2711's RPiVid ASB Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 09/15] soc: bcm: bcm2835-power: Bypass power_on/off() calls Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 10/15] dt-bindings: gpu: v3d: Add BCM2711's compatible Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 11/15] drm/v3d: Get rid of pm code Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 12/15] drm/v3d: Add support for bcm2711 Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 13/15] ARM: dts: bcm2711: Enable V3D Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 14/15] ARM: configs: Enable DRM_V3D Nicolas Saenz Julienne
2021-02-17 11:48 ` [PATCH v3 15/15] arm64: config: " Nicolas Saenz Julienne
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=20210217114811.22069-4-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=wahrenst@gmx.net \
/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).