Only convert it to ENOMEM in ttm_bo_validate.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index edf10618fe2b..8c1eaa74fa21 100644
--- a/drivers/
Try to fill up VRAM as well by setting the busy flag on GTT allocations.
This fixes the issue that when VRAM was evacuated for suspend it's never
filled up again unless the application is restarted.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 6 ++
1 file
From: Somalapuram Amaranath
Instead of a list of separate busy placement add flags which indicate
that a placement should only be used when there is room or if we need to
evict.
v2: add missing TTM_PL_FLAG_IDLE for i915
v3: fix auto build test ERROR on drm-tip/drm-tip
v4: fix some typos pointed
Previously we would never try to move a BO into the preferred placements
when it ever landed in a busy placement since those were considered
compatible.
Rework the whole handling and finally unify the idle and busy handling.
ttm_bo_validate() is now responsible to try idle placement first and then
Seems to be unused.
Signed-off-by: Christian König
---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h| 1 -
drivers/gpu/drm/vmwgfx/vmwgfx_ttm_buffer.c | 28 --
2 files changed, 29 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
b/drivers/gpu/drm/vmwgfx/vmwgfx_dr
Hi guys,
I'm trying to make this functionality a bit more useful for years now
since we multiple reports that behavior of drivers can be suboptimal
when multiple placements be given.
So basically instead of hacking around the TTM behavior in the driver
once more I've gone ahead and changed the id
> -Original Message-
> From: Nikula, Jani
> Sent: Monday, January 8, 2024 7:01 PM
> To: Murthy, Arun R ; intel-gfx@lists.freedesktop.org;
> Deak, Imre
> Cc: Murthy, Arun R
> Subject: Re: [PATCH] drm/i915/display/dp: 128/132b DP-capable with SST
>
> On Wed, 03 Jan 2024, Arun R Murthy wr
== Series Details ==
Series: drm/i915/gt: Use rc6.supported flag from intel_gt for rc6_enable sysfs
URL : https://patchwork.freedesktop.org/series/128343/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14098 -> Patchwork_128343v1
== Series Details ==
Series: drm/i915/gt: Use rc6.supported flag from intel_gt for rc6_enable sysfs
URL : https://patchwork.freedesktop.org/series/128343/
State : warning
== Summary ==
Error: dim checkpatch failed
eb5660834460 drm/i915/gt: Use rc6.supported flag from intel_gt for rc6_enable
s
== Series Details ==
Series: VBT read Cleanup
URL : https://patchwork.freedesktop.org/series/128341/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14098 -> Patchwork_128341v1
Summary
---
**SUCCESS**
No regressions
== Series Details ==
Series: VBT read Cleanup
URL : https://patchwork.freedesktop.org/series/128341/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Currently if rc6 is supported, it gets enabled and the sysfs files for
rc6_enable_show and rc6_enable_dev_show uses masks to check information
from drm_i915_private.
However rc6_support functions take more variables and conditions into
consideration and thus these masks are not enough for most of
On 1/5/2024 3:33 AM, Kamil Konieczny wrote:
Hi Vinay,
On 2024-01-04 at 17:10:00 -0800, Vinay Belgaumkar wrote:
looks good, there are some nits, first about subject:
[PATCH i-g-t] tests/perf_pmu: Restore sysfs freq in exit handler
s!tests/perf_pmu:!tests/intel/perf_pmu:!
Also you can drop "sy
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/display/intel_dp.c
between commit:
fc93835bb0d7 ("drm: Add HPD state to drm_connector_oob_hotplug_event()")
from Linus' tree and commit:
cd572b3bb27e ("drm/i915: Disable hotplug detection work
Vbt can be read from different sources viz. firmware, opregion,
oprom or spi. This will be useful for us to handle the vbt cleanup
during bios remove phase.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c | 15 ---
drivers/gpu/drm/i915/displa
Grouping various vbt load options, move vbt load from firmware option
from opregion vbt load function to bios init.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c | 47 ++-
drivers/gpu/drm/i915/display/intel_opregion.c | 45 -
Asls offset is used to calculate the relative offset of vbt in ASLE
mailbox. Cache the address read from PCI config space to use later during
vbt extraction.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_opregion.c | 4 +++-
drivers/gpu/drm/i915/display/intel_opregio
VBT not read from opregion needs to be freed. Vbt read from
opregion is simply remapped and hence need to point to NULL. While
at it assign the type to NONE VBT type. Free the vbt in other cases.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c | 20 +
vbt_firmware was used to cache the vbt read from firmware. With
introduction of intel_vbt, vbt field is used to cache the firmware read
from different sources making vbt_firmware field redundant. Kill this
field to simplify intel_vbt structure.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu
As part of opregion setup, vbt is extracted from the opregion. Move
the vbt parts of opregion setup into its own function.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_opregion.c | 143 ++
1 file changed, 76 insertions(+), 67 deletions(-)
diff --git
Opregion is probed early during the driver bring up and if present,
vbt is extracted. Move vbt loading to a more appropriate place during
bios init where the vbt is parsed. While at it remove the empty return.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c
intel_vbt will be used to cache the vbt read from firmware. Make
vbt firmware read variant operate on intel_vbt to cache the fw for
future reference.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
dif
We depend on a non null vbt field in intel_vbt to determine
if a vbt is read from its source. This may not be foolproof
hence rely on vbt->type to determine if vbt is read from a source.
Note that this does not determine the validity of read vbt.
Signed-off-by: Radhakrishna Sripada
---
drivers/g
For some platforms where vbt does not reside in opregion,
vbt needs to be cached for debug purposes. Cache them for
future usage.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers
Pass newly created intel_vbt to oprom_get_vbt to standardize
the signature and naming. vbt_header explicitly called out within
the body to avoid confusing with intel_vbt.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c | 32 +++
1 file change
For discrete cards, vbt need not exist in opregion as in the case with
pre opregion platforms. To handle vbt in such cases, move vbt fields
in opregion structure to newly introduced vbt structure. This organizes vbt
related fields and processed intel_vbt_data under the same structure.
Signed-off-b
intel_vbt newly introduced, should be used to cache in the vbt
read from spi. Pass intel_vbt to spi read variant to cache intel_vbt
for future reference.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c | 32 +++
1 file changed, 16 insertions(
Vbt data is scattered to multiple places like vbt_data and
opregion vbt fields. Introduce a new structure intel_vbt
to collate various vbt fields into one simple structure. This
will be used to cache the vbt read from spi flash/oprom as well
as the vbt read from opregion and firmware.
Signed-off-b
intel_bios_init previously operated on vbt_header. Make use
of the newly introduced intel_vbt to be later streamline
different vbt reading methods.
Signed-off-by: Radhakrishna Sripada
---
drivers/gpu/drm/i915/display/intel_bios.c | 28 ---
1 file changed, 15 insertions(+), 13
This series does the VBT read cleanup. The series introduces new
intel_vbt structure to cache and collate vbt related info. Vbt
read from different sources viz. firmware/opregion/spi/oprom
needs to be cached for debug purposes and handled accordingly
during cleanup.
Radhakrishna Sripada (15):
dr
On Mon, Jan 08, 2024 at 05:13:51PM -0500, Rodrigo Vivi wrote:
On Wed, Jan 03, 2024 at 11:59:16PM -0600, Lucas De Marchi wrote:
On Wed, Jan 03, 2024 at 02:50:57PM +0100, Thomas Hellström wrote:
> On Tue, 2023-12-26 at 13:30 -0500, Rodrigo Vivi wrote:
> > On Fri, Dec 22, 2023 at 12:36:39PM +0100,
On Tue, Jan 02, 2024 at 09:44:48PM +0200, Jani Nikula wrote:
> On Tue, 02 Jan 2024, Juha-Pekka Heikkila wrote:
> > Aux ccs framebuffers don't work on Xe driver hence disable them
> > from plane capabilities until they are fixed. Flat ccs framebuffers
> > work and they are left enabled. Here is sep
On Wed, Jan 03, 2024 at 02:50:57PM +0100, Thomas Hellström wrote:
> On Tue, 2023-12-26 at 13:30 -0500, Rodrigo Vivi wrote:
> > On Fri, Dec 22, 2023 at 12:36:39PM +0100, Thomas Hellström wrote:
> > > Add the xe repo to drm-tip and the dim tools.
> > > For now use the sha1 of the first drm-xe-next pu
On Wed, Jan 03, 2024 at 11:59:16PM -0600, Lucas De Marchi wrote:
> On Wed, Jan 03, 2024 at 02:50:57PM +0100, Thomas Hellström wrote:
> > On Tue, 2023-12-26 at 13:30 -0500, Rodrigo Vivi wrote:
> > > On Fri, Dec 22, 2023 at 12:36:39PM +0100, Thomas Hellström wrote:
> > > > Add the xe repo to drm-tip
On Mon, Jan 08, 2024 at 10:35:56AM -0300, Gustavo Sousa wrote:
> Quoting Patchwork (2024-01-05 21:14:37-03:00)
> >== Series Details ==
> >
> >Series: Update bxt_sanitize_cdclk() for Xe2_LPD (rev3)
> >URL : https://patchwork.freedesktop.org/series/128175/
> >State : failure
> >
> >== Summary ==
>
On Fri, Jan 05, 2024 at 08:38:44AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Fix HPD handling during driver init/shutdown (rev2)
> URL : https://patchwork.freedesktop.org/series/128186/
> State : failure
Thanks for the review, the patchset is pushed to drm-intel-next
On 1/4/24 21:16, Jani Nikula wrote:
Including drm_edid.h from nouveau_connector.h causes the rebuild of 15
files when drm_edid.h is modified, while there are only a few files that
actually need to include drm_edid.h.
Cc: Karol Herbst
Cc: Lyude Paul
Cc: Danilo Krummrich
Cc: nouv...@lists.freed
Quoting Gustavo Sousa (2024-01-08 14:27:46-03:00)
>Quoting Gustavo Sousa (2024-01-08 10:35:56-03:00)
>>Quoting Patchwork (2024-01-05 21:14:37-03:00)
>>>== Series Details ==
>>>
>>>Series: Update bxt_sanitize_cdclk() for Xe2_LPD (rev3)
>>>URL : https://patchwork.freedesktop.org/series/128175/
>>>S
Quoting Gustavo Sousa (2024-01-08 10:35:56-03:00)
>Quoting Patchwork (2024-01-05 21:14:37-03:00)
>>== Series Details ==
>>
>>Series: Update bxt_sanitize_cdclk() for Xe2_LPD (rev3)
>>URL : https://patchwork.freedesktop.org/series/128175/
>>State : failure
>>
>>== Summary ==
>>
>>CI Bug Log - chang
== Series Details ==
Series: drm/xe/display: Disable aux ccs framebuffers (rev3)
URL : https://patchwork.freedesktop.org/series/128122/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14093 -> Patchwork_128122v3
Summary
-
== Series Details ==
Series: Extend ARL support
URL : https://patchwork.freedesktop.org/series/128322/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14092_full -> Patchwork_128322v1_full
Summary
---
**FAILURE**
Se
== Series Details ==
Series: drm/xe/display: Disable aux ccs framebuffers (rev3)
URL : https://patchwork.freedesktop.org/series/128122/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./arch/x86/include/asm
== Series Details ==
Series: drm/xe/display: Disable aux ccs framebuffers (rev3)
URL : https://patchwork.freedesktop.org/series/128122/
State : warning
== Summary ==
Error: dim checkpatch failed
ce28f70c318a drm/xe/display: Disable aux ccs framebuffers
Traceback (most recent call last):
File
Quoting Tvrtko Ursulin (2024-01-05 12:39:31)
>
> On 04/01/2024 21:23, Andi Shyti wrote:
> >>> +void intel_gt_apply_ccs_mode(struct intel_gt *gt)
> >>> +{
> >>> + mutex_lock(>->ccs.mutex);
> >>> + __intel_gt_apply_ccs_mode(gt);
> >>> + mutex_unlock(>->ccs.mutex);
> >>> +}
> >>> +
> >>> +vo
== Series Details ==
Series: drm/i915: clear the QGV mask set by GOP while booting (rev2)
URL : https://patchwork.freedesktop.org/series/128223/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_14093 -> Patchwork_128223v2
Summ
On Mon, Jan 08, 2024 at 05:57:37PM +0530, Haridhar Kalvala wrote:
> From: Harish Chegondi
>
> Xe_LPG+ (IP version 12.74) should take the same general code
> paths as Xe_LPG (versions 12.70 and 12.71).
>
> Xe_LPG+'s workaround list will be handled by the next patch.
>
> Signed-off-by: Harish Che
Aux ccs framebuffers don't work on Xe driver hence disable them
from plane capabilities until they are fixed. Flat ccs framebuffers
work and they are left enabled. Here is separated plane capabilities
check on i915 so it can behave differencly depending on the driver.
Closes: https://gitlab.freede
From: George D Sworo
GOP driver in the firmware is masking the QGV points except the one
which can
provide high Bandwidth required for panel.
On boot to the OS the mask is already set, and is not cleared anywhere
in the i915 driver
even though sagv is enabled. This means Pcode is unable to switc
== Series Details ==
Series: Extend ARL support
URL : https://patchwork.freedesktop.org/series/128322/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14092 -> Patchwork_128322v1
Summary
---
**SUCCESS**
No regressio
Quoting Patchwork (2024-01-05 21:14:37-03:00)
>== Series Details ==
>
>Series: Update bxt_sanitize_cdclk() for Xe2_LPD (rev3)
>URL : https://patchwork.freedesktop.org/series/128175/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_14080_full -> Patchwork_128175v3_full
>==
== Series Details ==
Series: Extend ARL support
URL : https://patchwork.freedesktop.org/series/128322/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./arch/x86/include/asm/bitops.h:116:1: warning: unrepla
On Wed, 03 Jan 2024, Arun R Murthy wrote:
> With a value of '0' read from MSTM_CAP register MST to be enabled.
> DP2.1 SCR updates the spec for 128/132b DP capable supporting only one
> stream and not supporting single stream sideband MSG.
> The underlying protocol will be MST to enable use of MTP
== Series Details ==
Series: Bigjoiner refactoring (rev2)
URL : https://patchwork.freedesktop.org/series/128311/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_14092 -> Patchwork_128311v2
Summary
---
**SUCCESS**
No
== Series Details ==
Series: Bigjoiner refactoring (rev2)
URL : https://patchwork.freedesktop.org/series/128311/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./arch/x86/include/asm/bitops.h:116:1: warnin
== Series Details ==
Series: Bigjoiner refactoring (rev2)
URL : https://patchwork.freedesktop.org/series/128311/
State : warning
== Summary ==
Error: dim checkpatch failed
ed3c2b2b22ef drm/i915: Add bigjoiner force enable option to debugfs
519ee160310d drm/i915/bigjoiner: Refactor bigjoiner st
On Mon, 2024-01-08 at 11:44 +0200, Hogander, Jouni wrote:
> On Mon, 2024-01-08 at 11:20 +0200, Imre Deak wrote:
> > On Mon, Jan 08, 2024 at 10:31:07AM +0200, Hogander, Jouni wrote:
> > > On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> >
> > > > An unexpected modeset or connector detection by
From: Harish Chegondi
Xe_LPG+ (IP version 12.74) should take the same general code
paths as Xe_LPG (versions 12.70 and 12.71).
Xe_LPG+'s workaround list will be handled by the next patch.
Signed-off-by: Harish Chegondi
Signed-off-by: Haridhar Kalvala
---
drivers/gpu/drm/i915/gt/intel_engine_
From: Matt Roper
Some of our existing Xe_LPG workarounds and tuning are also applicable
to the version 12.74 variant. Extend the condition bounds accordingly.
Also fix the comment on Wa_14018575942 while we're at it.
v2: Extend some more workarounds (Harish)
Signed-off-by: Matt Roper
Signed-o
From: Matt Roper
Our existing MTL driver handling is also sufficient to handle ARL, so
these IDs are simply added to the MTL ID list.
Bspec: 55420
Signed-off-by: Matt Roper
---
include/drm/i915_pciids.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/drm/i915_pciids.h b/include/
Some SKUs of Arrow Lake use a slightly newer Xe_LPG+ graphics
IP (version 12.74). Add some additional PCI IDs and extend the
code to support this newer IP version. The general code flow
should continue to match existing MTL and Xe_LPG code paths.
Harish Chegondi (1):
drm/i915/xelpg: Extend dri
Don't call enabled_bigjoiner_pipes twice, lets just move
intel_get_bigjoiner_config earlier, because it is anyway
calling same function.
Also cleanup hsw_enabled_transcoders from irrelevant bigjoiner code.
Signed-off-by: Stanislav Lisovskiy
---
drivers/gpu/drm/i915/display/intel_display.c | 22 +
Handle only bigjoiner masters in skl_commit_modeset_enables/disables,
slave crtcs should be handled by master hooks. Same for encoders.
That way we can also remove a bunch of checks like
intel_crtc_is_bigjoiner_slave.
Signed-off-by: Stanislav Lisovskiy
---
drivers/gpu/drm/i915/display/intel_ddi
For validation purposes, it might be useful to be able to
force Bigjoiner mode, even if current dotclock/resolution
do not require that.
Lets add such to option to debugfs.
v2: - Apparently intel_dp_need_bigjoiner can't be used, when
debugfs entry is created so lets just check manually
There are few things we need to do for bigjoiner, in order
to improve code maintenance and also make testing for Bigjoiner
easier.
Those series contain addition of bigjoiner force debugfs option,
in order to be able to force bigjoiner even if there is no display
support, also we refactor pipe vs tr
> -Original Message-
> From: Nautiyal, Ankit K
> Sent: Monday, January 8, 2024 5:08 PM
> To: Murthy, Arun R ; intel-gfx@lists.freedesktop.org;
> Nikula, Jani ; Deak, Imre
> Subject: Re: [PATCH] drm/i915/display/dp: 128/132b DP-capable with SST
>
>
> On 1/3/2024 2:37 PM, Arun R Murthy w
On 1/3/2024 2:37 PM, Arun R Murthy wrote:
With a value of '0' read from MSTM_CAP register MST to be enabled.
DP2.1 SCR updates the spec for 128/132b DP capable supporting only one
stream and not supporting single stream sideband MSG.
I think, we still need to read bit DP_SINGLE_STREAM_SIDEBAN
== Series Details ==
Series: Bigjoiner refactoring
URL : https://patchwork.freedesktop.org/series/128311/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/128311/revisions/1/mbox/ not
applied
Applying: drm/i915: Add bigjoiner force enable option to
On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> An AUX transfer on any disconnected DP port results in long
> timeout/retry delays the same way as this is described for TypeC port
> in
>
> commit a972cd3f0eb5 ("drm/i915/tc: Abort DP AUX transfer on a
> disconnected TC port")
>
> Prevent the
On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> Glitches deasserting the connector HPD line can lead to incorrectly
> detecting a disconnect event (a glitch asserting the line will only
> cause a redundant connect->disconnect transition). The source of such
> a
> glitch can be noise on the li
On Mon, 08 Jan 2024, Stanislav Lisovskiy wrote:
> For validation purposes, it might be useful to be able to
> force Bigjoiner mode, even if current dotclock/resolution
> do not require that.
> Lets add such to option to debugfs.
>
> v2: - Apparently intel_dp_need_bigjoiner can't be used, when
>
On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> Add hooks to intel_digital_port to lock and unlock the port and add a
> helper to check the connector's detect status while the port is
> locked
> already. This simplifies checking the connector detect status in
> intel_dp_aux_xfer() and intel_d
On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> As described in the previous two patches an unexpected connector
> detection can happen during the init/shutdown sequences. Prevent
> these
> by returning the connector's current status from the detection
> handlers.
>
> Signed-off-by: Imre Dea
On Mon, 2024-01-08 at 11:20 +0200, Imre Deak wrote:
> On Mon, Jan 08, 2024 at 10:31:07AM +0200, Hogander, Jouni wrote:
> > On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
>
> > > An unexpected modeset or connector detection by a user (user
> > > space
> > > or FB console) during the initializa
On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> As described in the previous patch, an unexpected connector
> detection/modeset started from the intel_hotplug::hotplug_work can
> happen during the driver init/shutdown sequence. Prevent these by
> disabling the queuing of and flushing all the
On Mon, Jan 08, 2024 at 10:31:07AM +0200, Hogander, Jouni wrote:
> On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> > An unexpected modeset or connector detection by a user (user space
> > or FB console) during the initialization/shutdown sequence is
> > possible either via a hotplug IRQ hand
Handle only bigjoiner masters in skl_commit_modeset_enables/disables,
slave crtcs should be handled by master hooks. Same for encoders.
That way we can also remove a bunch of checks like
intel_crtc_is_bigjoiner_slave.
Signed-off-by: Stanislav Lisovskiy
---
drivers/gpu/drm/i915/display/intel_ddi
Don't call enabled_bigjoiner_pipes twice, lets just move
intel_get_bigjoiner_config earlier, because it is anyway
calling same function.
Also cleanup hsw_enabled_transcoders from irrelevant bigjoiner code.
Signed-off-by: Stanislav Lisovskiy
---
drivers/gpu/drm/i915/display/intel_display.c | 22 +
For validation purposes, it might be useful to be able to
force Bigjoiner mode, even if current dotclock/resolution
do not require that.
Lets add such to option to debugfs.
v2: - Apparently intel_dp_need_bigjoiner can't be used, when
debugfs entry is created so lets just check manually
There are few things we need to do for bigjoiner, in order
to improve code maintenance and also make testing for Bigjoiner
easier.
Those series contain addition of bigjoiner force debugfs option,
in order to be able to force bigjoiner even if there is no display
support, also we refactor pipe vs tr
On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> An unexpected modeset or connector detection by a user (user space or
> FB
> console) during the initialization/shutdown sequence is possible
> either
> via a hotplug IRQ handling work or via the connector sysfs
> (status/detect) interface. Thes
80 matches
Mail list logo
