Hi Daniel, Dave,
Here's this week drm-misc-next PR
Maxime
drm-misc-next-2022-04-28:
drm-misc-next for 5.19:
UAPI Changes:
Cross-subsystem Changes:
Core Changes:
- Introduction of display-helper module, and rework of the DP, DSC,
HDCP, HDMI and SCDC headers
- doc: Improvements for tiny
On 28/04/2022 05:19, Matt Roper wrote:
We're now ready to start exposing compute engines to userspace.
v2:
- Move kerneldoc for other engine classes to a separate patch. (Andi)
Cc: Daniele Ceraolo Spurio
Cc: Tvrtko Ursulin
Cc: Vinay Belgaumkar
Cc: Jordan Justen
Cc: Szymon Morek
UMD (m
Hi Daniel,
On Wed, Apr 13, 2022 at 01:20:11PM +0200, Daniel Vetter wrote:
> On Wed, 13 Apr 2022 at 01:36, Abhinav Kumar wrote:
> > On 4/8/2022 9:04 PM, Abhinav Kumar wrote:
> > >
> > >
> > > On 4/7/2022 4:12 PM, Rob Clark wrote:
> > >> On Thu, Apr 7, 2022 at 3:59 PM Abhinav Kumar
> > >> wrote:
>
On Wed, 27 Apr 2022, Zhi Wang wrote:
> After the refactor of GVT-g, the reference of intel_gvt_match_device()
> only happens in handlers.c. Make it static to let the compiler be
> happy.
>
> Cc: Jason Gunthorpe
> Cc: Jani Nikula
> Cc: Robert Beckett
> Signed-off-by: Zhi Wang
Reviewed-by: Jani
On Wed, 27 Apr 2022, Zhi Wang wrote:
> A compiling error was reported when CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n.
> Fix the problem by using the pre-defined macro.
>
> Cc: Jason Gunthorpe
> Cc: Jani Nikula
> Signed-off-by: Zhi Wang
We'll get this right, for now, but I do wonder if breaking these
On 28/04/2022 05:19, Matt Roper wrote:
Compute engines have a separate register that the driver should use to
perform MMIO-based TLB invalidation.
Note that the term "context" in this register's bspec description is
used to refer to the engine instance (in the same way "context" is used
on bsp
Well usually we increment the drm minor version when adding some new
flags on amdgpu.
Additional to that just one comment from our experience with that: You
don't just need one flag, but two. The first one is a hint which says
"CPU access needed" and the second is a promise which says "CPU acc
Remove shmem region and object backend code as they are now unnecessary.
In the case of objects placed in SMEM and backed by kernel shmem files, the
file pointer has to be retrieved from the ttm_tt structure, so change this
as well. This means accessing an shmem-backed BO's file pointer requires
ge
Am 27.04.22 um 17:02 schrieb Matthew Auld:
On 27/04/2022 07:55, Christian König wrote:
Well usually we increment the drm minor version when adding some new
flags on amdgpu.
Additional to that just one comment from our experience with that:
You don't just need one flag, but two. The first one
This patch is an attempt at eliminating the old shmem memory region and GEM
object backend, in favour of a TTM-based one that is able to manage objects
placed on both system and local memory.
Known issues:
Many GPU hungs in machines of GEN <= 5. My assumption is this has something
to do with a c
Fix the following -Wstringop-overflow warnings when building with GCC-11:
drivers/gpu/drm/i915/intel_pm.c:3106:9: warning: ‘intel_read_wm_latency’
accessing 16 bytes in a region of size 10 [-Wstringop-overflow=]
3106 | intel_read_wm_latency(dev_priv, dev_priv->wm.pri_latency);
|
Fix following coccicheck error:
./drivers/gpu/drm/i915/gvt/handlers.c:2925:35-41: ERROR: block is NULL but
dereferenced.
Use gvt->mmio.mmio_block instead of block to avoid NULL pointer
dereference when find_mmio_block returns NULL.
Fixes: e0f74ed4634d ("i915/gvt: Separate the MMIO tracking table
== Series Details ==
Series: Replace shmem memory region and object backend with TTM
URL : https://patchwork.freedesktop.org/series/103259/
State : warning
== Summary ==
Error: dim checkpatch failed
d619a74d74ea drm/i915: Replace shmem memory region and object backend with TTM
-:37: CHECK:COMP
On 27/04/2022 18:36, Matthew Auld wrote:
On 27/04/2022 09:36, Tvrtko Ursulin wrote:
On 20/04/2022 18:13, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & Thomas)
- Rework error capture interactio
== Series Details ==
Series: Replace shmem memory region and object backend with TTM
URL : https://patchwork.freedesktop.org/series/103259/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11550 -> Patchwork_103259v1
Summary
-
== Series Details ==
Series: drm/i915: Fix -Wstringop-overflow warning in call to
intel_read_wm_latency()
URL : https://patchwork.freedesktop.org/series/103260/
State : warning
== Summary ==
Error: dim checkpatch failed
bb6f50272286 drm/i915: Fix -Wstringop-overflow warning in call to
intel_
== Series Details ==
Series: i915/gvt: Fix NULL pointer dereference in init_mmio_block_handlers
URL : https://patchwork.freedesktop.org/series/103261/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/103261/revisions/1/mbox/ not
applied
Applying: i9
== Series Details ==
Series: drm/i915: Fix -Wstringop-overflow warning in call to
intel_read_wm_latency()
URL : https://patchwork.freedesktop.org/series/103260/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11550 -> Patchwork_103260v1
=
++Laurent ,Dmitry, and Abhinav
> Changes to create a i915 private pipeline to enable the WD transcoder
> without relying on the current drm_writeback framework.
>
> Signed-off-by: Suraj Kandpal
> ---
> drivers/gpu/drm/i915/Makefile | 1 +
> .../drm/i915/display/intel_display_t
On 28/04/2022 09:55, Tvrtko Ursulin wrote:
On 27/04/2022 18:36, Matthew Auld wrote:
On 27/04/2022 09:36, Tvrtko Ursulin wrote:
On 20/04/2022 18:13, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spelling fixes and other small tweaks. (Akeem & T
== Series Details ==
Series: drm/i915: Fix -Wstringop-overflow warning in call to
intel_read_wm_latency()
URL : https://patchwork.freedesktop.org/series/103260/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11550_full -> Patchwork_103260v1_full
===
On 28/04/2022 11:25, Matthew Auld wrote:
On 28/04/2022 09:55, Tvrtko Ursulin wrote:
On 27/04/2022 18:36, Matthew Auld wrote:
On 27/04/2022 09:36, Tvrtko Ursulin wrote:
On 20/04/2022 18:13, Matthew Auld wrote:
Add an entry for the new uapi needed for small BAR on DG2+.
v2:
- Some spell
On Wed-27-04-2022 03:31 am, Navare, Manasi wrote:
On Mon, Apr 25, 2022 at 12:16:11PM +0530, Bhanuprakash Modem wrote:
Modern display hardware is capable of supporting variable refresh rates.
This patch introduces helpers to attach and set "vrr_enabled" property
on the crtc to allow userspace to
Hi Suraj,
On Thu, Apr 28, 2022 at 05:51:47AM +, Kandpal, Suraj wrote:
> ++Laurent ,Dmitry, and Abhinav
>
> Hi,
> Can you have a look at the private implementation i915 is currently going
> with till
> we can figure out how to work with drm core .
No, sorry, I barely have time to follow up
On Thu, Apr 28, 2022 at 10:08:47AM +0200, Maxime Ripard wrote:
> Hi Daniel,
>
> On Wed, Apr 13, 2022 at 01:20:11PM +0200, Daniel Vetter wrote:
> > On Wed, 13 Apr 2022 at 01:36, Abhinav Kumar
> > wrote:
> > > On 4/8/2022 9:04 PM, Abhinav Kumar wrote:
> > > >
> > > >
> > > > On 4/7/2022 4:12 PM, R
On Wed, Apr 27, 2022 at 09:19:24PM -0700, Matt Roper wrote:
> Compute engines have a separate register that the driver should use to
> perform MMIO-based TLB invalidation.
>
> Note that the term "context" in this register's bspec description is
> used to refer to the engine instance (in the same w
Hi,
On 28/04/2022 00:07, Matt Roper wrote:
Rather than storing subslice masks internally as u8[] (inside the sseu
structure) and u32 (everywhere else), let's move over to using an
intel_sseu_ss_mask_t typedef compatible with the operations in
linux/bitmap.h. We're soon going to start adding c
On Wed, Apr 27, 2022 at 08:41:35AM -0700, Niranjana Vishwanathapura wrote:
> On Wed, Apr 20, 2022 at 03:45:25PM -0700, Niranjana Vishwanathapura wrote:
> > On Thu, Mar 31, 2022 at 10:28:48AM +0200, Daniel Vetter wrote:
> > > Adding a pile of people who've expressed interest in vm_bind for their
> >
Hi Matt,
On Wed, Apr 27, 2022 at 09:19:23PM -0700, Matt Roper wrote:
> We'll be adding a new type of engine soon. Let's document the existing
> engine classes first to help make it clear what each type of engine is
> used for.
>
> Cc: Andi Shyti
> Signed-off-by: Matt Roper
Reviewed-by: Andi S
Hi Matt,
On Wed, Apr 27, 2022 at 09:19:25PM -0700, Matt Roper wrote:
> We're now ready to start exposing compute engines to userspace.
>
> v2:
> - Move kerneldoc for other engine classes to a separate patch. (Andi)
>
> Cc: Daniele Ceraolo Spurio
> Cc: Tvrtko Ursulin
> Cc: Vinay Belgaumkar
>
On 14/04/22 17:41, Balasubramani Vivekanandan wrote:
> On 04.04.2022 15:01, Mullati Siva wrote:
>> From: Siva Mullati
>>
>> Convert CT commands and descriptors to use iosys_map rather
>> than plain pointer and save it in the intel_guc_ct_buffer struct.
>> This will help with ct_write and ct_read
On 27.04.2022 22:46, Dixit, Ashutosh wrote:
On Sun, 24 Apr 2022 15:36:23 -0700, Andi Shyti wrote:
Hi Andrzej and Ashutosh,
b/drivers/gpu/drm/i915/gt/intel_gt_types.h
index 937b2e1a305e..4c72b4f983a6 100644
--- a/drivers/gpu/drm/i915/gt/intel_gt_types.h
+++ b/drivers/gpu/drm/i915/gt/intel_gt
== Series Details ==
Series: drm/i915/gt: Fix memory leaks in per-gt sysfs
URL : https://patchwork.freedesktop.org/series/103236/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11550_full -> Patchwork_103236v1_full
Summary
-
Addressed the failure and re-reported.
Re-opened the issue https://gitlab.freedesktop.org/drm/intel/-/issues/5196
igt@syncobj_timeline@wait-all-for-submit-snapshot - fail - Failed assertion:
__syncobj_timeline_wait_ioctl(wait->fd, &wait->wait) == 0, error: -62 != 0
Filed a new issue
https://gitla
At a high level, this change looks good and simple.
However, inside __guc_reset_context, i think there might be
an observed change in behavior for parallel submission.
(or perhaps this change is part the intent?):
Unless my understanding is incorrect, assuming a
parallel submission comes
On Thu, 28 Apr 2022 at 09:39, Adrian Larumbe
wrote:
>
> Remove shmem region and object backend code as they are now unnecessary.
> In the case of objects placed in SMEM and backed by kernel shmem files, the
> file pointer has to be retrieved from the ttm_tt structure, so change this
> as well. Thi
The following changes since commit ac21ab5d1de0de34201c90d32eee436f873d1e5b:
Mellanox: Add lc_ini_bundle for xx.2010.1006 (2022-04-25 07:36:16 -0400)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-firmware guc_v70.1.2_dg2
for you to fetch changes up to 89ae5eb
This series refactors i915's stolen memory region to use ttm.
v2: handle disabled stolen similar to legacy version.
relying on ttm to fail allocs works fine, but is dmesg noisy and causes
testing
dmesg warning regressions.
v3: rebase to latest drm-tip.
fix v2 code
prepare for ttm based stolen region by using ttm range manager
as the resource manager for stolen region.
Signed-off-by: Robert Beckett
Reviewed-by: Thomas Hellström
---
drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c | 6 ++--
drivers/gpu/drm/i915/intel_region_ttm.c | 31 +++
Stolen regions are not page backed or considered iomem.
Prevent flags indicating such.
This correctly prevents stolen buffers from attempting to directly map
them.
See i915_gem_object_has_struct_page() and i915_gem_object_has_iomem()
usage for where it would break otherwise.
Signed-off-by: Robert
ttm managed buffers start off with system resource definitions and ttm_tt
tracking structures allocated (though unpopulated).
currently this prevents clearing of buffers on first move to desired
placements.
The desired behaviour is to clear user allocated buffers and any kernel
buffers that specif
stolen/kernel buffers should not be mmapable by userland.
do not provide callbacks to facilitate this for these buffers.
Signed-off-by: Robert Beckett
---
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 32 +
1 file changed, 27 insertions(+), 5 deletions(-)
diff --git a/driver
add callbacks for alloc and free.
this allows region creators to allocate any extra storage they may
require.
Signed-off-by: Robert Beckett
---
drivers/gpu/drm/i915/intel_memory_region.c | 16 +---
drivers/gpu/drm/i915/intel_memory_region.h | 2 ++
2 files changed, 15 insertions(+),
refactor stolen memory region to use ttm.
this necessitates using ttm resources to track reserved stolen regions
instead of drm_mm_nodes.
Signed-off-by: Robert Beckett
---
drivers/gpu/drm/i915/display/intel_fbc.c | 78 +--
.../gpu/drm/i915/gem/i915_gem_object_types.h | 2 -
drivers/gpu/
Fix function name when documenting it:
drivers/gpu/drm/i915/gvt/handlers.c:3066: warning: expecting prototype
for intel_t_default_mmio_write(). Prototype was for
intel_vgpu_default_mmio_write() instead
Fixes: e39c5add3221 ("drm/i915/gvt: vGPU MMIO virtualization")
Signed-o
Fix broken build:
$ make W=1 drivers/gpu/drm/i915/gvt/handlers.o
...
CC [M] drivers/gpu/drm/i915/gvt/handlers.o
drivers/gpu/drm/i915/gvt/handlers.c:75:6: error: no previous prototype
for ‘intel_gvt_match_device’ [-Werror=missing-prototypes]
75 | boo
On 4/28/22 8:40 PM, De Marchi, Lucas wrote:
> Fix broken build:
>
> $ make W=1 drivers/gpu/drm/i915/gvt/handlers.o
> ...
> CC [M] drivers/gpu/drm/i915/gvt/handlers.o
> drivers/gpu/drm/i915/gvt/handlers.c:75:6: error: no previous prototype
> for ‘intel_gvt_match_device
== Series Details ==
Series: drm/i915: ttm for stolen region (rev5)
URL : https://patchwork.freedesktop.org/series/102540/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Thu, Apr 28, 2022 at 01:42:53PM -0700, Wang, Zhi A wrote:
On 4/28/22 8:40 PM, De Marchi, Lucas wrote:
Fix broken build:
$ make W=1 drivers/gpu/drm/i915/gvt/handlers.o
...
CC [M] drivers/gpu/drm/i915/gvt/handlers.o
drivers/gpu/drm/i915/gvt/handlers.c:75:6: error:
== Series Details ==
Series: series starting with [1/2] drm/i915/gvt: Fix missing static
URL : https://patchwork.freedesktop.org/series/103293/
State : failure
== Summary ==
Error: make failed
CALLscripts/checksyscalls.sh
CALLscripts/atomic/check-atomics.sh
DESCEND objtool
CHK
== Series Details ==
Series: drm/i915: ttm for stolen region (rev5)
URL : https://patchwork.freedesktop.org/series/102540/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11550 -> Patchwork_102540v5
Summary
---
**FAILU
On Thu, Apr 28, 2022 at 08:55:48PM +, Patchwork wrote:
== Series Details ==
Series: series starting with [1/2] drm/i915/gvt: Fix missing static
URL : https://patchwork.freedesktop.org/series/103293/
State : failure
== Summary ==
Error: make failed
CALLscripts/checksyscalls.sh
CALL
Frontbuffer updates were scheduling the execution of DRRS work thread
even if DRRS is not active.
There was no issues with it because intel_drrs_downclock_work() checks
if DRRS is active but there is no reason to keep scheduling this work
thread and wasting CPU time.
Cc: Ville Syrjälä
Signed-off-
So far the i915's DRRS feature was automatically changing between
preferred panel mode and downclock mode based on idleness but ChromeOS
compositor team is asking to be in control of the mode switch.
So for certain types of content it can switch to a mode with a lower
refresh rate without the user
When driver takes over display from firmware it does some checks and
if possible it tries to avoid a modeset to improve user boot
experience.
But even if DRRS is supported it was being left disabled as
intel_crtc_copy_fastset() was overwritten new state with the old one
(hardware readout).
So her
Hi folks:
Here is the pull of gvt-next which fixes the compilation error and warnings
for the the GVT-g refactor patches:
- Fix a compiling warning of non-static function only having one caller.
- Fix a potential NULL pointer reference in the code re-factor.
- Fix a compiling error when CONFIG_D
On Tue, 26 Apr 2022 08:52:58 -0300
Jason Gunthorpe wrote:
> On Tue, Apr 26, 2022 at 08:42:25AM +, Wang, Zhi A wrote:
> > On 4/26/22 8:37 AM, Jani Nikula wrote:
> > > On Tue, 26 Apr 2022, "Wang, Zhi A" wrote:
> > >> Hi folks:
> > >>
> > >> Here is the pull of gvt-next which fixs the compi
On Thu, 28 Apr 2022 15:35:58 -0600
Alex Williamson wrote:
> On Tue, 26 Apr 2022 08:52:58 -0300
> Jason Gunthorpe wrote:
>
> > On Tue, Apr 26, 2022 at 08:42:25AM +, Wang, Zhi A wrote:
> > > On 4/26/22 8:37 AM, Jani Nikula wrote:
> > > > On Tue, 26 Apr 2022, "Wang, Zhi A" wrote:
>
== Series Details ==
Series: series starting with [1/3] drm/i915/display: Do not schedule DRRS work
thread when it is not active
URL : https://patchwork.freedesktop.org/series/103294/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11550 -> Patchwork_103294v1
==
== Series Details ==
Series: series starting with [1/3] drm/i915/display: Do not schedule DRRS work
thread when it is not active
URL : https://patchwork.freedesktop.org/series/103294/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11550_full -> Patchwork_103294v1_full
Some recent Intel dGfx platforms allow media IP to work at a different
frequency from the base GT. This patch series exposes sysfs controls for
this functionality in the new per-gt sysfs. Some enhancements and fixes to
previous per-gt functionality are also included to complete the new
functionalit
Expose new sysfs to program and retrieve media freq factor. Factor values
of 0 (dynamic), 0.5 and 1.0 are supported via a u8.8 fixed point
representation (corresponding to integer values of 0, 128 and 256
respectively).
Media freq factor is converted to media_ratio_mode for GuC. It is
programmed i
Media ratio mode (the ability for media IP to work at a different frequency
from the GT) is available for a subset of dGfx platforms supporting
GuC/SLPC. Introduce 'has_media_ratio_mode' flag in intel_device_info to
identify these platforms and set it for XEHPSDV and DG2/ATS-M.
Signed-off-by: Ashu
All kmalloc'd kobjects need a kobject_put() to free memory. For example in
previous code, kobj_gt_release() never gets called. The requirement of
kobject_put() now results in a slightly different code organization.
v2: s/gtn/gt/ (Andi)
Cc: Andi Shyti
Cc: Andrzej Hajda
Fixes: b770bcfae9ad ("drm/
Each gt contains an independent instance of pcode. Extend pcode functions
to interface with pcode on different gt's. To avoid creating dependency of
display functionality on intel_gt, new pcode function interfaces are
exposed in terms of uncore rather than intel_gt. Previous struct
drm_i915_private
From: Dale B Stimson
Some dGfx pcode commands take additional sub-commands and parameters. Add a
couple of helpers to help formatting these commands to improve code
readability.
v2: Fixed commit author (Rodrigo)
v3: Function rename and convert to new uncore interface for pcode functions
Remo
Convert appropriate callers to use per-gt pcode functions. Callers using
pcode functions at "global scope", including *all* display functions are
not converted, they continue to use the legacy pcode interface.
v2: Convert to new uncore interface for pcode functions
Cc: Andi Shyti
Cc: Rodrigo Viv
Add the following sysfs file to gt/gtN/.defaults:
* media_freq_factor
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Signed-off-by: Ashutosh Dixit
---
drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c | 18 ++
drivers/gpu/drm/i915/gt/intel_gt_types.h| 1 +
drivers/gpu/drm/i915/gt/uc/intel
Create a gt/gtN/.defaults directory (similar to
engine//.defaults) to expose default parameter values for each
gt in sysfs. Populate the .defaults directory with RPS parameter default
values in order to allow userspace to revert to default values when needed.
This patch adds the following sysfs fi
From: Dale B Stimson
Retrieve RP0 and RPn freq for media IP from PCODE and display in per-gt
sysfs. This patch adds the following files to gt/gtN sysfs:
* media_RP0_freq_mhz
* media_RPn_freq_mhz
v2: Fixed commit author (Rodrigo)
v3: Convert to new uncore interface for pcode functions
Cc: Rodrig
== Series Details ==
Series: drm/i915: Media freq factor and per-gt enhancements/fixes (rev3)
URL : https://patchwork.freedesktop.org/series/102665/
State : warning
== Summary ==
Error: dim checkpatch failed
81e412ac8d3c drm/i915: Introduce has_media_ratio_mode
3ae6e0c36677 drm/i915/gt: Add me
== Series Details ==
Series: drm/i915: Media freq factor and per-gt enhancements/fixes (rev3)
URL : https://patchwork.freedesktop.org/series/102665/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Hi all,
On Wed, 13 Apr 2022 10:10:14 +1000 Stephen Rothwell
wrote:
>
> On Wed, 6 Apr 2022 10:34:05 +1000 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the amdgpu tree got a conflict in:
> >
> > drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c
> >
> > between commit:
> >
> > fee2ed
== Series Details ==
Series: drm/i915: Media freq factor and per-gt enhancements/fixes (rev3)
URL : https://patchwork.freedesktop.org/series/102665/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11550 -> Patchwork_102665v3
On Sun, 24 Apr 2022 15:05:47 -0700, Andi Shyti wrote:
>
> Hi Ashutosh,
>
> [...]
>
> > +static ssize_t media_RP0_freq_mhz_show(struct device *dev,
> > + struct device_attribute *attr,
> > + char *buff)
> > +{
> > + struct intel_gt
On Sun, 24 Apr 2022 14:54:22 -0700, Andi Shyti wrote:
>
> Hi Ashutosh,
>
> On Tue, Apr 19, 2022 at 11:25:04PM -0700, Ashutosh Dixit wrote:
> > Convert appropriate callers to use per-gt pcode functions. Callers using
> > pcode functions at "global scope", including *all* display functions are
> > no
On Sun, 24 Apr 2022 12:08:18 -0700, Andi Shyti wrote:
>
> Hi Ashutosh,
Hi Andi,
> [...]
>
> > -static bool skl_pcode_try_request(struct drm_i915_private *i915, u32 mbox,
> > - u32 request, u32 reply_mask, u32 reply,
> > - u32 *status)
> > +s
On Sun, 24 Apr 2022 15:00:24 -0700, Andi Shyti wrote:
>
> Hi Ashutosh,
>
> On Tue, Apr 19, 2022 at 11:25:05PM -0700, Ashutosh Dixit wrote:
> > From: Dale B Stimson
> >
> > Add a couple of helpers to help formatting pcode commands and improve code
> > readability.
>
> Can you please add some more d
On Thu, 28 Apr 2022 07:36:14 -0700, Andrzej Hajda wrote:
> On 27.04.2022 22:46, Dixit, Ashutosh wrote:
> > On Sun, 24 Apr 2022 15:36:23 -0700, Andi Shyti wrote:
> >> Hi Andrzej and Ashutosh,
> >>
> >> b/drivers/gpu/drm/i915/gt/intel_gt_types.h
> >> index 937b2e1a305e..4c72b4f983a6 100644
>
VGA
switcheroo), but, until these improvements are done and land in
upstream, audio drivers needs to be unbound if i915 driver goes unbind.
Yet, even if such fixes got merged, this series is still needed, as it makes
such dependencies more explicit and easier to debug.
PS.: This series was generated a
Sometimes, device drivers are bound using indirect references,
which is not visible when looking at /proc/modules or lsmod.
Add a function to allow setting up module references for such
cases.
Reviewed-by: Dan Williams
Signed-off-by: Mauro Carvalho Chehab
---
See [PATCH 0/2] at:
https://lore.
On some devices, the hda driver needs to hook into a video driver,
in order to be able to properly access the audio hardware and/or
the power management function.
That's the case of several snd_hda_intel devices that depends on
i915 driver.
Currently, this dependency is hidden from /proc/modules
== Series Details ==
Series: Let userspace know when snd-hda-intel needs i915
URL : https://patchwork.freedesktop.org/series/103315/
State : warning
== Summary ==
Error: dim checkpatch failed
4f9130351583 module: add a function to add module references
-:53: WARNING:BRACES: braces {} are not n
83 matches
Mail list logo
