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>
Subject: [PATCH v5 0/6] Raspberry PI 4 V3D enablement
Date: Wed, 1 Jun 2022 12:02:43 +0100 [thread overview]
Message-ID: <20220601110249.569540-1-pbrobinson@gmail.com> (raw)
This is a follow up from my v4 patchset. The power management pieces have
been split out to a separate independent set of patches by Stefan [1]. This
version 5 of the DRM patches are independent and given the V3D driver has
been upstream for some time the two patches to enable it in defconfigs can
be taken at anytime independent of the enablement for the Raspberry Pi 4.
I've tested this using mesa 22.0.x and Wayland/Gnome on Fedora 36, it's
more or less stable with basic testing.
Changes since v4:
- Fixes for device tree and bindings
- Split out the power management changes into an independent set
- Rebase to 5.18
- Individual changes in patches
[1] https://www.spinics.net/lists/arm-kernel/msg980342.html
Nicolas Saenz Julienne (1):
arm64: config: Enable DRM_V3D
Peter Robinson (5):
dt-bindings: gpu: v3d: Add BCM2711's compatible
drm/v3d: Get rid of pm code
drm/v3d: Add support for bcm2711
ARM: dts: bcm2711: Enable V3D
ARM: configs: Enable DRM_V3D
.../devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 1 +
arch/arm/boot/dts/bcm2711-rpi.dtsi | 4 ++++
arch/arm/boot/dts/bcm2711.dtsi | 11 +++++++++++
arch/arm/configs/bcm2835_defconfig | 1 +
arch/arm/configs/multi_v7_defconfig | 1 +
arch/arm64/configs/defconfig | 1 +
drivers/gpu/drm/v3d/Kconfig | 2 +-
drivers/gpu/drm/v3d/v3d_debugfs.c | 18 +-----------------
drivers/gpu/drm/v3d/v3d_drv.c | 12 +-----------
drivers/gpu/drm/v3d/v3d_gem.c | 12 +-----------
10 files changed, 23 insertions(+), 40 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-01 11:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 11:02 Peter Robinson [this message]
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
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=20220601110249.569540-1-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=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).