From: Florian Fainelli <f.fainelli@gmail.com>
To: Peter Robinson <pbrobinson@gmail.com>,
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>
Subject: Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement
Date: Wed, 8 Jun 2022 11:26:51 +0200 [thread overview]
Message-ID: <cadecbfd-e174-eadb-276c-577bb2bf70f2@gmail.com> (raw)
In-Reply-To: <20220603092610.1909675-1-pbrobinson@gmail.com>
On 6/3/2022 11:26 AM, Peter Robinson wrote:
> 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 v5:
> - Update the DT compatible to match the others that were updated
> - Adjust the Kconfig help text
> - Add review tags
>
> 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
I can take the last 3 patches through the Broadcom ARM SoC pull request,
but the first three should probably go via the DRM tree unless you want
me to merge them all?
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-08 9:28 UTC|newest]
Thread overview: 21+ 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 ` [PATCH v6 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible Peter Robinson
2022-06-03 9:26 ` [PATCH v6 2/6] drm/v3d: Get rid of pm code Peter Robinson
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 ` [PATCH v6 4/6] ARM: dts: bcm2711: Enable V3D Peter Robinson
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-13 17:08 ` Florian Fainelli
2022-06-03 9:26 ` [PATCH v6 6/6] arm64: config: " Peter Robinson
2022-06-13 17:08 ` Florian Fainelli
2022-06-08 9:26 ` Florian Fainelli [this message]
2022-06-08 12:23 ` [PATCH v6 0/6] Raspberry PI 4 V3D enablement Javier Martinez Canillas
2022-06-08 15:51 ` Melissa Wen
2022-06-08 16:48 ` Javier Martinez Canillas
2022-06-10 11:05 ` Melissa Wen
2022-06-10 12:13 ` Javier Martinez Canillas
2022-06-13 9:30 ` Melissa Wen
2022-06-08 12:51 ` Melissa Wen
2022-06-08 22:35 ` Stefan Wahren
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=cadecbfd-e174-eadb-276c-577bb2bf70f2@gmail.com \
--to=f.fainelli@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=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=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).