[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <F774B5D6-BC66-414A-B3E2-DED68FB59644@goldelico.com>
Date: Thu, 23 Nov 2023 10:04:42 +0100
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: frank.binns@...tec.com, matt.coster@...tec.com,
Donald Robson <donald.robson@...tec.com>
Cc: boris.brezillon@...labora.com, faith.ekstrand@...labora.com,
airlied@...il.com, daniel@...ll.ch,
maarten.lankhorst@...ux.intel.com, tzimmermann@...e.de, afd@...com,
matthew.brost@...el.com, christian.koenig@....com,
luben.tuikov@....com, dakr@...hat.com,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org,
corbet@....net, linux-doc@...r.kernel.org,
Maxime Ripard <mripard@...nel.org>,
Tony Lindgren <tony@...mide.com>,
dri-devel@...ts.freedesktop.org, openpvrsgx-devgroup@...ux.org,
kernel@...a-handheld.com
Subject: Re: [PATCH v9 00/20] Imagination Technologies PowerVR DRM driver
> Am 22.11.2023 um 20:34 schrieb Maxime Ripard <mripard@...nel.org>:
>
> Hi,
>
> On Wed, Nov 22, 2023 at 04:34:21PM +0000, Donald Robson 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 be found 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
>>
>> Vulkan driver links referred to above:
>> [1] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15243
>> [2] https://gitlab.freedesktop.org/mesa/mesa/-/tree/main/src/imagination/vulkan
>> [3] https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15507
>>
>> 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/frankbinns/powervr/-/tree/dev/v9_dts
>> The full development history can be found here:
>> https://gitlab.freedesktop.org/frankbinns/powervr/-/tree/powervr-next
>
> I just merged all the patches to drm-misc-next.
>
> Congrats :)
A big applause to the team that accomplished this!
Let me take this opportunity to ask if there could be a similar effort supported by imgtec
for the SGX drivers? There are still a lot of devices using this version of PVR in the wild,
like OpenPandora or Pyra Handheld, that are stuck with older Linux kernels (which are now
unmaintained) because there are no compatible SGX drivers for modern kernels.
And we have the openpvrsgx community that can definitely help with debugging (we all own
various OMAP and jz4780 devices), but we lack the documentation to actually develop and
upstream such a driver (and user-space code) ourselves.
Nikolaus
Powered by blists - more mailing lists