Add these two dev attrs for xgmi info details which is helpful for
developers checking the xgmi topology by catting the sys file directly.
Take 4 cards with xgmi connection as an example, get the num_hops for each
device or node through xmig_hive_info dir like,
cat /sys/bus/pci/devices/:41:00.
This patch enables following UMD stable Pstates profile levels for
power_dpm_force_performance_level interface.
- profile_peak
- profile_min_mclk
- profile_min_sclk
- profile_standard
Signed-off-by: shikaguo
---
.../drm/amd/pm/swsmu/smu13/yellow_carp_ppt.c | 94 ++-
.../drm/am
[AMD Official Use Only - General]
Series is:
Reviewed-by: Yifan Zhang
From: Huang, Tim
Sent: Wednesday, June 7, 2023 4:02 PM
To: amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ; Zhang, Yifan
; Liu, Aaron ; Guo, Shikai
; Huang, Tim
Subject: [PATCH 3/
[AMD Official Use Only - General]
> -Original Message-
> From: Limonciello, Mario
> Sent: Wednesday, June 7, 2023 1:53 AM
> To: amd-gfx@lists.freedesktop.org
> Cc: Limonciello, Mario
> Subject: [PATCH 2/2] drm/amd: Tighten permissions on VBIOS flashing
> attributes
>
> Non-root users sho
[AMD Official Use Only - General]
Hi Felix
Yes. This patch is aiming to avoid concurrent running of kernel graphics queue
and kernel compute queue.
Previously we might get wrong guilty job if a bad compute job and a good gfx
job submitted concurrently.
Like Xorg might be crashed if we submitte
[Public]
> -Original Message-
> From: Kuehling, Felix
> Sent: Wednesday, June 7, 2023 6:23 PM
> To: Kim, Jonathan ; amd-gfx@lists.freedesktop.org
> Cc: Huang, JinHuiEric
> Subject: Re: [PATCH] drm/amdkfd: fix and enable debugging for gfx11
>
>
> On 2023-06-07 16:20, Jonathan Kim wrote:
>
On 2023-06-07 16:20, Jonathan Kim wrote:
There are a couple of fixes required to enable gfx11 debugging.
First, ADD_QUEUE.trap_en is an inappropriate place to toggle
a per-process register so move it to SET_SHADER_DEBUGGER.trap_en.
When ADD_QUEUE.skip_process_ctx_clear is set, MES will priorit
Hi Dave, Daniel,
Fixes for 6.4.
The following changes since commit 9561de3a55bed6bdd44a12820ba81ec416e705a7:
Linux 6.4-rc5 (2023-06-04 14:04:27 -0400)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git
tags/amd-drm-fixes-6.4-2023-06-07
for you to fetch
There are a couple of fixes required to enable gfx11 debugging.
First, ADD_QUEUE.trap_en is an inappropriate place to toggle
a per-process register so move it to SET_SHADER_DEBUGGER.trap_en.
When ADD_QUEUE.skip_process_ctx_clear is set, MES will prioritize
the SET_SHADER_DEBUGGER.trap_en setting.
[Public]
> -Original Message-
> From: Kim, Jonathan
> Sent: Wednesday, June 7, 2023 3:28 PM
> To: Kuehling, Felix ; amd-
> g...@lists.freedesktop.org
> Cc: Huang, JinHuiEric
> Subject: RE: [PATCH] drm/amdkfd: fix and enable debugging for gfx11
>
>
>
> > -Original Message-
> > From
Non-root users shouldn't be able to try to trigger a VBIOS flash
or query the flashing status. This should be reserved for users with the
appropriate permissions.
Fixes: 8424f2ccb3c0 ("drm/amdgpu/psp: Add vbflash sysfs interface support")
Reviewed-by: Alex Deucher
Signed-off-by: Mario Limonciell
The VBIOS image update flow requires userspace to:
1) Write the image to `psp_vbflash`
2) Read `psp_vbflash`
3) Poll `psp_vbflash_status` to check for completion
If userspace reads `psp_vbflash` before writing an image, it's
possible that it causes problems that can put the dGPU into an invalid
st
On 2023-06-07 13:32, Jonathan Kim wrote:
Legacy debug devices limited to pinning a single debug VMID for debugging
are the only devices that require disabling GFX OFF while accessing
debug registers. Debug devices that support multi-process debugging
rely on the hardware scheduler to update de
[Public]
> -Original Message-
> From: Kuehling, Felix
> Sent: Wednesday, June 7, 2023 2:20 PM
> To: amd-gfx@lists.freedesktop.org; Kim, Jonathan
> Cc: Huang, JinHuiEric
> Subject: Re: [PATCH] drm/amdkfd: fix and enable debugging for gfx11
>
>
> On 2023-06-07 13:26, Jonathan Kim wrote:
>
On 2023-06-07 13:26, Jonathan Kim wrote:
There are a few fixes required to enable gfx11 debugging.
First, ADD_QUEUE.trap_en is an inappropriate place to toggle
a per-process register so move it to SET_SHADER_DEBUGGER.trap_en.
When ADD_QUEUE.skip_process_ctx_clear is set, MES will prioritize
th
On Wed, Jun 7, 2023 at 4:42 AM Felix Richter wrote:
>
> Hi Guys,
>
> so I checked, the kernel I am running has this commit
> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> /commit/?id=08da182175db4c7f80850354849d95f2670e8cd9) applied already!
>
> https://github.com/ju6ge/lin
On 2023-06-07 13:27, Felix Kuehling wrote:
On 2023-06-06 12:24, James Zhu wrote:
Don't sleep when event age unmatch, and update last_event_age.
It is only for KFD_EVENT_TYPE_SIGNAL which is checked by user space.
Signed-off-by: James Zhu
---
drivers/gpu/drm/amd/amdkfd/kfd_events.c | 15 +++
[Public]
Thanks Michel.
Do you see the issue if you force disable FAMS? The following diff should do:
diff --git a/drivers/gpu/drm/amd/display/dc/dcn30/dcn30_resource.c
b/drivers/gpu/drm/amd/display/dc/dcn30/dcn30_resource.c
index f4ee4b3df596..475c16aab518 100644
--- a/drivers/gpu/drm/amd/dis
[Public]
+ Felix (typo on email)
> -Original Message-
> From: Kim, Jonathan
> Sent: Wednesday, June 7, 2023 1:32 PM
> To: amd-gfx@lists.freedesktop.org
> Cc: felix.kuel...@amd.com; Huang, JinHuiEric ;
> Kim, Jonathan
> Subject: [PATCH] drm/amdkfd: optimize gfx off enable toggle for debu
[Public]
+ Felix (typo on email)
> -Original Message-
> From: Kim, Jonathan
> Sent: Wednesday, June 7, 2023 1:27 PM
> To: amd-gfx@lists.freedesktop.org
> Cc: felix.kuel...@amd.com; Huang, JinHuiEric ;
> Kim, Jonathan
> Subject: [PATCH] drm/amdkfd: fix and enable debugging for gfx11
>
>
Legacy debug devices limited to pinning a single debug VMID for debugging
are the only devices that require disabling GFX OFF while accessing
debug registers. Debug devices that support multi-process debugging
rely on the hardware scheduler to update debug registers and do not run
into GFX OFF acc
On 2023-06-06 12:24, James Zhu wrote:
Don't sleep when event age unmatch, and update last_event_age.
It is only for KFD_EVENT_TYPE_SIGNAL which is checked by user space.
Signed-off-by: James Zhu
---
drivers/gpu/drm/amd/amdkfd/kfd_events.c | 15 +++
1 file changed, 15 insertions(+
There are a few fixes required to enable gfx11 debugging.
First, ADD_QUEUE.trap_en is an inappropriate place to toggle
a per-process register so move it to SET_SHADER_DEBUGGER.trap_en.
When ADD_QUEUE.skip_process_ctx_clear is set, MES will prioritize
the SET_SHADER_DEBUGGER.trap_en setting.
Secon
On 2023-06-07 13:17, Felix Kuehling wrote:
On 2023-06-06 12:24, James Zhu wrote:
Add event age tracking
Signed-off-by: James Zhu
---
include/uapi/linux/kfd_ioctl.h | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/kfd_ioctl.h
b/include/
On 2023-06-06 12:24, James Zhu wrote:
Add event age tracking
Signed-off-by: James Zhu
---
include/uapi/linux/kfd_ioctl.h | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/kfd_ioctl.h b/include/uapi/linux/kfd_ioctl.h
index 1781e7669982..eeb2
Allow the user to specify -2 as auto enabled with displays.
By default we don't enter runtime suspend when there are
displays attached because it does not work well in some
desktop environments due to the driver sending hotplug
events on resume in case any new displays were attached
while the GPU
On 6/6/23 20:01, Pillai, Aurabindo wrote:
>
> I'm attaching another DMCUB firmware which has the bug fix for the hang we
> saw at our end and some added tracing enabled.
Still runs into the newer hang when starting a KDE Plasma Wayland session.
Should I try this for starting the game without th
DDR5 channels are 32 bit rather than 64, report the width properly
in the log.
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2468
Signed-off-by: Alex Deucher
---
.../gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c | 20 +--
1 file changed, 14 insertions(+), 6 deletions(-)
diff
The wptr needs to be incremented at at least 64 dword intervals,
use 256 to align with windows. This should fix potential hangs
with unaligned updates.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c | 4 ++--
drivers/gpu/drm/amd/amdgpu/sdma_v4_4_2.c | 4 ++--
2 files c
[Public]
Series is:
Acked-by: Alex Deucher
From: Huang, Tim
Sent: Wednesday, June 7, 2023 4:02 AM
To: amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ; Zhang, Yifan
; Liu, Aaron ; Guo, Shikai
; Huang, Tim
Subject: [PATCH 3/3] drm/amd/pm: enable more Psta
[AMD Official Use Only - General]
Acked-by: Alex Deucher
From: amd-gfx on behalf of Deng, Emily
Sent: Tuesday, June 6, 2023 9:16 PM
To: Deng, Emily ; amd-gfx@lists.freedesktop.org
Subject: RE: [PATCH] drm/amdgpu/mmsch: Correct the definition for mmsch init
h
Thanks! All of the core DRM patches (1-6) are
Reviewed-by: Simon Ser
Acked-by: Alex Deucher
On Wed, Jun 7, 2023 at 7:09 AM shikaguo wrote:
>
> This patch enables following UMD stable Pstates profile levels for
> power_dpm_force_performance_level interface.
>
> - profile_peak
> - profile_min_mclk
> - profile_min_sclk
> - profile_standard
>
> Signed-off-by: shikag
On 2023-06-07 11:27, Mukul Joshi wrote:
This patch fixes a regression caused by a bad merge where
the handling of reserved SDMA queues was accidentally removed.
With the fix, the reserved SDMA queues are again correctly
marked as unavailable for allocation.
Fixes: c27842c84a848 ("drm/amdkfd: U
This patch fixes a regression caused by a bad merge where
the handling of reserved SDMA queues was accidentally removed.
With the fix, the reserved SDMA queues are again correctly
marked as unavailable for allocation.
Fixes: c27842c84a848 ("drm/amdkfd: Update SDMA queue management for GFX9.4.3")
S
Rename mman.entity to mman.high_pr to make the distinction
clearer that this is a high priority scheduler. Similarly,
rename the recently added mman.delayed to mman.low_pr to
make it clear it is a low priority scheduler.
No functional change in this patch.
Signed-off-by: Mukul Joshi
---
drivers/
In order to IGT test colorspace we'll want to print
the currently enabled colorspace on a stream. We add
a new debugfs to do so, using the same scheme as
current bpc reporting.
This might also come in handy when debugging display
issues.
v4:
- Fix function doc comment
- Fix sRGB debug print
Sign
From: Joshua Ashton
Replace the messy two if-else chains here that were
on the same value with a switch on the enum.
Signed-off-by: Joshua Ashton
Signed-off-by: Harry Wentland
Reviewed-by: Harry Wentland
Cc: Pekka Paalanen
Cc: Sebastian Wick
Cc: vitaly.pros...@amd.com
Cc: Joshua Ashton
Cc
From: Joshua Ashton
Given that we always pass dm_state into here now, this won't ever
trigger anymore.
This is needed for we will always fail mode validation with invalid
clocks or link bandwidth errors.
Signed-off-by: Joshua Ashton
Signed-off-by: Harry Wentland
Reviewed-by: Harry Wentland
Look at connector->colorimetry to determine output colorspace.
We don't want to impact current SDR behavior, so
DRM_MODE_COLORIMETRY_DEFAULT preserves current behavior.
Also add support to explicitly set BT601 and BT709.
v4:
- Roll support for BT709 and BT601 into this patch
- Add default case t
We need the connector_state for colorspace and scaling information
and can get it from connector->state.
Signed-off-by: Harry Wentland
Reviewed-by: Joshua Ashton
Cc: Pekka Paalanen
Cc: Sebastian Wick
Cc: vitaly.pros...@amd.com
Cc: Joshua Ashton
Cc: Simon Ser
Cc: Melissa Wen
Cc: dri-de...@l
v3: Fix kerneldocs (kernel test robot)
v4: Avoid returning NULL from drm_get_colorspace_name
Signed-off-by: Harry Wentland
Reviewed-by: Sebastian Wick
Reviewed-by: Joshua Ashton
Cc: Pekka Paalanen
Cc: Sebastian Wick
Cc: vitaly.pros...@amd.com
Cc: Uma Shankar
Cc: Ville Syrjälä
Cc: Joshua A
Drivers might not support all colorspaces defined in
dp_colorspaces and hdmi_colorspaces. This results in
undefined behavior when userspace is setting an
unsupported colorspace.
Allow drivers to pass the list of supported colorspaces
when creating the colorspace property.
v2:
- Use 0 to indicate
We need to signal mode_changed to make sure we update the output
colorspace.
v2: No need to call drm_hdmi_avi_infoframe_colorimetry as DC does its
own infoframe packing.
Signed-off-by: Harry Wentland
Reviewed-by: Leo Li
Reviewed-by: Joshua Ashton
Cc: Pekka Paalanen
Cc: Sebastian Wick
Cc
We want compositors to be able to set the output
colorspace on DP and HDMI outputs, based on the
caps reported from the receiver via EDID.
Signed-off-by: Harry Wentland
Reviewed-by: Joshua Ashton
Cc: Pekka Paalanen
Cc: Sebastian Wick
Cc: vitaly.pros...@amd.com
Cc: Joshua Ashton
Cc: Simon Ser
We an use bitfields to track the support ones for HDMI
and DP. This allows us to print colorspaces in a consistent
manner without needing to know whether we're dealing with
DP or HDMI.
v4:
- Rename _MAX to _COUNT and leave comment to indicate
it's not a valid value
- Fix misplaced function doc
Signed-off-by: Harry Wentland
Reviewed-by: Sebastian Wick
Reviewed-by: Joshua Ashton
Cc: Pekka Paalanen
Cc: Sebastian Wick
Cc: vitaly.pros...@amd.com
Cc: Uma Shankar
Cc: Ville Syrjälä
Cc: Joshua Ashton
Cc: Jani Nikula
Cc: Simon Ser
Cc: Ville Syrjälä
Cc: Melissa Wen
Cc: dri-de...@lists.
From: Joshua Ashton
To match the other enums, and add more information about these values.
v2:
- Specify where an enum entry comes from
- Clarify DEFAULT and NO_DATA behavior
- BT.2020 CYCC is "constant luminance"
- correct type for BT.601
v4:
- drop DP/HDMI clarifications that might create
This patchset is based on Joshua's previous patchset [1], as well
as my previous patchset [2].
It is
- enabling support for the colorspace property in amdgpu, as well as
- allowing drivers to specify the supported set of colorspaces, and
Colorspace, Infoframes, and YCbCr matrix
--
This allows us to use strongly typed arguments.
v2:
- Bring NO_DATA back
- Provide explicit enum values
v3:
- Drop unnecessary '&' from kerneldoc (emersion)
v4:
- Fix Normal Colorimetry comment
Signed-off-by: Harry Wentland
Reviewed-by: Simon Ser
Reviewed-by: Sebastian Wick
Reviewed-by: Pe
[AMD Official Use Only - General]
Reviewed-by: Mukul Joshi
> -Original Message-
> From: Kim, Jonathan
> Sent: Wednesday, June 7, 2023 10:39 AM
> To: amd-gfx@lists.freedesktop.org
> Cc: Joshi, Mukul ; Kuehling, Felix
> ; Kim, Jonathan ;
> Joshi, Mukul
> Subject: [PATCH] drm/amdkfd: fix
Exception handling for vmfaults should be raised with additional data.
Reported-by: Mukul Joshi
Signed-off-by: Jonathan Kim
---
drivers/gpu/drm/amd/amdkfd/kfd_events.c | 34 +++--
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_
Fixes the following gcc with W=1:
In file included from ./include/linux/string.h:253,
from ./include/linux/bitmap.h:11,
from ./include/linux/cpumask.h:12,
from ./arch/x86/include/asm/cpumask.h:5,
from ./arch/x86/include/asm/msr.h:
I can't see the other patches in this series, so I'm missing some
context. I don't understand what "process isolation between graphics and
compute" means here. It seems to be unrelated to KFD compute. This patch
seems to be mostly about handling of reserved VMIDs. Maybe you're trying
to avoid r
[AMD Official Use Only - General]
Hi Shikai,
Comments inline.
From: Guo, Shikai
Sent: Wednesday, June 7, 2023 7:07 PM
To: amd-gfx@lists.freedesktop.org
Cc: Liang, Prike ; Liu, Aaron ; Huang,
Tim ; Guo, Shikai
Subject: [PATCH] drm/amd/pm: enable more Pstates p
Am 2023-06-06 um 18:53 schrieb Philip Yang:
If hmm_range_fault returns -EBUSY, we should call hmm_range_fault again
to validate the remaining pages. On one system with NUMA auto balancing
enabled, hmm_range_fault takes 6 seconds for 1GB range because CPU
migrate the range one page at a time. To
On 6/6/23 17:36, Alex Deucher wrote:
> 0x5b70 is a missing RV370 secondary id. Add it so
> we don't try and probe it with amdgpu.
>
> Cc: mic...@daenzer.net
> Signed-off-by: Alex Deucher
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/dr
[AMD Official Use Only - General]
Hi Lyude,
Much appreciated!
Will update and send out another version.
Thanks,
Wayne Lin
> -Original Message-
> From: Lyude Paul
> Sent: Wednesday, June 7, 2023 6:03 AM
> To: Lin, Wayne ; amd-gfx@lists.freedesktop.org
> Cc: ville.syrj...@linux.intel.com;
From: Aric Cyr
This version brings along following fixes:
- Improvement on eDP
- PSR bug fixes
- SubVP bug fixes
- Improvements on pipe handling to address potential issues
- Freesync bug fix
- DPIA bug fix
- Fix multi-display issues
Acked-by: Stylon Wang
Signed-off-by: Aric Cyr
---
drivers/g
From: Dmytro Laktyushkin
The k1/k2 pixel rate dividers in dccg should only be updated on stream enable
and do not actually depend on whether odm combine is active.
This removes an on flip update of these and fixes the calculate function
to ignore odm status for dp steams.
Acked-by: Stylon Wang
From: Samson Tam
Revert commit b957de69c4c8 ("drm/amd/display: reallocate DET for dual displays
with high pixel rate ratio")
[Why]
Previously had modified DET allocation algorithm to allocate less DET
segments for lower pixel rate display and more DET segments for higher
pixel rate display. Bu
From: Peichen Huang
[Why]
DPIA doesn't support UHBR, driver should not enable UHBR
for dp tunneling
[How]
limit DPIA link rate to HBR3
Cc: Mario Limonciello
Cc: Alex Deucher
Cc: sta...@vger.kernel.org
Acked-by: Stylon Wang
Signed-off-by: Peichen Huang
Reviewed-by: Mustapha Ghaddar
---
dri
From: Alvin Lee
[Description]
- Missed color / CSC updates in fast update path
which caused Custom Color to break.
- Add color / CSC updates to new fast update path
to fix custom color
Acked-by: Stylon Wang
Signed-off-by: Alvin Lee
Reviewed-by: Jun Lei
---
.../drm/amd/display/dc/core/dc_
From: Austin Zheng
Why:
Some EDIDs report a minimum refresh rate lower than what HW can support
How:
Add a check to calculate minimum supported refresh rate with current timing
and use that as the minimum if a lower one is passed in
Acked-by: Stylon Wang
Signed-off-by: Austin Zheng
Reviewed-b
From: Artem Grishin
[Why]
When iterating over all pipes in the loop, the CRB allocation algorithm
may potentially skip some of the pipes. Previously, the current pipe
index didn't get updated in this case, causing incorrect outcome.
[How]
Increment the pipe index when skipping over a pipe in the
From: Daniel Miess
Revert commit 6c2c207e4a24 ("drm/amd/display: Move DCN314 DOMAIN power control
to DMCUB")
[Why]
Controling hubp power gating using the DMCUB isn't stable so we
are reverting this change to move control back into the driver
Acked-by: Stylon Wang
Signed-off-by: Daniel Miess
From: Alvin Lee
[Description]
PSR implementation in FW has inline polling which can poll for up
to 1ms. This will interfere with SubVP because SubVP is timing
sensitive and can't tolerate up to 1ms worth of delay before
handling vertical or VLINE interrupts. Therefore block SubVP + DRR
cases if D
From: Saaem Rizvi
[Why and How]
We should not disable phantom pipes in this sequence, as this should be
controlled by FW. Furthermore, the previous programming sequence would
have enabled the phantom pipe in driver as well, causing corruption.
This change should avoid this from occuring.
Cc: Mar
From: Alvin Lee
Re-enable SubVP high refresh now that it is fixed
for displays with high refresh rates.
Acked-by: Stylon Wang
Signed-off-by: Alvin Lee
Reviewed-by: Saaem Rizvi
---
drivers/gpu/drm/amd/display/dc/dcn32/dcn32_resource.c | 2 +-
drivers/gpu/drm/amd/display/dc/dcn321/dcn321_res
From: Daniel Miess
[Why & How]
Bugs preventing DPP/HUBP power gating have been addressed
so this should be reenabled on dcn314 for sufficient
hardware rev versions
Acked-by: Stylon Wang
Signed-off-by: Daniel Miess
Reviewed-by: Nicholas Kazlauskas
---
.../gpu/drm/amd/display/dc/dcn314/dcn314_
From: Alvin Lee
[Description]
- SubVP high refresh should only be enabled if all displays
are >= 120hz. We do not want to accidentally enables configs
such as 60hz[SubVP] + 120hz[SubVP]
- Ensure that the SubVP config generation code does not produce
configs such as 60hz[SubVP] + 120hz[SubVP
From: Tom Chung
[Why]
dmub_psr_get_state() return an invalid PSR state while disable
the PSR because convert_psr_state() doesn't recognize the state
that return from DMCUB.
[How]
Add a PSR state to make the dmub_psr_get_state() return a
correct PSR state.
Acked-by: Stylon Wang
Signed-off-by: T
From: Tom Chung
[Why]
When the PSR enabled. If you try to adjust the timing parameters,
it may cause system hang. Because the timing mismatch with the
DMCUB settings.
[How]
Disable the PSR before adjusting timing parameters.
Cc: Mario Limonciello
Cc: Alex Deucher
Cc: sta...@vger.kernel.org
Ac
From: Aric Cyr
Acked-by: Stylon Wang
Signed-off-by: Aric Cyr
---
drivers/gpu/drm/amd/display/dc/dc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/display/dc/dc.h
b/drivers/gpu/drm/amd/display/dc/dc.h
index 7cf3e9510043..5c906b007e4d 100644
--- a/driv
From: Fangzhi Zuo
Any invalid mode from hw perspective should be given corresponding
error code, otherwise it leads to confusing warning message
"[drm] Mode Validation Warning: Validation OK failed validation."
Acked-by: Stylon Wang
Signed-off-by: Fangzhi Zuo
Reviewed-by: Dmytro Laktyushkin
-
From: Austin Zheng
Why:
Log DP2 data to be used for debugging purposes
How:
Check the reported link rate of the DP connection and
translate it to the DP version.
Acked-by: Stylon Wang
Signed-off-by: Austin Zheng
Reviewed-by: Martin Leung
---
drivers/gpu/drm/amd/display/dc/dc.h | 6
From: Hersen Wu
[Why] within dc_link_detect, edp edid is read only for the first time
and saved. edid will not be read after the first time read. to run edp
edid read test, need read edp edid for each dc_link_detect. dc->config
flag allow_edp_hotplug_detection could be used for edp edid test.
[H
From: Hersen Wu
[Why] most edp support only timings from edid. applying
non-edid timings, especially those timings out of edp
bandwidth, may damage edp.
[How] do not add non-edid timings for edp.
Cc: Mario Limonciello
Cc: Alex Deucher
Cc: sta...@vger.kernel.org
Acked-by: Stylon Wang
Signed-o
This DC patchset brings improvements in multiple areas. In summary, we
highlight:
- Improvement on eDP
- PSR bug fixes
- SubVP bug fixes
- Improvements on pipe handling to address potential issues
- Freesync bug fix
- DPIA bug fix
- Fix multi-display issues
Cc: Daniel Wheeler
Alvin Lee (4):
Am 07.06.23 um 12:57 schrieb Chong Li:
enforce process isolation between graphics and compute via using the same
reserved vmid.
v2: remove params "struct amdgpu_vm *vm" from
amdgpu_vmid_alloc_reserved and amdgpu_vmid_free_reserved.
Signed-off-by: Chong Li
Reviewed-by: Christian König
This patch enables following UMD stable Pstates profile levels for
power_dpm_force_performance_level interface.
- profile_peak
- profile_min_mclk
- profile_min_sclk
- profile_standard
Signed-off-by: shikaguo
---
.../drm/amd/pm/swsmu/smu13/yellow_carp_ppt.c | 94 ++-
.../drm/am
enforce process isolation between graphics and compute via using the same
reserved vmid.
v2: remove params "struct amdgpu_vm *vm" from
amdgpu_vmid_alloc_reserved and amdgpu_vmid_free_reserved.
Signed-off-by: Chong Li
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
drivers/gpu/drm/amd/a
Hi,
On 2023/6/7 17:09, Chen, Guchun wrote:
[Public]
It's
https://gitlab.freedesktop.org/agd5f/linux/-/tree/amd-staging-drm-next?ref_type=heads.
Latest patches including yours's will be pushed to this branch after a while.
Now I know, thanks for your kindness reply.
Regards,
Guchun
On Tuesday, June 6th, 2023 at 22:25, Harry Wentland
wrote:
> + if (supported_colorspaces != 0 && (colorspaces & BIT(i)) == 0)
This patch actually also introduces a change in behavior: passing no
colorspace will make the function advertise all colorspaces. I have a
hard time understa
Hi Guys,
so I checked, the kernel I am running has this commit
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
/commit/?id=08da182175db4c7f80850354849d95f2670e8cd9) applied already!
https://github.com/ju6ge/linux/commit/917680e6056aa288cac288d3afd2745d372beb61u
And the bug
On Tuesday, June 6th, 2023 at 22:26, Harry Wentland
wrote:
> -int drm_mode_create_hdmi_colorspace_property(struct drm_connector *connector)
> +int drm_mode_create_hdmi_colorspace_property(struct drm_connector *connector,
> + u32 supported_colorspaces)
>
On Tuesday, June 6th, 2023 at 22:25, Harry Wentland
wrote:
> We an use bitfields to track the support ones for HDMI
Typo: "We can"
[Public]
With the 3 nitpicks fixed in patch 1, the series are: Acked-by: Guchun Chen
Regards,
Guchun
> -Original Message-
> From: amd-gfx On Behalf Of Alex
> Deucher
> Sent: Tuesday, June 6, 2023 11:40 PM
> To: Deucher, Alexander
> Cc: samuel.pitoi...@gmail.com; amd-gfx@lists.freedes
[Public]
3 nitpick comments.
> -Original Message-
> From: amd-gfx On Behalf Of Alex
> Deucher
> Sent: Friday, May 26, 2023 12:52 AM
> To: amd-gfx@lists.freedesktop.org
> Cc: Deucher, Alexander ;
> samuel.pitoi...@gmail.com
> Subject: [PATCH 1/3] drm/amdgpu: add cached GPU fault structure
[Public]
It's
https://gitlab.freedesktop.org/agd5f/linux/-/tree/amd-staging-drm-next?ref_type=heads.
Latest patches including yours's will be pushed to this branch after a while.
Regards,
Guchun
> -Original Message-
> From: amd-gfx On Behalf Of Sui
> Jingfeng
> Sent: Wednesday, June 7
Add the ability to control the vclk and dclk frequency by
power_dpm_force_performance_level interface.
Signed-off-by: Tim Huang
---
.../drm/amd/pm/swsmu/smu13/smu_v13_0_4_ppt.c | 29 +++
1 file changed, 29 insertions(+)
diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_
This patch enables following UMD stable Pstates profile
levels for power_dpm_force_performance_level interface.
- profile_peak
- profile_min_mclk
- profile_min_sclk
- profile_standard
Signed-off-by: Tim Huang
---
.../drm/amd/pm/swsmu/smu13/smu_v13_0_4_ppt.c | 54 ++-
1 file cha
PMFW use the left-shifted 16 bits argument to set the VCLK
DPM frequency for SMU v13.0.4.
Signed-off-by: Tim Huang
---
drivers/gpu/drm/amd/pm/swsmu/inc/smu_v13_0.h | 2 ++
drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_4_ppt.c | 11 +--
2 files changed, 11 insertions(+), 2 deletio
Root PD BO should be reserved before unmap and remove
a bo_va from VM otherwise lockdep will complain.
v2: check fpriv->csa_va is not NULL instead of amdgpu_mcbp (christian)
[14616.936827] WARNING: CPU: 6 PID: 1711 at
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c:1762 amdgpu_vm_bo_del+0x399/0x3f0
[amd
From: Ruili Ji
Starting from GC_11_0_4, flag trap_en should be enabled for trap handler.
Signed-off-by: Ruili Ji
Signed-off-by: Aaron Liu
Reviewed-by: Alex Deucher
---
drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
95 matches
Mail list logo
