From: Frank Binns <Frank.Binns@imgtec.com>
To: "mripard@kernel.org" <mripard@kernel.org>,
"faith.ekstrand@collabora.com" <faith.ekstrand@collabora.com>,
Sarah Walker <Sarah.Walker@imgtec.com>
Cc: "corbet@lwn.net" <corbet@lwn.net>,
"luben.tuikov@amd.com" <luben.tuikov@amd.com>,
"christian.koenig@amd.com" <christian.koenig@amd.com>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"dakr@redhat.com" <dakr@redhat.com>,
"hns@goldelico.com" <hns@goldelico.com>,
"afd@ti.com" <afd@ti.com>, "daniel@ffwll.ch" <daniel@ffwll.ch>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"boris.brezillon@collabora.com" <boris.brezillon@collabora.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"matthew.brost@intel.com" <matthew.brost@intel.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"airlied@gmail.com" <airlied@gmail.com>
Subject: Re: [PATCH v8 00/20] Imagination Technologies PowerVR DRM driver
Date: Wed, 1 Nov 2023 10:15:15 +0000 [thread overview]
Message-ID: <eb0dcfe7a5f4da207bdbbd9630e5d6e5c940dfa5.camel@imgtec.com> (raw)
In-Reply-To: <lg7cdw3qlak74zefbx25f5pnazrburteldueoqz7o7cphydqp7@q56er3qa5muf>
Hi Maxime,
On Tue, 2023-10-31 at 17:31 +0100, Maxime Ripard wrote:
> Hi Sarah, Faith, Frank,
>
> On Tue, Oct 31, 2023 at 03:12:37PM +0000, Sarah Walker wrote:
> > This patch series adds the initial DRM driver for Imagination Technologies PowerVR
> > GPUs, starting with those based on our Rogue architecture. It's worth pointing
> > out that this is a new driver, written from the ground up, rather than a
> > refactored version of our existing downstream driver (pvrsrvkm).
> >
> > This new DRM driver supports:
> > - GEM shmem allocations
> > - dma-buf / PRIME
> > - Per-context userspace managed virtual address space
> > - DRM sync objects (binary and timeline)
> > - Power management suspend / resume
> > - GPU job submission (geometry, fragment, compute, transfer)
> > - META firmware processor
> > - MIPS firmware processor
> > - GPU hang detection and recovery
> >
> > Currently our main focus is on the AXE-1-16M GPU. Testing so far has been done
> > using a TI SK-AM62 board (AXE-1-16M GPU). The driver has also been confirmed to
> > work on the BeaglePlay board. Firmware for the AXE-1-16M can befound here:
> > https://gitlab.freedesktop.org/frankbinns/linux-firmware/-/tree/powervr
> >
> > A Vulkan driver that works with our downstream kernel driver has already been
> > merged into Mesa [1][2]. Support for this new DRM driver is being maintained in
> > a merge request [3], with the branch located here:
> > https://gitlab.freedesktop.org/frankbinns/mesa/-/tree/powervr-winsys
> >
> > Job stream formats are documented at:
> > https://gitlab.freedesktop.org/mesa/mesa/-/blob/f8d2b42ae65c2f16f36a43e0ae39d288431e4263/src/imagination/csbgen/rogue_kmd_stream.xml
> >
> > The Vulkan driver is progressing towards Vulkan 1.0. The current combination of this
> > kernel driver with the Mesa Vulkan driver (powervr-mesa-next branch) successfully
> > completes Vulkan CTS 1.3.4.1 in our local runs. The driver is expected to pass the
> > Khronos Conformance Process once the submission is made.
> >
> > The code in this patch series, along with the needed dts changes can be found here:
> > https://gitlab.freedesktop.org/sarah-walker-imgtec/powervr/-/tree/dev/v8_dts
> > The full development history can be found here:
> > https://gitlab.freedesktop.org/frankbinns/powervr/-/tree/powervr-next
>
> Awesome, thanks for sending a new version of that series.
>
> At XDC, we all agreed that we would merge this version if the changes
> requested by Faith were fixed, and if the Mesa PR was updated to match
> that new kernel series.
>
> Are we there yet?
We've made all the changes that were requested at XDC. There are a couple of
questions Faith had for me that I still need to respond to. I'll hopefully be
getting to these today.
The Mesa MR adding support for this kernel driver is all up to date:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15507
>
> If so, Faith, should we add your Reviewed-by/Acked-by tag to the UAPI patch?
>
> > This patch series has dependencies on a number of patches not yet merged. They
> > are listed below :
> >
> > drm/sched: Convert drm scheduler to use a work queue rather than kthread:
> > https://lore.kernel.org/dri-devel/20230404002211.3611376-2-matthew.brost@intel.com/
> > drm/sched: Move schedule policy to scheduler / entity:
> > https://lore.kernel.org/dri-devel/20230404002211.3611376-3-matthew.brost@intel.com/
> > drm/sched: Add DRM_SCHED_POLICY_SINGLE_ENTITY scheduling policy:
> > https://lore.kernel.org/dri-devel/20230404002211.3611376-4-matthew.brost@intel.com/
> > drm/sched: Start run wq before TDR in drm_sched_start:
> > https://lore.kernel.org/dri-devel/20230404002211.3611376-6-matthew.brost@intel.com/
> > drm/sched: Submit job before starting TDR:
> > https://lore.kernel.org/dri-devel/20230404002211.3611376-7-matthew.brost@intel.com/
> > drm/sched: Add helper to set TDR timeout:
> > https://lore.kernel.org/dri-devel/20230404002211.3611376-8-matthew.brost@intel.com/
>
> What is the state of those patches? Iirc, we were expecting them to be
> merged soon at XDC
I see there was a new version posted yesterday:
https://lists.freedesktop.org/archives/dri-devel/2023-October/428612.html
It looks pretty close now. We'll rebase our patches so hopefully we have a
trivial rebase once they get merged.
Thanks
Frank
>
> Thanks,
> Maxime
next prev parent reply other threads:[~2023-11-01 10:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 15:12 Sarah Walker
2023-10-31 15:12 ` [PATCH v8 01/20] sizes.h: Add entries between SZ_32G and SZ_64T Sarah Walker
2023-10-31 15:12 ` [PATCH v8 02/20] drm/gpuvm: Helper to get range of unmap from a remap op Sarah Walker
2023-11-14 16:42 ` Danilo Krummrich
2023-11-20 11:07 ` [EXTERNAL] " Donald Robson
2023-10-31 15:12 ` [PATCH v8 03/20] dt-bindings: gpu: Add Imagination Technologies PowerVR/IMG GPU Sarah Walker
2023-10-31 15:12 ` [PATCH v8 04/20] drm/imagination/uapi: Add PowerVR driver UAPI Sarah Walker
2023-11-06 14:51 ` Faith Ekstrand
2023-10-31 15:12 ` [PATCH v8 05/20] drm/imagination: Add skeleton PowerVR driver Sarah Walker
2023-10-31 15:12 ` [PATCH v8 06/20] drm/imagination: Get GPU resources Sarah Walker
2023-10-31 15:12 ` [PATCH v8 07/20] drm/imagination: Add GPU register headers Sarah Walker
2023-10-31 15:12 ` [PATCH v8 08/20] drm/imagination: Add firmware and MMU related headers Sarah Walker
2023-10-31 15:12 ` [PATCH v8 09/20] drm/imagination: Add FWIF headers Sarah Walker
2023-10-31 15:12 ` [PATCH v8 10/20] drm/imagination: Add GPU ID parsing and firmware loading Sarah Walker
2023-10-31 15:12 ` [PATCH v8 11/20] drm/imagination: Add GEM and VM related code Sarah Walker
2023-10-31 15:12 ` [PATCH v8 12/20] drm/imagination: Implement power management Sarah Walker
2023-10-31 15:12 ` [PATCH v8 13/20] drm/imagination: Implement firmware infrastructure and META FW support Sarah Walker
2023-10-31 15:12 ` [PATCH v8 14/20] drm/imagination: Implement MIPS firmware processor and MMU support Sarah Walker
2023-10-31 15:12 ` [PATCH v8 15/20] drm/imagination: Implement free list and HWRT create and destroy ioctls Sarah Walker
2023-10-31 15:12 ` [PATCH v8 16/20] drm/imagination: Implement context creation/destruction ioctls Sarah Walker
2023-10-31 15:12 ` [PATCH v8 17/20] drm/imagination: Implement job submission and scheduling Sarah Walker
2023-10-31 15:12 ` [PATCH v8 18/20] drm/imagination: Add firmware trace header Sarah Walker
2023-10-31 15:12 ` [PATCH v8 19/20] drm/imagination: Add firmware trace to debugfs Sarah Walker
2023-10-31 15:12 ` [PATCH v8 20/20] drm/imagination: Add driver documentation Sarah Walker
2023-10-31 16:31 ` [PATCH v8 00/20] Imagination Technologies PowerVR DRM driver Maxime Ripard
2023-11-01 10:15 ` Frank Binns [this message]
2023-11-06 9:43 ` mripard
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=eb0dcfe7a5f4da207bdbbd9630e5d6e5c940dfa5.camel@imgtec.com \
--to=frank.binns@imgtec.com \
--cc=Sarah.Walker@imgtec.com \
--cc=afd@ti.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=christian.koenig@amd.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=faith.ekstrand@collabora.com \
--cc=hns@goldelico.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®