Le 21/09/2024 à 06:33, Ryosuke Yasuoka a écrit :
QXL supports the drm_panic module, which displays a message to the
screen when a kernel panic occurs.
Signed-off-by: Ryosuke Yasuoka
---
Hi,
a few comments/nitpicks below, if of interest.
diff --git a/drivers/gpu/drm/qxl/qxl_cmd.c b/drivers/
QXL supports the drm_panic module, which displays a message to the
screen when a kernel panic occurs.
Signed-off-by: Ryosuke Yasuoka
---
v3
Adjust function's arguments indentation. Discussion v2 patch is in [2]
[2] https://lore.kernel.org/lkml/20240919071230.840994-1-ryasu...@redhat.com/T/
v2
I
Hi All,
The lastest Git kernel doesn't boot anymore after the latest DRM updates
(drm-next-2024-09-19). [1]
I tested it with an AMD Radeon HD 6970 (Cayman XT) and with an AMD
Radeon HD 5870 (Cypress XT).
I reverted the DRM updates and after that the kernel boots without any
problems.
Ple
On Thu, 19 Sep 2024 14:45:47 +0530, Manikandan Muralidharan wrote:
> Add Microchip AC69T88A 5" LVDS interface (800x480) TFT LCD panel
> compatible string
>
> Signed-off-by: Manikandan Muralidharan
> ---
> changes in v2:
> - Replace microchip,ac69t88a-lvds-panel with
> microchip,ac69t88a
> ---
>
Hi Huan,
> Subject: [PATCH v7 0/7] udmabuf bug fix and some improvements
>
> This patchset attempts to fix some errors in udmabuf and remove the
> upin_list structure, also try clean up code.
>
> By this patchset, udmabuf remove page struct relay, only use
> pfn and folios.
>
> Some of this fix
Drawing from the FW-calculated values in a previous commit, we can increase
the numbers for an open file by collecting them from finished jobs when
updating their group synchronisation objects.
Display of fdinfo key-value pairs is governed by a bitmask that is by
default unset in the present commi
Implement drm object's status callback.
Also, we consider a PRIME imported BO to be resident if its matching
dma_buf has an open attachment, which means its backing storage had already
been allocated.
Signed-off-by: Adrián Larumbe
Reviewed-by: Steven Price
Reviewed-by: Liviu Dudau
Reviewed-by:
This commit introduces a DRM device sysfs attribute that lets UM control
the job accounting status in the device. The knob variable had been brought
in as part of a previous commit, but now we're able to fix it manually.
As sysfs files are part of a driver's uAPI, describe its legitimate input
val
In order to support UM in calculating rates of GPU utilisation, the current
operating and maximum GPU clock frequencies must be recorded during device
initialisation, and also during OPP state transitions.
Signed-off-by: Adrián Larumbe
---
drivers/gpu/drm/panthor/panthor_devfreq.c | 18 +
Enable calculations of job submission times in clock cycles and wall
time. This is done by expanding the boilerplate command stream when running
a job to include instructions that compute said times right before and
after a user CS.
A separate kernel BO is created per queue to store those values.
This patch series enables userspace utilities like gputop and nvtop to
query a render context's fdinfo file and figure out rates of engine
and memory utilisation.
Previous discussion can be found at
https://lore.kernel.org/dri-devel/20240913124857.389630-1-adrian.laru...@collabora.com/
Changelog:
Hi Steve, thanks for the review.
I've applied all of your suggestions for the next patch series revision, so I'll
only be answering to your question about the calc_profiling_ringbuf_num_slots
function further down below.
On 16.09.2024 12:15, Steven Price wrote:
> On 13/09/2024 13:42, Adrián Larum
On Fri, Sep 20, 2024 at 05:50:10PM -0400, Felix Kuehling wrote:
>
> On 2024-09-20 17:23, Matthew Brost wrote:
> > On Fri, Sep 20, 2024 at 04:26:50PM -0400, Felix Kuehling wrote:
> > > On 2024-09-18 11:10, Alistair Popple wrote:
> > > > Matthew Brost writes:
> > > >
> > > > > On Wed, Sep 11, 2024
On 2024-09-20 17:23, Matthew Brost wrote:
On Fri, Sep 20, 2024 at 04:26:50PM -0400, Felix Kuehling wrote:
On 2024-09-18 11:10, Alistair Popple wrote:
Matthew Brost writes:
On Wed, Sep 11, 2024 at 02:53:31PM +1000, Alistair Popple wrote:
Matthew Brost writes:
I haven't seen the same in t
On Fri, Sep 20, 2024 at 04:26:50PM -0400, Felix Kuehling wrote:
> On 2024-09-18 11:10, Alistair Popple wrote:
> > Matthew Brost writes:
> >
> > > On Wed, Sep 11, 2024 at 02:53:31PM +1000, Alistair Popple wrote:
> > > > Matthew Brost writes:
> > > >
> > > > I haven't seen the same in the NVIDIA
On 2024-09-20 01:56, Jani Nikula wrote:
> On Thu, 19 Sep 2024, Fangzhi Zuo wrote:
>> [why]
>> How we determine the dsc_aux used for dsc decompression in
>> drm_dp_mst_dsc_aux_for_port() today having some defects:
>>
>> 1. The method how we determine a connected peer device is virtual or not
>>
On 2024-09-18 11:10, Alistair Popple wrote:
Matthew Brost writes:
On Wed, Sep 11, 2024 at 02:53:31PM +1000, Alistair Popple wrote:
Matthew Brost writes:
I haven't seen the same in the NVIDIA UVM driver (out-of-tree, I know)
Still a driver.
Indeed, and I'm happy to answer any questions abo
On Fri, Sep 20, 2024 at 9:54 AM Akhil P Oommen wrote:
>
> On Tue, Sep 17, 2024 at 01:14:19PM +0200, Antonino Maniscalco wrote:
> > Some userspace changes are necessary so add a flag for userspace to
> > advertise support for preemption when creating the submitqueue.
> >
> > When this flag is not s
On Fri, Sep 20, 2024 at 9:15 AM Akhil P Oommen wrote:
>
> On Wed, Sep 18, 2024 at 08:39:30AM -0700, Rob Clark wrote:
> > On Wed, Sep 18, 2024 at 12:46 AM Neil Armstrong
> > wrote:
> > >
> > > Hi,
> > >
> > > On 17/09/2024 13:14, Antonino Maniscalco wrote:
> > > > This series implements preemption
On Wed, Sep 18, 2024 at 12:31:55AM +0300, Dmitry Baryshkov wrote:
> On Wed, Sep 18, 2024 at 02:08:41AM GMT, Akhil P Oommen wrote:
> > From: Puranam V G Tejaswi
> >
> > Add support for Adreno 663 found on sa8775p based platforms.
> >
> > Signed-off-by: Puranam V G Tejaswi
> > Signed-off-by: Akhi
On Wed, Sep 18, 2024 at 09:46:33AM +0200, Neil Armstrong wrote:
> Hi,
>
> On 17/09/2024 13:14, Antonino Maniscalco wrote:
> > This series implements preemption for A7XX targets, which allows the GPU to
> > switch to an higher priority ring when work is pushed to it, reducing
> > latency
> > for h
On Tue, Sep 17, 2024 at 01:14:20PM +0200, Antonino Maniscalco wrote:
> Initialize with 4 rings to enable preemption.
>
> For now only on A750 as other targets require testing.
>
> Add the "preemption_enabled" module parameter to override this for other
> A7xx targets.
>
> Signed-off-by: Antonino
On Tue, Sep 17, 2024 at 01:14:19PM +0200, Antonino Maniscalco wrote:
> Some userspace changes are necessary so add a flag for userspace to
> advertise support for preemption when creating the submitqueue.
>
> When this flag is not set preemption will not be allowed in the middle
> of the submitted
On Tue, Sep 17, 2024 at 01:14:18PM +0200, Antonino Maniscalco wrote:
> Add trace points corresponding to preemption being triggered and being
> completed for latency measurement purposes.
>
> Signed-off-by: Antonino Maniscalco
> Tested-by: Neil Armstrong # on SM8650-QRD
Reviewed-by: Akhil P Oom
On Tue, Sep 17, 2024 at 01:14:17PM +0200, Antonino Maniscalco wrote:
> Use the postamble to reset perf counters when switching between rings,
> except when sysprof is enabled, analogously to how they are reset
> between submissions when switching pagetables.
>
> Signed-off-by: Antonino Maniscalco
On Tue, Sep 17, 2024 at 01:14:15PM +0200, Antonino Maniscalco wrote:
> This patch implements preemption feature for A6xx targets, this allows
> the GPU to switch to a higher priority ringbuffer if one is ready. A6XX
> hardware as such supports multiple levels of preemption granularities,
> ranging
On Tue, Sep 17, 2024 at 12:47:10PM GMT, Tejas Vipin wrote:
> Changes the elida-kd35t133 panel to use multi style functions for
> improved error handling.
>
> Signed-off-by: Tejas Vipin
> ---
> drivers/gpu/drm/panel/panel-elida-kd35t133.c | 107 ---
> 1 file changed, 45 insertions
On Wed, Sep 18, 2024 at 10:33:57AM GMT, Yang Li wrote:
> ./drivers/gpu/drm/msm/hdmi/hdmi_phy_8998.c:282:2-3: Unneeded semicolon
>
> This patch removes an unneeded semicolon after a switch statement in the
> pll_get_post_div function. Adding a semicolon after a switch statement is
> unnecessary a
On Wed, Sep 18, 2024 at 03:48:41PM GMT, Chen Ni wrote:
> There is no need to call the dev_err() function directly to print a
> custom message when handling an error from platform_get_irq() function
> as it is going to display an appropriate error message in case of a
> failure.
>
> Signed-off-by:
On Wed, Sep 18, 2024 at 04:01:17PM GMT, Manikandan Muralidharan wrote:
> Add the Microchip's DSI controller wrapper driver that uses
> the Synopsys DesignWare MIPI DSI host controller bridge.
>
> Signed-off-by: Manikandan Muralidharan
> ---
> changes in v4:
> - Fixed issues reported by kernel tes
On Wed, Sep 18, 2024 at 08:39:30AM -0700, Rob Clark wrote:
> On Wed, Sep 18, 2024 at 12:46 AM Neil Armstrong
> wrote:
> >
> > Hi,
> >
> > On 17/09/2024 13:14, Antonino Maniscalco wrote:
> > > This series implements preemption for A7XX targets, which allows the GPU
> > > to
> > > switch to an high
Hi,
I simplified the C reproducer as follows:
#include
#include
#include
#include
#include
#include
#include
#include
struct param {
uint8_t type;
struct tiocl_selection ts;
};
int main()
{
write(1, "executing program\n", sizeof("executing program\n") - 1);
On Fri, Sep 20, 2024 at 01:27:54PM GMT, Pin-yen Lin wrote:
> On Thu, Sep 19, 2024 at 10:58 AM wrote:
> >
> > From: Hermes Wu
> >
> > Fix HDCP CTS items on UNIGRAF DPR-100.
> >
> > Signed-off-by: Hermes Wu
>
> Reviewed-by: Pin-yen Lin
For the sake of somebody applying the patch because it was
On Thu, Sep 19, 2024 at 02:45:48PM GMT, Manikandan Muralidharan wrote:
> Add support for Microchip AC69T88A 5 inch TFT LCD 800x480
> Display module with LVDS interface.The panel uses the Sitronix
> ST7262 800x480 Display driver
AC69T88A seems to be a module name, rather than a panel name. What is
On 17/09/2024 15:21, Alex Deucher wrote:
On Mon, Aug 12, 2024 at 2:10 AM Lu Yao wrote:
Add support for the drm_panic module, which displays a pretty user
friendly message on the screen when a Linux kernel panic occurs.
Signed-off-by: Lu Yao
Patch looks good to me. Any chance you want to c
On Fri, Sep 20, 2024 at 04:24:51PM GMT, Hermes Wu wrote:
> From: Hermes Wu
>
> add AUX-I2C functionality to support MCCS
>
> Signed-off-by: Hermes Wu
> ---
> drivers/gpu/drm/bridge/ite-it6505.c | 209 ++--
> 1 file changed, 200 insertions(+), 9 deletions(-)
>
All my co
On Fri, Sep 20, 2024 at 04:24:50PM GMT, Hermes Wu wrote:
> From: Hermes Wu
>
> Fix HDCP CTS items on UNIGRAF DPR-100
>
> Signed-off-by: Hermes Wu
All my comments from v1 (except for the Changes-Id trailers) seem to
apply as well.
> ---
> drivers/gpu/drm/bridge/ite-it6505.c | 152
On Fri, Sep 20, 2024 at 04:24:49PM GMT, Hermes Wu wrote:
> From: Hermes Wu
>
> This series change aux function to support MCCS and fix HDCP CTS
It is v2, but where is the changelog?
Also please give reviewers some time and don't next revisions too
quickly.
Last, but not least, new series = new
On Fri, Sep 20, 2024 at 04:24:47PM GMT, Hermes Wu wrote:
> From: "Hermes.Wu"
>
> add AUX-I2C functionality to support MCCS.
Same comment regarding the commit message.
>
> Change-Id: I63e1a0e5da67526f89f35605a82944be67dee8ac
No Gerrit
> Signed-off-by: Hermes Wu
> ---
> drivers/gpu/drm/brid
On Fri, Sep 20, 2024 at 04:24:46PM GMT, Hermes Wu wrote:
> From: allen chen
>
> Fix HDCP CTS items on UNIGRAF DPR-100.
Fix how? What was broken? Please describe the reasoning for the change.
Also if it a fix, please use Fixes tags as required. If you have
further questions, see Documentation/pro
On Do, 2024-09-12 at 16:30 +0800, Jinjie Ruan wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable when request IRQ.
>
> Fixes: 47b1be5c0f4e ("staging: imx/drm: request irq only after a
+Cc: Kees
On Fri, Sep 20, 2024 at 02:18:19PM +0300, Raag Jadav wrote:
> On Thu, Sep 19, 2024 at 04:45:28PM +0300, Andy Shevchenko wrote:
> > On Thu, Sep 19, 2024 at 11:38:50AM +0300, Raag Jadav wrote:
> > > On Thu, Sep 19, 2024 at 10:38:51AM +0300, Jani Nikula wrote:
...
> > > Anyway, would you
On Sat, Aug 31, 2024 at 09:06:39PM GMT, Stephen Boyd wrote:
> Add support to the DRM atomic logic to support lane remapping between
> bridges, encoders and connectors. Typically lane mapping is handled
> statically in firmware, e.g. on DT we use the data-lanes property to
> assign lanes when connec
On Fri, 2024-09-20 at 12:33 +0200, Christian König wrote:
> Am 20.09.24 um 10:57 schrieb Philipp Stanner:
> > On Wed, 2024-09-18 at 15:39 +0200, Christian König wrote:
> > > Tearing down the scheduler with jobs still on the pending list
> > > can
> > > lead to use after free issues. Add a warning i
On 20/09/2024 11:28, Liviu Dudau wrote:
> Since 641bb4394f40 ("fs: move FMODE_UNSIGNED_OFFSET to fop_flags")
> the FMODE_UNSIGNED_OFFSET flag has been moved to fop_flags and renamed,
> but the patch failed to make the changes for the panthor driver.
> When user space opens the render node the WARN(
Hi Daniel,
On 21/08/2024 15:37, Daniel Almeida wrote:
This is of interest to userspace, and similar in nature to the GPU
and CSIF information we already return in the query ioctl.
Signed-off-by: Daniel Almeida
---
drivers/gpu/drm/panthor/panthor_device.h | 3 +++
drivers/gpu/drm/panthor/pa
On Thu, Sep 12, 2024 at 04:30:17PM +0800, Jinjie Ruan wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable when request IRQ.
>
> Fixes: 9021c317b770 ("drm/imx: Add initial support for D
Hi Jinjie,
On Thu, Sep 12, 2024 at 04:30:16PM +0800, Jinjie Ruan wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable when request IRQ.
>
> Fixes: 9021c317b770 ("drm/imx: Add initial s
Hello Daniel,
On Thu, 19 Sep 2024 14:43:23 +0200
Daniel Thompson wrote:
> On Tue, Sep 17, 2024 at 10:53:10AM +0200, Luca Ceresoli wrote:
> > led-backlight is a consumer of one or multiple LED class devices, but no
> > devlink is created for such supplier-producer relationship. One consequence
>
On 19/09/2024 17:11, Kaustabh Chakraborty wrote:
> decon_commit() gets called during atomic_enable. At this stage, DECON is
> suspended, and thus the function refuses to run. Fix the suspended
> condition checking in decon_commit().
>
> Signed-off-by: Kaustabh Chakraborty
> ---
If this is a fix,
On 19/09/2024 17:20, Kaustabh Chakraborty wrote:
> Add the compatible string of Exynos7870 to the existing list.
>
> Signed-off-by: Kaustabh Chakraborty
... and the DTS is ?
Acked-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On Tue, Aug 06, 2024 at 10:52:59AM GMT, André Almeida wrote:
> Currently, DRM atomic uAPI allows only primary planes to be flipped
> asynchronously. However, each driver might be able to perform async
> flips in other different plane types. To enable drivers to set their own
> restrictions on which
On 2024-09-20 09:04, neil.armstr...@linaro.org wrote:
> On 19/09/2024 22:34, Jonas Karlman wrote:
>> Hi Neil,
>>
>> On 2024-09-13 10:02, Neil Armstrong wrote:
>>> On 08/09/2024 15:28, Jonas Karlman wrote:
Update successfully read EDID during hotplug processing to ensure the
connector dipl
Am 20.09.24 um 11:06 schrieb Pierre-Eric Pelloux-Prayer:
If a drm_file name is set append it to the process name.
This information is useful with the virtio/native-context driver: this
allows the guest applications identifier to visible in amdgpu's output.
The output in amdgpu_vm_info/amdgpu_ge
On Fri, 20 Sep 2024 11:28:02 +0100
Liviu Dudau wrote:
> Since 641bb4394f40 ("fs: move FMODE_UNSIGNED_OFFSET to fop_flags")
> the FMODE_UNSIGNED_OFFSET flag has been moved to fop_flags and renamed,
> but the patch failed to make the changes for the panthor driver.
> When user space opens the rende
linus/master v6.11 next-20240920]
[cannot apply to pci/next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://
On Fri, 20 Sep 2024, Michał Winiarski wrote:
> VF MMIO resource reservation, either created by system firmware and
> inherited by Linux PCI subsystem or created by the subsystem itself,
> contains enough space to fit the BAR of all SR-IOV Virtual Functions
> that can potentially be created (total
On Thu, Sep 19, 2024 at 04:45:28PM +0300, Andy Shevchenko wrote:
> On Thu, Sep 19, 2024 at 11:38:50AM +0300, Raag Jadav wrote:
> > On Thu, Sep 19, 2024 at 10:38:51AM +0300, Jani Nikula wrote:
>
> ...
>
> > Anyway, would you prefer strlcat instead?
>
> FYI: strl*() are subject to remove. They are
From: Andy Yan
The Cluster windows of upcoming VOP on rk3576 also support
linear YUV support, we need to set uv swap bit for it.
As the VOP2_WIN_UV_SWA register defined on rk3568/rk3588 is
0x, so this register will not be touched on these
two platforms.
Signed-off-by: Andy Yan
---
(no
On Thu, Sep 19, 2024 at 01:14:03PM -0500, Vidith Madhu wrote:
> Hi all,
> I'd like to discuss a potential opportunity to enhance the `vrr_enabled`
> property of `drm_crtc_state`. Currently, this property is a Boolean flag, but
> this exposes some ambiguity and potential disconnect between client
linus/master v6.11 next-20240920]
[cannot apply to pci/next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url:
https://
Am 20.09.24 um 10:57 schrieb Philipp Stanner:
On Wed, 2024-09-18 at 15:39 +0200, Christian König wrote:
Tearing down the scheduler with jobs still on the pending list can
lead to use after free issues. Add a warning if drivers try to
destroy a scheduler which still has work pushed to the HW.
Di
Since 641bb4394f40 ("fs: move FMODE_UNSIGNED_OFFSET to fop_flags")
the FMODE_UNSIGNED_OFFSET flag has been moved to fop_flags and renamed,
but the patch failed to make the changes for the panthor driver.
When user space opens the render node the WARN() added by the patch
gets triggered.
Fixes: 641
Am 20.09.24 um 00:35 schrieb Michał Winiarski:
VF MMIO resource reservation, either created by system firmware and
inherited by Linux PCI subsystem or created by the subsystem itself,
contains enough space to fit the BAR of all SR-IOV Virtual Functions
that can potentially be created (total VFs s
Hi Dave, Simona,
First pull request for v6.12!
Enjoy!
Cheers,
~Maarten
drm-misc-next-2024-09-20:
drm-misc-next for v6.12:
UAPI Changes:
- Add panthor/DEV_QUERY_TIMESTAMP_INFO query.
Cross-subsystem Changes:
- Updated dt bindings.
- Add documentation explaining default errnos for fences.
- Mar
On Thu, Sep 19, 2024 at 08:53:43PM +0200, Thomas Zimmermann wrote:
> Several places in drm.ko use struct drm_rect and its helpers. This
> only works as the called interfaces are declared as static inline in
> the header file. Fix the issue by linking drm_rect.o into drm.ko.
Seems reasonable.
Revie
Am 20.09.24 um 00:35 schrieb Michał Winiarski:
Similar to regular resizable BAR, VF BAR can also be resized.
The structures are very similar, which means we can reuse most of the
implementation. See PCIe r4.0, sec 9.3.7.4.
Signed-off-by: Michał Winiarski
---
drivers/pci/iov.c | 28
On 19/09/2024 09:12, Ryosuke Yasuoka wrote:
QXL supports the drm_panic module, which displays a message to the
screen when a kernel panic occurs.
It looks good to me. I think you just need to adjust some functions
argument indentation (tab size is 8), see below.
Best regards,
--
Jocelyn
On Sat, Aug 31, 2024 at 09:06:53PM GMT, Stephen Boyd wrote:
> Add a DT graph binding to google,cros-ec-typec so that it can combine
> DisplayPort (DP) and USB SuperSpeed (SS) data into a USB type-c endpoint
> that is connected to the usb-c-connector node's SS endpoint. This also
> allows us to conn
And rename it process_desc, since it will soon contain more than
just the process_name.
Signed-off-by: Pierre-Eric Pelloux-Prayer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_dev_coredump.c | 4 ++--
drivers/gpu/drm/amd/amdgpu/amdgpu_job.c
Add an optional drm-client-name field to drm fdinfo's output.
Reviewed-by: Christian König
Reviewed-by: Tvrtko Ursulin
Signed-off-by: Pierre-Eric Pelloux-Prayer
---
Documentation/gpu/drm-usage-stats.rst | 5 +
drivers/gpu/drm/drm_file.c| 5 +
2 files changed, 10 insertions(
If a drm_file name is set append it to the process name.
This information is useful with the virtio/native-context driver: this
allows the guest applications identifier to visible in amdgpu's output.
The output in amdgpu_vm_info/amdgpu_gem_info looks like this:
pid:12255Process:glxgears/te
This will allow to use flexible array to store the process name and
other information.
This also means that process name will be determined once and for all,
instead of at each submit.
Signed-off-by: Pierre-Eric Pelloux-Prayer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 15 +--
1 f
At this point the vm is locked so we safely modify it without risk of
concurrent access.
Signed-off-by: Pierre-Eric Pelloux-Prayer
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c
b/driver
Giving the opportunity to userspace to associate a free-form
name with a drm_file struct is helpful for tracking and debugging.
This is similar to the existing DMA_BUF_SET_NAME ioctl.
Access to name is protected by a mutex, and the 'clients' debugfs
file has been updated to print it.
Userspace M
v3 changelog:
* Added DRM_NAME_MAX_LEN instead of using NAME_MAX
* Fixed Tvrtko & Christian comments on patch 1
* Added R-b tags to patch 2
* Following Christian' suggestion patch 3 became 4 patches:
- amdgpu_task_info::process_name is now a flexible array
- amdgpu_vm::task_info is allocated
On Wed, 2024-09-18 at 15:39 +0200, Christian König wrote:
> Tearing down the scheduler with jobs still on the pending list can
> lead to use after free issues. Add a warning if drivers try to
> destroy a scheduler which still has work pushed to the HW.
Did you have time yet to look into my propose
From: Hermes Wu
Fix HDCP CTS items on UNIGRAF DPR-100
Signed-off-by: Hermes Wu
---
drivers/gpu/drm/bridge/ite-it6505.c | 152 ++--
1 file changed, 101 insertions(+), 51 deletions(-)
diff --git a/drivers/gpu/drm/bridge/ite-it6505.c
b/drivers/gpu/drm/bridge/ite-it6505.c
github.com/intel-lab-lkp/linux/commits/Micha-Winiarski/PCI-Add-support-for-VF-Resizable-Bar-extended-cap/20240920-064112
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git for-linus
patch link:
https://lore.kernel.org/r/20240919223557.1897608-2-michal.winiarski%40intel.com
pat
From: "Hermes.Wu"
add AUX-I2C functionality to support MCCS.
Change-Id: I63e1a0e5da67526f89f35605a82944be67dee8ac
Signed-off-by: Hermes Wu
---
drivers/gpu/drm/bridge/ite-it6505.c | 209 ++--
1 file changed, 200 insertions(+), 9 deletions(-)
diff --git a/drivers/gpu/dr
From: allen chen
Fix HDCP CTS items on UNIGRAF DPR-100.
Change-Id: I03f0758779f73164c8ae2fdf61e41dc693e27605
Change-Id: Ib7a8fabaeccd56d3bd7c8adc7384a363b0f7b88d
Signed-off-by: Hermes Wu
---
drivers/gpu/drm/bridge/ite-it6505.c | 152 ++--
1 file changed, 101 insertions
From: "Hermes.Wu"
Add AUX i2c funtion for MCCS
Change-Id: Ia8952f3cde4d9610d6f8a0c3915fc6ffefc6da22
Signed-off-by: Hermes Wu
---
drivers/gpu/drm/bridge/ite-it6505.c | 209 ++--
1 file changed, 200 insertions(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/bridge/ite-it
From: "Hermes.Wu"
This series change aux function to support MCCS and fix HDCP CTS
Hermes.Wu (1):
drm/bridge: it6505: Add MSSC suport
allen chen (1):
drm/bridge: it6505: HDCP CTS fail on repeater items
drivers/gpu/drm/bridge/ite-it6505.c | 343 +++-
1 file change
From: Hermes Wu
add AUX-I2C functionality to support MCCS
Signed-off-by: Hermes Wu
---
drivers/gpu/drm/bridge/ite-it6505.c | 209 ++--
1 file changed, 200 insertions(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/bridge/ite-it6505.c
b/drivers/gpu/drm/bridge/ite-it650
From: Hermes Wu
This series change aux function to support MCCS and fix HDCP CTS
Hermes Wu (2):
drm/bridge: it6505: HDCP CTS fail on repeater
drm/bridge: it6505: Add MCCS support
drivers/gpu/drm/bridge/ite-it6505.c | 343 +++-
1 file changed, 292 insertions(+), 51 d
From: Andy Yan
Thanks for the basic work from Collabora, I can bringup a HDMI
display out on rk3576.
PATCH 1 is a carryover from the working when add support for rk3588,
is very usefull when some people want me help debug some issue
online, so I really hope it can be merged at t
From: Andy Yan
VOP2 on rk3576:
Three video ports:
VP0 Max 4096x2160
VP1 Max 2560x1600
VP2 Max 1920x1080
2 4K Cluster windows with AFBC/RFBC, line RGB and YUV
4 Esmart windows with line RGB/YUV support:
Esmart0/1: 4K
Esmart2/3: 2k, or worked together as a single 4K plane at shared
line buffer mod
From: Andy Yan
Add vop found on rk3576, the main difference between rk3576 and the
previous vop is that each VP has its own interrupt line.
Signed-off-by: Andy Yan
---
Changes in v3:
- ordered by soc name
- Add description for newly added interrupt
Changes in v2:
- Add dt bindings
.../bind
From: Andy Yan
In the upcoming VOP of rk3576, a window cannot attach to all Video
Ports, we introduce a possible_vp_mask for every window to indicate
which Video Ports this window can attach to.
Signed-off-by: Andy Yan
---
(no changes since v1)
drivers/gpu/drm/rockchip/rockchip_drm_vop2.c |
From: Andy Yan
In the upcoming VOP of rk3576, a Window cannot attach to all Video Ports,
so make sure all VP find it's suitable primary plane, then register the
remain windows as overlay plane will make code easier.
Signed-off-by: Andy Yan
---
Changes in v3:
- Add comments for why we should t
From: Andy Yan
There is a version number hardcoded in the VOP VERSION_INFO
register, and the version number increments sequentially based
on the production order of the SOC.
So using this version number to distinguish different VOP features
will simplify the code.
Signed-off-by: Andy Yan
---
From: Andy Yan
In the upcoming VOP for rk3576, every VP has it's own LAYER_SEL
register, and the configuration value of each VP for the same
window maybe different, so extend the layer_sel_id to array,
let it can descption the layer select configuration value for
different VP.
Signed-off-by: And
From: Andy Yan
The VOP interface mux, overlay, background delay cycle configuration
of different SOC are much different. Add platform specific callback
ops to let the core driver look cleaner and more refined.
Signed-off-by: Andy Yan
---
(no changes since v2)
Changes in v2:
- Add platform sp
From: Andy Yan
Move rockchip_drm_drv.h in rockchip_drm_vop2.h to fix the follow
sparse warning:
ARCH=arm64 LLVM=1 make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
mrproper defconfig all -j12
drivers/gpu/drm/rockchip/rockchip_vop2_reg.c:502:24: sparse:
warning: symbol 'vop2_platform_driver'
From: Andy Yan
This is the only afbc format supported by the upcoming
VOP for rk3576.
Add support for it.
Signed-off-by: Andy Yan
---
(no changes since v2)
Changes in v2:
- split it from main patch add support for rk3576
drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 17 +
From: Andy Yan
Every layer of vop2 should bind a window, and we also need to make
sure that this window is not used by other layer.
0x5 is a reserved layer sel value on rk3568, but it will select
Cluster3 on rk3588, configure unused layers to 0x5 will lead
alpha blending error on rk3588.
When
From: Andy Yan
The alpha setup should start from the second layer, the current calculation
starts incorrectly from the first layer, a negative offset will be obtained
in the following formula:
offset = (mixer_id + zpos - 1) * 0x10
Fixes: 604be85547ce ("drm/rockchip: Add VOP2 driver")
Signed-off
From: Andy Yan
The phy_id of cluster windws are not increase one for each window.
Fixes: 604be85547ce ("drm/rockchip: Add VOP2 driver")
Signed-off-by: Andy Yan
Tested-by: Derek Foreman
---
(no changes since v1)
drivers/gpu/drm/rockchip/rockchip_drm_vop2.c | 18 +-
1 file cha
From: Andy Yan
The vop mmu support translate physical address upper 4 GB to iova
below 4 GB. So set dma mask to 64 bit to indicate we support address
> 4GB.
This can avoid warnging message like this on some boards with DDR
> 4 GB:
rockchip-drm display-subsystem: swiotlb buffer is full (sz: 2662
From: Andy Yan
/sys/kernel/debug/dri/vop2/summary: dump vop display state
/sys/kernel/debug/dri/vop2/regs: dump whole vop registers
/sys/kernel/debug/dri/vop2/active_regs: only dump the registers of
activated modules
Signed-off-by: Andy Yan
Reviewed-by: Sascha Hauer
---
(no changes since v1
1 - 100 of 118 matches
Mail list logo
