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

On Wed, 01 Jun 2022 12:02:44 +0100, Peter Robinson wrote:
> 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>
> ---
> Changes since v5:
> - Change compatible to align downstream and othee HW, reorder to suit
> 
>  Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2022-06-02 14:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 11:02 [PATCH v5 0/6] Raspberry PI 4 V3D enablement Peter Robinson
2022-06-01 11:02 ` [PATCH v5 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible Peter Robinson
2022-06-02 11:58   ` Stefan Wahren
2022-06-02 14:49   ` Rob Herring [this message]
2022-06-02 22:56   ` Javier Martinez Canillas
2022-06-01 11:02 ` [PATCH v5 2/6] drm/v3d: Get rid of pm code Peter Robinson
2022-06-02 22:59   ` Javier Martinez Canillas
2022-06-03  7:07   ` nicolas saenz julienne
2022-06-01 11:02 ` [PATCH v5 3/6] drm/v3d: Add support for bcm2711 Peter Robinson
2022-06-02 12:00   ` Stefan Wahren
2022-06-02 23:05   ` Javier Martinez Canillas
2022-06-01 11:02 ` [PATCH v5 4/6] ARM: dts: bcm2711: Enable V3D Peter Robinson
2022-06-02 12:04   ` Stefan Wahren
2022-06-02 13:32     ` Peter Robinson
2022-06-02 23:07   ` Javier Martinez Canillas
2022-06-01 11:02 ` [PATCH v5 5/6] ARM: configs: Enable DRM_V3D Peter Robinson
2022-06-02 11:48   ` Stefan Wahren
2022-06-02 23:09   ` Javier Martinez Canillas
2022-06-01 11:02 ` [PATCH v5 6/6] arm64: config: " Peter Robinson
2022-06-02 12:05   ` Stefan Wahren
2022-06-02 23:10   ` Javier Martinez Canillas

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=20220602144946.GA2296795-robh@kernel.org \
    --to=robh@kernel.org \
    --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=pbrobinson@gmail.com \
    --cc=robh+dt@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 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).