[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: Swap ggtt_vma during legacy cursor update

2023-06-29 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915: Swap ggtt_vma during legacy cursor update URL : https://patchwork.freedesktop.org/series/120018/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13337_full -> Patchwork_120018v1_full

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Refactor PAT/cache handling (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Refactor PAT/cache handling (rev2) URL : https://patchwork.freedesktop.org/series/119982/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13337_full -> Patchwork_119982v2_full Summary

Re: [Intel-gfx] [RFC 0/3] Get optimal audio frequency and channels

2023-06-29 Thread Golani, Mitulkumar Ajitkumar
Hi @Jani Nikula > -Original Message- > From: Jani Nikula > Sent: 29 June 2023 13:43 > To: Golani, Mitulkumar Ajitkumar ; > intel-gfx@lists.freedesktop.org > Subject: Re: [Intel-gfx] [RFC 0/3] Get optimal audio frequency and channels > > On Wed, 28 Jun 2023, Mitul Golani > wrote: > >

Re: [Intel-gfx] [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register

2023-06-29 Thread Sui Jingfeng
Hi, On 2023/6/30 01:44, Limonciello, Mario wrote: I think what you can do is pick up all the tags in your next version. Once the whole series has tags we can discuss how it merges. Yes, you are right. I will prepare the next version. But I think, I should only gather the reverent part

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/pxp: Optimize GET_PARAM:PXP_STATUS (rev3)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915/pxp: Optimize GET_PARAM:PXP_STATUS (rev3) URL : https://patchwork.freedesktop.org/series/118723/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13338 -> Patchwork_118723v3 Summary

Re: [Intel-gfx] [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register

2023-06-29 Thread suijingfeng
Hi, On 2023/6/30 01:44, Limonciello, Mario wrote: [Public] -Original Message- From: 15330273...@189.cn <15330273...@189.cn> Sent: Thursday, June 29, 2023 12:00 PM To: Bjorn Helgaas ; Sui Jingfeng Cc: Bjorn Helgaas ; linux-fb...@vger.kernel.org; Cornelia Huck ; Karol Herbst ;

[Intel-gfx] [PATCH v3] drm/i915/pxp: Optimize GET_PARAM:PXP_STATUS

2023-06-29 Thread Alan Previn
After recent discussions with Mesa folks, it was requested that we optimize i915's GET_PARAM for the PXP_STATUS without changing the UAPI spec. Add these additional optimizations: - If any PXP initializatoin flow failed, then ensure that we catch it so that we can change the returned

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/shrinker: Treat fb's with higher priority than active reference

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915/shrinker: Treat fb's with higher priority than active reference URL : https://patchwork.freedesktop.org/series/120039/ State : success == Summary == CI Bug Log - changes from CI_DRM_13337 -> Patchwork_120039v1

[Intel-gfx] [RFC] drm/i915/shrinker: Treat fb's with higher priority than active reference

2023-06-29 Thread Radhakrishna Sripada
Earlier framebuffers were treated as an active reference in the shrinker code and were skipped from eviction during kswapd run. However when the memory pressure is high, the fb object would be evicted. This causes display flicker while running memory stress tests when fb objects are created from

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Fail if DSC compression requirement is less than platform supports (rev3)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Fail if DSC compression requirement is less than platform supports (rev3) URL : https://patchwork.freedesktop.org/series/119848/ State : success == Summary == CI Bug Log - changes from CI_DRM_13335_full -> Patchwork_119848v3_full

Re: [Intel-gfx] [PATCH] drm/i915/pxp: Optimize GET_PARAM:PXP_STATUS

2023-06-29 Thread Teres Alexis, Alan Previn
On Tue, 2023-06-20 at 09:30 -0500, Balasubrawmanian, Vivaik wrote: > On 6/1/2023 12:45 PM, Alan Previn wrote: > > After recent discussions with Mesa folks, it was requested > > that we optimize i915's GET_PARAM for the PXP_STATUS without > > changing the UAPI spec. > > > > This patch adds this

Re: [Intel-gfx] [PATCH v3] drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests

2023-06-29 Thread Tvrtko Ursulin
On 29/06/2023 21:42, Alan Previn wrote: On MTL, if the GSC Proxy init flows haven't completed, submissions to the GSC engine will fail. Those init flows are dependent on the mei's gsc_proxy component that is loaded in parallel with i915 and a worker that could potentially start after i915

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests (rev3)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests (rev3) URL : https://patchwork.freedesktop.org/series/117713/ State : success == Summary == CI Bug Log - changes from CI_DRM_13337 -> Patchwork_117713v3

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests (rev3)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests (rev3) URL : https://patchwork.freedesktop.org/series/117713/ State : warning == Summary == Error: dim checkpatch failed d16f50ca614e drm/i915/selftest/gsc: Ensure GSC Proxy init completes

[Intel-gfx] [PATCH v3] drm/i915/selftest/gsc: Ensure GSC Proxy init completes before selftests

2023-06-29 Thread Alan Previn
On MTL, if the GSC Proxy init flows haven't completed, submissions to the GSC engine will fail. Those init flows are dependent on the mei's gsc_proxy component that is loaded in parallel with i915 and a worker that could potentially start after i915 driver init is done. That said, all subsytems

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/quirk: Add quirk for devices that cannot be dimmed (rev3)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915/quirk: Add quirk for devices that cannot be dimmed (rev3) URL : https://patchwork.freedesktop.org/series/118971/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13337 -> Patchwork_118971v3

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Swap ggtt_vma during legacy cursor update

2023-06-29 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915: Swap ggtt_vma during legacy cursor update URL : https://patchwork.freedesktop.org/series/120018/ State : success == Summary == CI Bug Log - changes from CI_DRM_13337 -> Patchwork_120018v1

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Refactor PAT/cache handling (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Refactor PAT/cache handling (rev2) URL : https://patchwork.freedesktop.org/series/119982/ State : success == Summary == CI Bug Log - changes from CI_DRM_13337 -> Patchwork_119982v2 Summary ---

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Refactor PAT/cache handling (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Refactor PAT/cache handling (rev2) URL : https://patchwork.freedesktop.org/series/119982/ State : warning == Summary == Error: dim checkpatch failed bad38a5a74aa drm/i915: Refactor PAT/cache handling Traceback (most recent call last): File

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Refactor PAT/cache handling (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Refactor PAT/cache handling (rev2) URL : https://patchwork.freedesktop.org/series/119982/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/guc: Dump perf_limit_reasons for debug (rev2)

2023-06-29 Thread Belgaumkar, Vinay
On 6/28/2023 10:41 AM, Patchwork wrote: Project List - Patchwork *Patch Details* *Series:* drm/i915/guc: Dump perf_limit_reasons for debug (rev2) *URL:* https://patchwork.freedesktop.org/series/119893/ *State:*failure *Details:*

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Don't rely that 2 VDSC engines are always enough for pixel rate (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Don't rely that 2 VDSC engines are always enough for pixel rate (rev2) URL : https://patchwork.freedesktop.org/series/119967/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13336 -> Patchwork_119967v2

Re: [Intel-gfx] [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register

2023-06-29 Thread Limonciello, Mario
[Public] > -Original Message- > From: 15330273...@189.cn <15330273...@189.cn> > Sent: Thursday, June 29, 2023 12:00 PM > To: Bjorn Helgaas ; Sui Jingfeng > > Cc: Bjorn Helgaas ; linux-fb...@vger.kernel.org; > Cornelia Huck ; Karol Herbst ; > nouv...@lists.freedesktop.org; Joonas Lahtinen

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Don't rely that 2 VDSC engines are always enough for pixel rate (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Don't rely that 2 VDSC engines are always enough for pixel rate (rev2) URL : https://patchwork.freedesktop.org/series/119967/ State : warning == Summary == Error: dim checkpatch failed 6ecbb473f50a drm/i915: Don't rely that 2 VDSC engines are always

[Intel-gfx] [PATCH] drm/i915/quirk: Add quirk for devices that cannot be dimmed

2023-06-29 Thread Allen Ballway
Cybernet T10C cannot be dimmed without the backlight strobing. Create a new quirk to lock the minimum brightness to the highest supported value. This aligns the device with its behavior on Windows, which will not lower the brightness below maximum. Signed-off-by: Allen Ballway --- V2 -> V3: Fix

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Don't preserve dpll_hw_state for slave crtc in Bigjoiner (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Don't preserve dpll_hw_state for slave crtc in Bigjoiner (rev2) URL : https://patchwork.freedesktop.org/series/119978/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13336 -> Patchwork_119978v2

Re: [Intel-gfx] [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register

2023-06-29 Thread Sui Jingfeng
Hi, On 2023/6/29 23:54, Bjorn Helgaas wrote: On Thu, Jun 22, 2023 at 01:08:15PM +0800, Sui Jingfeng wrote: Hi, A nouveau developer(Lyude) from redhat send me a R-B, Thanks for the developers of nouveau project. Please allow me add a link[1] here. [1]

[Intel-gfx] ✗ Fi.CI.IGT: failure for Fix ctx workarounds for non-masked regs (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: Fix ctx workarounds for non-masked regs (rev2) URL : https://patchwork.freedesktop.org/series/119826/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13332_full -> Patchwork_119826v2_full Summary

Re: [Intel-gfx] [PATCH v2 1/6] drm/i915: use mock device info for creating mock device

2023-06-29 Thread Yang, Fei
> Instead of modifying the device info on the fly, use static const > mock device info. > > It's not okay to modify device info at runtime; we've added separate > runtime info for info that needs to be modified at runtime. We've > added safeguards to device info to prevent it from being modified,

Re: [Intel-gfx] [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register

2023-06-29 Thread Bjorn Helgaas
On Thu, Jun 22, 2023 at 01:08:15PM +0800, Sui Jingfeng wrote: > Hi, > > > A nouveau developer(Lyude) from redhat send me a R-B, > > Thanks for the developers of nouveau project. > > > Please allow me add a link[1] here. > > > [1] >

[Intel-gfx] [PATCH 2/2] drm/i915: Handle legacy cursor update as normal update

2023-06-29 Thread Maarten Lankhorst
Move hw_done to cleanup, to ensure we only unpin cursor fb after we received a flip event. This disables the legacy_cursor_update immediate completion of flip_done events, and waits for flip_done before cleaning up. Signed-off-by: Maarten Lankhorst ---

[Intel-gfx] [PATCH 1/2] drm/i915: Swap ggtt_vma during legacy cursor update

2023-06-29 Thread Maarten Lankhorst
Xe is lacking the ability to re-use the ggtt_vma when updating cursor. Instead of pinning from the new plane_state, move the ggtt_vma from old_plane_state to new_plane_state. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/i915/display/intel_cursor.c | 5 ++--- 1 file changed, 2

Re: [Intel-gfx] [PATCH v7 6/8] PCI/VGA: Introduce is_boot_device function callback to vga_client_register

2023-06-29 Thread Sui Jingfeng
Hi, Humble ping ! Please share some bandwidth to help reviewing this series, OK ? As this series is useful for all architecture, I have tested on my X86, mips and LoongArch computer. Questions and comments is also welcome. If no one response within three days, I'm going to send a

[Intel-gfx] [PATCH v2] drm/i915: Refactor PAT/cache handling

2023-06-29 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Informal commit message for now. I got a bit impatient and curious to see if the idea we discussed would work so sketched something out. I think it is what I was describing back then.. So high level idea is to teach the driver what caching modes are hidden behind PAT

Re: [Intel-gfx] [PATCH v2 5/5] drm/i915: Try to initialize DDI/ICL+ DSI ports for every VBT child device

2023-06-29 Thread Ville Syrjälä
On Mon, Jun 26, 2023 at 04:06:00PM +0300, Jani Nikula wrote: > On Tue, 20 Jun 2023, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Try to deal with duplicate child devices for the same DDI port > > by attempting to initialize them in VBT defined order The first > > on to succeed for a

Re: [Intel-gfx] [PATCH v2 3/5] drm/i915: Remove DDC pin sanitation

2023-06-29 Thread Ville Syrjälä
On Wed, Jun 21, 2023 at 10:56:14AM +0300, Jani Nikula wrote: > On Tue, 20 Jun 2023, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Stop with the VBT DDC pin sanitation, and instead just check > > that the appropriate DDC pin is still available when initializing > > a HDMI connector. > >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fail if DSC compression requirement is less than platform supports (rev3)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Fail if DSC compression requirement is less than platform supports (rev3) URL : https://patchwork.freedesktop.org/series/119848/ State : success == Summary == CI Bug Log - changes from CI_DRM_13335 -> Patchwork_119848v3

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fail if DSC compression requirement is less than platform supports (rev3)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Fail if DSC compression requirement is less than platform supports (rev3) URL : https://patchwork.freedesktop.org/series/119848/ State : warning == Summary == Error: dim checkpatch failed 9fd5cc5c7436 drm/i915: Fail if DSC compression requirement is

Re: [Intel-gfx] [PATCH v2 6/6] drm/i915: make device info a const pointer to rodata

2023-06-29 Thread Jani Nikula
On Thu, 29 Jun 2023, Jani Nikula wrote: > On Thu, 29 Jun 2023, Tvrtko Ursulin wrote: >> On 27/06/2023 16:14, Jani Nikula wrote: >>> Finally we can get rid of the pseudo-const write-once device info, and >>> convert it into a const pointer to device info in rodata. >>> >>> Cc: Matt Roper >>>

Re: [Intel-gfx] [PATCH] drm/i915: Fail if DSC compression requirement is less than platform supports

2023-06-29 Thread Luca Coelho
On Thu, 2023-06-29 at 15:25 +0300, Stanislav Lisovskiy wrote: > Currently we just clamp that value to the highest supported one, however that > means, we are not able to fit this into our available bandwidth range, so we > might see glitches or FIFO underruns. > While choosing less compressed bpp

Re: [Intel-gfx] [PATCH v2 1/6] drm/i915: use mock device info for creating mock device

2023-06-29 Thread Andrzej Hajda
On 27.06.2023 17:13, Jani Nikula wrote: Instead of modifying the device info on the fly, use static const mock device info. It's not okay to modify device info at runtime; we've added separate runtime info for info that needs to be modified at runtime. We've added safeguards to device info

[Intel-gfx] [PATCH] drm/i915: Fail if DSC compression requirement is less than platform supports

2023-06-29 Thread Stanislav Lisovskiy
Currently we just clamp that value to the highest supported one, however that means, we are not able to fit this into our available bandwidth range, so we might see glitches or FIFO underruns. While choosing less compressed bpp than min bpp required to handle the mode is harmless and might even

Re: [Intel-gfx] [PATCH] drm/i915: Don't preserve dpll_hw_state for slave crtc in Bigjoiner

2023-06-29 Thread Jani Nikula
On Thu, 29 Jun 2023, "Lisovskiy, Stanislav" wrote: > On Wed, Jun 28, 2023 at 06:10:15PM +0300, Jani Nikula wrote: >> On Wed, 28 Jun 2023, Stanislav Lisovskiy >> wrote: >> > If we are using Bigjoiner dpll_hw_state is supposed to be exactly >> > same as for master crtc, so no need to save it's

Re: [Intel-gfx] [PATCH v2 1/6] drm/i915: use mock device info for creating mock device

2023-06-29 Thread Andi Shyti
Hi Jani, On Tue, Jun 27, 2023 at 06:13:58PM +0300, Jani Nikula wrote: > Instead of modifying the device info on the fly, use static const mock > device info. > > It's not okay to modify device info at runtime; we've added separate > runtime info for info that needs to be modified at runtime.

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gsc: define gsc fw (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915/gsc: define gsc fw (rev2) URL : https://patchwork.freedesktop.org/series/119310/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13330_full -> Patchwork_119310v2_full Summary ---

Re: [Intel-gfx] [RFC] drm/i915: Refactor PAT/cache handling

2023-06-29 Thread Tvrtko Ursulin
On 29/06/2023 06:39, Yang, Fei wrote: > From: Tvrtko Ursulin > > Informal commit message for now. > > I got a bit impatient and curious to see if the idea we discussed would > work so sketched something out. I think it is what I was describing back > then.. Oops, you beat me on this,

[Intel-gfx] [PULL] drm-misc-next-fixes

2023-06-29 Thread Thomas Zimmermann
Hi Dave and Daniel, only one trivial bugfix this week. Best regards Thomas drm-misc-next-fixes-2023-06-29: Short summary of fixes pull: * fbdev: Fix module infos on sparc The following changes since commit cf683e8870bd4be0fd6b98639286700a35088660: fbdev: Use /* */ comment in initializer

Re: [Intel-gfx] [PATCH] drm/i915: Don't preserve dpll_hw_state for slave crtc in Bigjoiner

2023-06-29 Thread Lisovskiy, Stanislav
On Wed, Jun 28, 2023 at 06:10:15PM +0300, Jani Nikula wrote: > On Wed, 28 Jun 2023, Stanislav Lisovskiy > wrote: > > If we are using Bigjoiner dpll_hw_state is supposed to be exactly > > same as for master crtc, so no need to save it's state for slave crtc. > > Could this help with [1]? > >

Re: [Intel-gfx] [PATCH v2 6/6] drm/i915: make device info a const pointer to rodata

2023-06-29 Thread Jani Nikula
On Thu, 29 Jun 2023, Tvrtko Ursulin wrote: > On 27/06/2023 16:14, Jani Nikula wrote: >> Finally we can get rid of the pseudo-const write-once device info, and >> convert it into a const pointer to device info in rodata. >> >> Cc: Matt Roper >> Cc: Lucas De Marchi >> Signed-off-by: Jani Nikula

Re: [Intel-gfx] [PATCH v2 6/6] drm/i915: make device info a const pointer to rodata

2023-06-29 Thread Tvrtko Ursulin
On 27/06/2023 16:14, Jani Nikula wrote: Finally we can get rid of the pseudo-const write-once device info, and convert it into a const pointer to device info in rodata. Cc: Matt Roper Cc: Lucas De Marchi Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/i915_drv.h | 4 ++--

Re: [Intel-gfx] [PATCH v2 2/6] drm/i915: move platform_engine_mask and memory_regions to device info

2023-06-29 Thread Tvrtko Ursulin
On 27/06/2023 16:13, Jani Nikula wrote: The mock device creation was the only place that needed to modify platform_engine_mask and memory_regions runtime. With mock_info in place for mock devices, we can move them to device info. Signed-off-by: Jani Nikula ---

Re: [Intel-gfx] [PATCH v2 1/6] drm/i915: use mock device info for creating mock device

2023-06-29 Thread Tvrtko Ursulin
On 27/06/2023 16:13, Jani Nikula wrote: Instead of modifying the device info on the fly, use static const mock device info. It's not okay to modify device info at runtime; we've added separate runtime info for info that needs to be modified at runtime. We've added safeguards to device info to

[Intel-gfx] ✓ Fi.CI.IGT: success for Get optimal audio frequency and channels (rev8)

2023-06-29 Thread Patchwork
== Series Details == Series: Get optimal audio frequency and channels (rev8) URL : https://patchwork.freedesktop.org/series/119121/ State : success == Summary == CI Bug Log - changes from CI_DRM_13330_full -> Patchwork_119121v8_full

[Intel-gfx] [PULL] drm-intel-next-fixes

2023-06-29 Thread Tvrtko Ursulin
Hi Dave, Daniel, A weekly collection of fixes for the drm-next/6.5 merge window. Mostly small display fixups, one for GuC/SLPC and one header file tidy. Regards, Tvrtko drm-intel-next-fixes-2023-06-29: - Allow DC states along with PW2 only for PWB functionality [adlp+] (Imre Deak) - Fix SSC

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fail if DSC compression requirement is less than platform supports (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: drm/i915: Fail if DSC compression requirement is less than platform supports (rev2) URL : https://patchwork.freedesktop.org/series/119848/ State : failure == Summary == CI Bug Log - changes from CI_DRM_13330_full -> Patchwork_119848v2_full

[Intel-gfx] ✓ Fi.CI.BAT: success for Fix ctx workarounds for non-masked regs (rev2)

2023-06-29 Thread Patchwork
== Series Details == Series: Fix ctx workarounds for non-masked regs (rev2) URL : https://patchwork.freedesktop.org/series/119826/ State : success == Summary == CI Bug Log - changes from CI_DRM_13332 -> Patchwork_119826v2 Summary ---

Re: [Intel-gfx] [RFC 0/3] Get optimal audio frequency and channels

2023-06-29 Thread Jani Nikula
On Wed, 28 Jun 2023, Mitul Golani wrote: > Currently we do not check if there is enough bandwidth for > audio, and what channels and freq it can really support. > Also sometimes there can be HW constraints e.g. GLK where audio > channels supported are only 2. Why are you sending this so many