Am 25.06.21 um 10:22 schrieb Thomas Zimmermann:
The field drm_device.irq_enabled is only used by legacy drivers
with userspace modesetting. Don't set it in armada.
Signed-off-by: Thomas Zimmermann
R-b'ed by Laurent via IRC
---
drivers/gpu/drm/armada/armada_drv.c | 2 --
1 file changed,
Fix kernel-doc function name warning:
../include/linux/dma-resv.h:227: warning: expecting prototype for
dma_resv_exclusive(). Prototype was for dma_resv_excl_fence() instead
Fixes: 6edbd6abb783d ("ma-buf: rename and cleanup dma_resv_get_excl v3")
Signed-off-by: Randy Dunlap
Cc: Sumit Semwal
Cc
Fix kernel-doc warning in host1x:
../drivers/gpu/host1x/bus.c:774: warning: Excess function parameter 'key'
description in '__host1x_client_register'
Fixes: 0cfe5a6e758f ("gpu: host1x: Split up client initalization and
registration")
Signed-off-by: Randy Dunlap
Cc: Thierry Reding
Cc: dri-deve
From: John Harrison
Add several module failure load inject points in the CT buffer creation
code path.
Signed-off-by: John Harrison
Signed-off-by: Matthew Brost
Reviewed-by: Michal Wajdeczko
---
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 8
1 file changed, 8 insertions(+)
diff --g
With the introduction of non-blocking CTBs more than one CTB can be in
flight at a time. Increasing the size of the CTBs should reduce how
often software hits the case where no space is available in the CTB
buffer.
Cc: John Harrison
Signed-off-by: Matthew Brost
Reviewed-by: Michal Wajdeczko
---
Improve the error message when a unsolicited CT response is received by
printing fence that couldn't be found, the last fence, and all requests
with a response outstanding.
Signed-off-by: Matthew Brost
Reviewed-by: Michal Wajdeczko
---
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 10 +++---
In upcoming patch we will allow more CTB requests to be sent in
parallel to the GuC for processing, so we shouldn't assume any more
that GuC will always reply without 10ms.
Use bigger value hardcoded value of 1s instead.
v2: Add CONFIG_DRM_I915_GUC_CTB_TIMEOUT config option
v3:
(Daniel Vetter)
Implement a stall timer which fails H2G CTBs once a period of time
with no forward progress is reached to prevent deadlock.
v2:
(Michal)
- Improve error message in ct_deadlock()
- Set broken when ct_deadlock() returns true
- Return -EPIPE on ct_deadlock()
Signed-off-by: John Harrison
Sign
CTB writes are now in the path of command submission and should be
optimized for performance. Rather than reading CTB descriptor values
(e.g. head, tail) which could result in accesses across the PCIe bus,
store shadow local copies and only read/write the descriptor values when
absolutely necessary
Add non blocking CTB send function, intel_guc_send_nb. GuC submission
will send CTBs in the critical path and does not need to wait for these
CTBs to complete before moving on, hence the need for this new function.
The non-blocking CTB now must have a flow control mechanism to ensure
the buffer is
As part of enabling GuC submission discussed in [1], [2], and [3] we
need optimize and update the CT code as this is now in the critical
path of submission. This series includes the patches to do that which is
the first 7 patches from [3]. The patches should have addressed all the
feedback in [3] a
Hi Rajeev,
On Sat, Jun 26, 2021 at 10:21:06PM +0530, Rajeev Nandan wrote:
> Do not give a warning for the eDP panels if the "bus_format" is
> not specified, since most eDP panels can support more than one
> bus formats and this can be auto-detected.
> Also, update the check to include bpc=10 for t
On Sat, Jun 19, 2021 at 10:28:07AM -0700, Yury Norov wrote:
> On Sat, Jun 19, 2021 at 05:24:15PM +0100, Marc Zyngier wrote:
> > On Fri, 18 Jun 2021 20:57:34 +0100,
> > Yury Norov wrote:
> > >
> > > The macros iterate thru all set/clear bits in a bitmap. They search a
> > > first bit using find_fi
https://bugzilla.kernel.org/show_bug.cgi?id=213569
Frank Kruger (fkrue...@mailbox.org) changed:
What|Removed |Added
CC||fkrue...@mailbox.org
https://bugzilla.kernel.org/show_bug.cgi?id=213599
--- Comment #4 from Yuya Nishihara (y...@tcha.org) ---
Yep. In my case, it's gfx9 but both gfx9/10 should be affected according to Bug
213561. LTS branches will need backport of these patches.
--
You may reply to this email to add a comment.
Yo
15 matches
Mail list logo