All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Robinson <pbrobinson@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>,
	bcm-kernel-feedback-list@broadcom.com,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Emma Anholt <emma@anholt.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	javierm@redhat.com, linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, maxime@cerno.tech,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: Peter Robinson <pbrobinson@gmail.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	Rob Herring <robh@kernel.org>
Subject: [PATCH v6 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible
Date: Fri,  3 Jun 2022 10:26:05 +0100	[thread overview]
Message-ID: <20220603092610.1909675-2-pbrobinson@gmail.com> (raw)
In-Reply-To: <20220603092610.1909675-1-pbrobinson@gmail.com>

BCM2711, Raspberry Pi 4's SoC, contains a V3D core. So add its specific
compatible to the bindings.

Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Reviewed-by: Stefan Wahren <stefan.wahren@i2se.com>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Acked-by: Rob Herring <robh@kernel.org>
---
Changes since v4:
- Change compatible to align downstream and other HW, reorder to suit

 Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
index e6485f7b046f..217c42874f41 100644
--- a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
+++ b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
@@ -16,6 +16,7 @@ properties:
 
   compatible:
     enum:
+      - brcm,2711-v3d
       - brcm,7268-v3d
       - brcm,7278-v3d
 
-- 
2.36.1


WARNING: multiple messages have this Message-ID (diff)
From: Peter Robinson <pbrobinson@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>,
	bcm-kernel-feedback-list@broadcom.com,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Emma Anholt <emma@anholt.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	javierm@redhat.com, linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, maxime@cerno.tech,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: Peter Robinson <pbrobinson@gmail.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: [PATCH v6 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible
Date: Fri,  3 Jun 2022 10:26:05 +0100	[thread overview]
Message-ID: <20220603092610.1909675-2-pbrobinson@gmail.com> (raw)
In-Reply-To: <20220603092610.1909675-1-pbrobinson@gmail.com>

BCM2711, Raspberry Pi 4's SoC, contains a V3D core. So add its specific
compatible to the bindings.

Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Reviewed-by: Stefan Wahren <stefan.wahren@i2se.com>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Acked-by: Rob Herring <robh@kernel.org>
---
Changes since v4:
- Change compatible to align downstream and other HW, reorder to suit

 Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
index e6485f7b046f..217c42874f41 100644
--- a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
+++ b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
@@ -16,6 +16,7 @@ properties:
 
   compatible:
     enum:
+      - brcm,2711-v3d
       - brcm,7268-v3d
       - brcm,7278-v3d
 
-- 
2.36.1


WARNING: multiple messages have this Message-ID (diff)
From: Peter Robinson <pbrobinson@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>,
	bcm-kernel-feedback-list@broadcom.com,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Emma Anholt <emma@anholt.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	javierm@redhat.com, linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, maxime@cerno.tech,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: Peter Robinson <pbrobinson@gmail.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	Rob Herring <robh@kernel.org>
Subject: [PATCH v6 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible
Date: Fri,  3 Jun 2022 10:26:05 +0100	[thread overview]
Message-ID: <20220603092610.1909675-2-pbrobinson@gmail.com> (raw)
In-Reply-To: <20220603092610.1909675-1-pbrobinson@gmail.com>

BCM2711, Raspberry Pi 4's SoC, contains a V3D core. So add its specific
compatible to the bindings.

Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Reviewed-by: Stefan Wahren <stefan.wahren@i2se.com>
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Acked-by: Rob Herring <robh@kernel.org>
---
Changes since v4:
- Change compatible to align downstream and other HW, reorder to suit

 Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
index e6485f7b046f..217c42874f41 100644
--- a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
+++ b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
@@ -16,6 +16,7 @@ properties:
 
   compatible:
     enum:
+      - brcm,2711-v3d
       - brcm,7268-v3d
       - brcm,7278-v3d
 
-- 
2.36.1


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

  reply	other threads:[~2022-06-03  9:26 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  9:26 [PATCH v6 0/6] Raspberry PI 4 V3D enablement Peter Robinson
2022-06-03  9:26 ` Peter Robinson
2022-06-03  9:26 ` Peter Robinson [this message]
2022-06-03  9:26   ` [PATCH v6 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26 ` [PATCH v6 2/6] drm/v3d: Get rid of pm code Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03 11:29   ` Melissa Wen
2022-06-03 11:29     ` Melissa Wen
2022-06-03 11:29     ` Melissa Wen
2022-06-03  9:26 ` [PATCH v6 3/6] drm/v3d: Add support for bcm2711 Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26 ` [PATCH v6 4/6] ARM: dts: bcm2711: Enable V3D Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:07   ` Florian Fainelli
2022-06-13 17:07     ` Florian Fainelli
2022-06-03  9:26 ` [PATCH v6 5/6] ARM: configs: Enable DRM_V3D Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:08   ` Florian Fainelli
2022-06-13 17:08     ` Florian Fainelli
2022-06-03  9:26 ` [PATCH v6 6/6] arm64: config: " Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:08   ` Florian Fainelli
2022-06-13 17:08     ` Florian Fainelli
2022-06-08  9:26 ` [PATCH v6 0/6] Raspberry PI 4 V3D enablement Florian Fainelli
2022-06-08  9:26   ` Florian Fainelli
2022-06-08 12:23   ` Javier Martinez Canillas
2022-06-08 12:23     ` Javier Martinez Canillas
2022-06-08 15:51     ` Melissa Wen
2022-06-08 15:51       ` Melissa Wen
2022-06-08 15:51       ` Melissa Wen
2022-06-08 16:48       ` Javier Martinez Canillas
2022-06-08 16:48         ` Javier Martinez Canillas
2022-06-08 16:48         ` Javier Martinez Canillas
2022-06-10 11:05         ` Melissa Wen
2022-06-10 11:05           ` Melissa Wen
2022-06-10 11:05           ` Melissa Wen
2022-06-10 12:13           ` Javier Martinez Canillas
2022-06-10 12:13             ` Javier Martinez Canillas
2022-06-10 12:13             ` Javier Martinez Canillas
2022-06-13  9:30             ` Melissa Wen
2022-06-13  9:30               ` Melissa Wen
2022-06-13  9:30               ` Melissa Wen
2022-06-08 12:51 ` Melissa Wen
2022-06-08 12:51   ` Melissa Wen
2022-06-08 12:51   ` Melissa Wen
2022-06-08 22:35   ` Stefan Wahren
2022-06-08 22:35     ` Stefan Wahren
2022-06-08 22:35     ` Stefan Wahren
2022-06-10 10:39     ` Melissa Wen
2022-06-10 10:39       ` Melissa Wen
2022-06-10 10:39       ` Melissa Wen

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=20220603092610.1909675-2-pbrobinson@gmail.com \
    --to=pbrobinson@gmail.com \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=catalin.marinas@arm.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=javierm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=maxime@cerno.tech \
    --cc=nsaenz@kernel.org \
    --cc=nsaenzjulienne@suse.de \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=stefan.wahren@i2se.com \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.