tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
branch HEAD: 0f067394dd3b2af3263339cf7183bdb6ee0ac1f8 Add linux-next specific
files for 20240109
Error/Warning reports:
https://lore.kernel.org/oe-kbuild-all/202401101414.8gvbgmxw-...@intel.com
Error
On 1/9/2024 6:30 PM, Le Ma wrote:
Use debug_mask=0x8 param to help isolating data path issues
on new systems in early phase.
v2: rename the flag for explicitness (lijo)
Signed-off-by: Le Ma
Series is
Reviewed-by: Lijo Lazar
Thanks,
Lijo
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h
[AMD Official Use Only - General]
I agree.
Thanks,
Candice
-Original Message-
From: Zhang, Hawking
Sent: Wednesday, January 10, 2024 10:48 AM
To: Li, Candice ; amd-gfx@lists.freedesktop.org
Cc: Li, Candice
Subject: RE: [PATCH] drm/amd/pm: Enable smu v13_0_6 eccinfo in firmware query
[AMD Official Use Only - General]
Let' s see if we can retire the get_ecc_info callback since from smu_v13.
(i.e., do not provide the callback implementation). What we just need to ensure
the driver can fallback to direct poll mode when aca debug mode is enabled,
this applies to both error
ping...
On 1/5/2024 2:05 PM, Ma Jun wrote:
> Fix the warning info below during mode1 reset.
> [ +0.04] Call Trace:
> [ +0.04]
> [ +0.06] ? show_regs+0x6e/0x80
> [ +0.11] ? __flush_work.isra.0+0x2e8/0x390
> [ +0.05] ? __warn+0x91/0x150
> [ +0.09] ?
smu v13_0_6 eccinfo is supported in firmware query mode only.
Signed-off-by: Candice Li
---
drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_6_ppt.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_6_ppt.c
[AMD Official Use Only - General]
Sorry, please ignore the patch.
Thanks,
Candice
-Original Message-
From: Li, Candice
Sent: Wednesday, January 10, 2024 10:11 AM
To: amd-gfx@lists.freedesktop.org
Cc: Li, Candice
Subject: [PATCH] drm/amd/pm: Enable smu v13_0_6 eccinfo in firmware
smu v13_0_6 eccinfo is supported in firmware query mode only.
Signed-off-by: Candice Li
---
drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_6_ppt.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu13/smu_v13_0_6_ppt.c
[AMD Official Use Only - General]
Reviewed-by: Hawking Zhang
Regards,
Hawking
-Original Message-
From: amd-gfx On Behalf Of Alex Deucher
Sent: Tuesday, January 9, 2024 23:46
To: amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander
Subject: [PATCH] drm/amdgpu: drop exp hw support check
[Public]
Reviewed-by: Tim Huang
-Original Message-
From: Zhang, Yifan
Sent: Wednesday, January 10, 2024 8:56 AM
To: amd-gfx@lists.freedesktop.org
Cc: Deucher, Alexander ; Yu, Lang ;
Ma, Li ; Huang, Tim ; Zhang, Yifan
Subject: [PATCH] drm/amdgpu: update regGL2C_CTRL4 value in golden
This patch to update regGL2C_CTRL4 in golden setting.
Signed-off-by: Yifan Zhang
---
drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
b/drivers/gpu/drm/amd/amdgpu/gfx_v11_0.c
index
[Public]
> -Original Message-
> From: amd-gfx On Behalf Of
> Deucher, Alexander
> Sent: Tuesday, January 9, 2024 5:29 PM
> To: Alexander Koskovich
> Cc: amd-gfx@lists.freedesktop.org
> Subject: RE: Documentation for RGB strip on RX 7900 XTX (Reference)
> >
> > -Original Message-
Hi,
On Tue, 9 Jan 2024 at 18:12, Andri Yngvason wrote:
> + * active color format:
> + * This read-only property tells userspace the color format actually used
> + * by the hardware display engine "on the cable" on a connector. The
> chosen
> + * value depends on hardware
On 1/9/2024 2:05 PM, Philip Yang wrote:
After svm range partial migrating to system memory, unmap to cleanup the
corresponding dma_addr vram domain flag, otherwise the future split will
get incorrect vram_pages and actual loc.
After range spliting, set new range and old range actual_loc:
new
[Public]
> -Original Message-
> From: Alexander Koskovich
> Sent: Tuesday, January 9, 2024 4:59 PM
> To: Deucher, Alexander
> Cc: amd-gfx@lists.freedesktop.org
> Subject: RE: Documentation for RGB strip on RX 7900 XTX (Reference)
>
> Is the AIB/OEM for this board not AMD?
>
LLVM moved their issue tracker from their own Bugzilla instance to
GitHub issues. While all of the links are still valid, they may not
necessarily show the most up to date information around the issues, as
all updates will occur on GitHub, not Bugzilla.
Another complication is that the Bugzilla
reviews.llvm.org was LLVM's Phabricator instances for code review. It
has been abandoned in favor of GitHub pull requests. While the majority
of links in the kernel sources still work because of the work Fangrui
has done turning the dynamic Phabricator instance into a static archive,
there are
reviews.llvm.org was LLVM's Phabricator instances for code review. It
has been abandoned in favor of GitHub pull requests. While the majority
of links in the kernel sources still work because of the work Fangrui
has done turning the dynamic Phabricator instance into a static archive,
there are
/bpf/prog_tests/xdpwall.c | 2 +-
.../selftests/bpf/progs/test_core_reloc_type_id.c | 2 +-
23 files changed, 40 insertions(+), 40 deletions(-)
---
base-commit: 0dd3ee31125508cd67f7e7172247f05b7fd1753a
change-id: 20240109-update-llvm-links-d03f9d649e1e
Best regards,
--
Nathan Chancellor
[AMD Official Use Only - General]
> -Original Message-
> From: Alexander Koskovich
> Sent: Tuesday, January 9, 2024 3:27 PM
> To: Deucher, Alexander
> Cc: amd-gfx@lists.freedesktop.org
> Subject: RE: Documentation for RGB strip on RX 7900 XTX (Reference)
>
> Doe AMD have documentation
After svm range partial migrating to system memory, unmap to cleanup the
corresponding dma_addr vram domain flag, otherwise the future split will
get incorrect vram_pages and actual loc.
After range spliting, set new range and old range actual_loc:
new range actual_loc is 0 if new->vram_pages is
On 2024-01-08 18:17, Chen, Xiaogang
wrote:
With a
nitpick below, this patch is
Reviewed-by:Xiaogang Chen
On 1/8/2024 4:36 PM, Philip Yang wrote:
After range spliting, set new range and
old range
From: Werner Sembach
This commit implements the "preferred color format" drm property for the
AMD GPU driver.
Signed-off-by: Werner Sembach
Signed-off-by: Andri Yngvason
Tested-by: Andri Yngvason
---
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 30 +++
From: Werner Sembach
This commit implements the "preferred color format" drm property for the
Intel GPU driver.
Signed-off-by: Werner Sembach
Co-developed-by: Andri Yngvason
Signed-off-by: Andri Yngvason
Tested-by: Andri Yngvason
---
drivers/gpu/drm/i915/display/intel_dp.c | 16
This is a subset of patches, originally submitted by Werner Sembach
titled: New uAPI drm properties for color management [1]
I've rebased against the current master branch, made modifications where
needed, and tested with both HDMI and DP on both Intel and AMD hardware,
using modified sway [2]
From: Werner Sembach
This commit implements the "active color format" drm property for the Intel
GPU driver.
Signed-off-by: Werner Sembach
Signed-off-by: Andri Yngvason
Tested-by: Andri Yngvason
---
drivers/gpu/drm/i915/display/intel_display.c | 33
From: Werner Sembach
Add a new general drm property "preferred color format" which can be used
by userspace to tell the graphic drivers to which color format to use.
Possible options are:
- auto (default/current behaviour)
- rgb
- ycbcr444
- ycbcr422 (not supported by both
From: Werner Sembach
Add a new general drm property "active color format" which can be used by
graphic drivers to report the used color format back to userspace.
There was no way to check which color format got actually used on a given
monitor. To surely predict this, one must know the exact
From: Werner Sembach
Remove unnecessary SIGNAL_TYPE_HDMI_TYPE_A check that was performed in the
drm_mode_is_420_only() case, but not in the drm_mode_is_420_also() &&
force_yuv420_output case.
Without further knowledge if YCbCr 4:2:0 is supported outside of HDMI,
there is no reason to use RGB
From: Werner Sembach
This commit implements the "active color format" drm property for the AMD
GPU driver.
Signed-off-by: Werner Sembach
Signed-off-by: Andri Yngvason
Tested-by: Andri Yngvason
---
.../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 42 ++-
No longer needed.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_discovery.c
index b8fde08aec8e..f96811bbe40e 100644
---
[Public]
> -Original Message-
> From: Alexander Koskovich
> Sent: Monday, January 8, 2024 7:22 PM
> To: Deucher, Alexander
> Cc: amd-gfx@lists.freedesktop.org
> Subject: RE: Documentation for RGB strip on RX 7900 XTX (Reference)
>
> Currently the reference cooler from AMD does not have
On 09/01/2024 14:57, Christian König wrote:
Am 09.01.24 um 15:26 schrieb Daniel Vetter:
On Tue, 9 Jan 2024 at 14:25, Tvrtko Ursulin
wrote:
On 09/01/2024 12:54, Daniel Vetter wrote:
On Tue, Jan 09, 2024 at 09:30:15AM +, Tvrtko Ursulin wrote:
On 09/01/2024 07:56, Christian König wrote:
Am 09.01.24 um 15:26 schrieb Daniel Vetter:
On Tue, 9 Jan 2024 at 14:25, Tvrtko Ursulin
wrote:
On 09/01/2024 12:54, Daniel Vetter wrote:
On Tue, Jan 09, 2024 at 09:30:15AM +, Tvrtko Ursulin wrote:
On 09/01/2024 07:56, Christian König wrote:
Am 07.12.23 um 19:02 schrieb Alex Deucher:
On Tue, 9 Jan 2024 at 14:25, Tvrtko Ursulin
wrote:
>
>
> On 09/01/2024 12:54, Daniel Vetter wrote:
> > On Tue, Jan 09, 2024 at 09:30:15AM +, Tvrtko Ursulin wrote:
> >>
> >> On 09/01/2024 07:56, Christian König wrote:
> >>> Am 07.12.23 um 19:02 schrieb Alex Deucher:
> Add shared stats.
Thanks for the info, will take a look.
Also just to clarify, this is the first party AMD 7900 XTX, not a third party
AIB (e.g. Sapphire, ASRock, etc).
On Tuesday, January 9th, 2024 at 3:02 AM, Christian König
wrote:
>
>
> Am 08.01.24 um 23:32 schrieb Deucher, Alexander:
>
> > [Public]
> >
On 09/01/2024 12:54, Daniel Vetter wrote:
On Tue, Jan 09, 2024 at 09:30:15AM +, Tvrtko Ursulin wrote:
On 09/01/2024 07:56, Christian König wrote:
Am 07.12.23 um 19:02 schrieb Alex Deucher:
Add shared stats. Useful for seeing shared memory.
v2: take dma-buf into account as well
Use debug_mask=0x8 param to help isolating data path issues
on new systems in early phase.
v2: rename the flag for explicitness (lijo)
Signed-off-by: Le Ma
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 6 ++
On Tue, Jan 09, 2024 at 09:30:15AM +, Tvrtko Ursulin wrote:
>
> On 09/01/2024 07:56, Christian König wrote:
> > Am 07.12.23 um 19:02 schrieb Alex Deucher:
> > > Add shared stats. Useful for seeing shared memory.
> > >
> > > v2: take dma-buf into account as well
> > >
> > > Signed-off-by:
On 1/9/2024 3:43 PM, Le Ma wrote:
se debug_mask=0x8 param to help isolating data path issues
on new systems in early phase.
Signed-off-by: Le Ma
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 6 ++
Am 09.01.24 um 11:31 schrieb Ma Jun:
Some customer platforms do not enable mmconfig for various reasons,
such as bios bug, and therefore cannot access the GPU extend configuration
space through mmio.
When the system enters the d3cold state and resumes, the amdgpu driver
fails to resume because
Some customer platforms do not enable mmconfig for various reasons,
such as bios bug, and therefore cannot access the GPU extend configuration
space through mmio.
When the system enters the d3cold state and resumes, the amdgpu driver
fails to resume because the extend configuration space
To bring debug options into effect in early initialization phase
Signed-off-by: Le Ma
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
index
se debug_mask=0x8 param to help isolating data path issues
on new systems in early phase.
Signed-off-by: Le Ma
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 1 +
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 6 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c | 2 +-
This reverts commit 1797d97a977280ac2cec95b1b59acc5856fea11e.
Will use debug module param instead of independent module param.
Signed-off-by: Le Ma
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 2 --
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 5 -
drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c
On 1/9/2024 12:24 AM, Christian König wrote:
> Am 08.01.24 um 10:24 schrieb Ma, Jun:
>> Hi Christian,
>>
>> On 1/5/2024 9:39 PM, Christian König wrote:
>>> Am 21.12.23 um 02:58 schrieb Ma, Jun:
Hi Christian,
On 12/20/2023 10:10 PM, Christian König wrote:
> Am 19.12.23 um
int p = -1.
unsigned u = p;
int p2 = u;
p2 is -1.
Marek
On Tue, Jan 9, 2024, 03:26 Christian König wrote:
> Am 09.01.24 um 09:09 schrieb 李真能:
>
> Thanks!
>
> What about the second patch?
>
> The second patch: amdgpu: change proirity value to be consistent with
> kernel.
>
> As I want to
On 09/01/2024 07:56, Christian König wrote:
Am 07.12.23 um 19:02 schrieb Alex Deucher:
Add shared stats. Useful for seeing shared memory.
v2: take dma-buf into account as well
Signed-off-by: Alex Deucher
Cc: Rob Clark
---
drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.c | 4
Am 09.01.24 um 09:23 schrieb Alexander Koskovich:
Thanks for the info, will take a look.
Also just to clarify, this is the first party AMD 7900 XTX, not a third party
AIB (e.g. Sapphire, ASRock, etc).
Yeah, but that doesn't matter.
For the reference designs AMD basically just says how it
Thanks!
What about the second patch?
The second patch: amdgpu: change proirity value to be consistent with kernel.
As I want to pass AMDGPU_CTX_PRIORITY_LOW to kernel module drm-scheduler, if these two patches are not applyed,
It can not pass LOW priority to drm-scheduler.
Do you have any other
Currently the reference cooler from AMD does not have an existing RGB
controller for OpenRGB, that's why I was looking for documentation on the I2C
commands to send to the second SMU, so I don't risk bricking my card by sending
wrong commands during development somehow.
writeSetCMDWithData:
When the priority value is passed to the kernel, the kernel compares it with the following values:
#define AMDGPU_CTX_PRIORITY_VERY_LOW -1023#define AMDGPU_CTX_PRIORITY_LOW -512#define AMDGPU_CTX_PRIORITY_NORMAL 0#define AMDGPU_CTX_PRIORITY_HIGH 512#define
Am 09.01.24 um 09:09 schrieb 李真能:
Thanks!
What about the second patch?
The second patch: amdgpu: change proirity value to be consistent
with kernel.
As I want to pass AMDGPU_CTX_PRIORITY_LOW to kernel module
drm-scheduler, if these two patches are not applyed,
It can not pass LOW
Am 08.01.24 um 23:32 schrieb Deucher, Alexander:
[Public]
-Original Message-
From: amd-gfx On Behalf Of
Alexander Koskovich
Sent: Sunday, January 7, 2024 11:19 PM
To: amd-gfx@lists.freedesktop.org
Subject: Documentation for RGB strip on RX 7900 XTX (Reference)
Hello,
I was wondering
54 matches
Mail list logo
