This is supported by Sienna Cichlid, Navy Flounder and Dimgrey
Cavefish. For these ASICs, the target voltage calculation can be
illustrated by "voltage = voltage calculated from v/f curve +
overdrive vddgfx offset".
V2: limit the smu_version check for Sienna Cichlid only
Here are some sample usag
Enable Sienna Cichlid gfxclk/uclk overdrive support.
Change-Id: I93535076f5857c0dfeb012a993bc85a16ca4df84
Signed-off-by: Evan Quan
Acked-by: Alex Deucher
---
drivers/gpu/drm/amd/pm/amdgpu_pm.c| 3 +-
.../amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 241 ++
2 files c
Populate the bootup overdrive table settings.
Change-Id: Iaee8c8afd5cbf12008aa6ffe0e90c8ffe5aa4fe2
Signed-off-by: Evan Quan
Acked-by: Alex Deucher
---
.../amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 38 +++
1 file changed, 38 insertions(+)
diff --git a/drivers/gpu/drm/amd/pm/sw
[AMD Public Use]
One spelling error in subject, s/reservarion/reservation.
With above fixed, the patch is: Reviewed-by: Guchun Chen
Regards,
Guchun
-Original Message-
From: amd-gfx On Behalf Of Alex Deucher
Sent: Thursday, December 17, 2020 12:37 AM
To: amd-gfx@lists.freedesktop.org
C
On Thu, Dec 17, 2020 at 10:57:01AM +0800, Hou, Xiaomeng (Matthew) wrote:
> Only pmfw version behind v4.63.23.00 could support this message.
>
> Signed-off-by: Xiaomeng Hou
Reviewed-by: Huang Rui
> ---
> drivers/gpu/drm/amd/pm/swsmu/smu11/vangogh_ppt.c | 9 +++--
> 1 file changed, 7 insert
Only pmfw version behind v4.63.23.00 could support this message.
Signed-off-by: Xiaomeng Hou
---
drivers/gpu/drm/amd/pm/swsmu/smu11/vangogh_ppt.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/pm/swsmu/smu11/vangogh_ppt.c
b/drivers/gpu/drm/amd/p
On 12/16/20 6:15 PM, Daniel Vetter wrote:
On Wed, Dec 16, 2020 at 7:26 PM Andrey Grodzovsky
wrote:
On 12/16/20 12:12 PM, Daniel Vetter wrote:
On Wed, Dec 16, 2020 at 5:18 PM Christian König
wrote:
Am 16.12.20 um 17:13 schrieb Andrey Grodzovsky:
On 12/16/20 9:21 AM, Daniel Vetter wrote:
O
On Wed, Dec 16, 2020 at 7:26 PM Andrey Grodzovsky
wrote:
>
>
> On 12/16/20 12:12 PM, Daniel Vetter wrote:
> > On Wed, Dec 16, 2020 at 5:18 PM Christian König
> > wrote:
> >> Am 16.12.20 um 17:13 schrieb Andrey Grodzovsky:
> >>> On 12/16/20 9:21 AM, Daniel Vetter wrote:
> On Wed, Dec 16, 2020
Am 2020-12-16 um 5:34 p.m. schrieb Harish Kasiviswanathan:
> Signed-off-by: Harish Kasiviswanathan
> Change-Id: Ic139a8b9c8bef1df183804e543103be206405dca
Please add a patch description (what type of problem does this fix) and
remove the "Change-Id". To stop git from adding one automatically in th
On Wed, Dec 16, 2020 at 11:39 PM Alex Deucher wrote:
>
> On Wed, Dec 16, 2020 at 5:28 PM Daniel Vetter wrote:
> >
> > On Wed, Dec 16, 2020 at 02:24:20PM -0500, Alex Deucher wrote:
> > > Hi Dave, Daniel,
> > >
> > > Fixes for 5.11.
> > >
> > > The following changes since commit
> > > b10733527bfd
On Fri, Nov 13, 2020 at 03:56:41PM -0500, Bindu Ramamurthy wrote:
> From: Wayne Lin
>
> [Why]
> Instead of calculating CRC on whole frame, add flexibility to calculate
> CRC on specific frame region.
>
> [How]
> Add few crc window coordinate properties. By default, CRC is calculated
> on whole f
On Wed, Dec 16, 2020 at 5:28 PM Daniel Vetter wrote:
>
> On Wed, Dec 16, 2020 at 02:24:20PM -0500, Alex Deucher wrote:
> > Hi Dave, Daniel,
> >
> > Fixes for 5.11.
> >
> > The following changes since commit b10733527bfd864605c33ab2e9a886eec317ec39:
> >
> > Merge tag 'amd-drm-next-5.11-2020-12-09
Signed-off-by: Harish Kasiviswanathan
Change-Id: Ic139a8b9c8bef1df183804e543103be206405dca
---
drivers/gpu/drm/amd/amdkfd/kfd_device.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_device.c
b/drivers/gpu/drm/amd/amdkfd/kfd_devic
On Wed, Dec 16, 2020 at 02:24:20PM -0500, Alex Deucher wrote:
> Hi Dave, Daniel,
>
> Fixes for 5.11.
>
> The following changes since commit b10733527bfd864605c33ab2e9a886eec317ec39:
>
> Merge tag 'amd-drm-next-5.11-2020-12-09' of
> git://people.freedesktop.org/~agd5f/linux into drm-next (2020
On Wed, 16 Dec 2020 at 19:00, Alex Deucher wrote:
>
> On Mon, Dec 14, 2020 at 12:53 PM Ard Biesheuvel wrote:
> >
> > This reverts commit c38d444e44badc557cf29fdfdfb823604890ccfa.
> >
> > Simply disabling -mgeneral-regs-only left and right is risky, given that
> > the standard AArch64 ABI permits
Hi Dave, Daniel,
Fixes for 5.11.
The following changes since commit b10733527bfd864605c33ab2e9a886eec317ec39:
Merge tag 'amd-drm-next-5.11-2020-12-09' of
git://people.freedesktop.org/~agd5f/linux into drm-next (2020-12-10 16:55:53
+1000)
are available in the Git repository at:
git://peop
On 12/16/20 12:12 PM, Daniel Vetter wrote:
On Wed, Dec 16, 2020 at 5:18 PM Christian König
wrote:
Am 16.12.20 um 17:13 schrieb Andrey Grodzovsky:
On 12/16/20 9:21 AM, Daniel Vetter wrote:
On Wed, Dec 16, 2020 at 9:04 AM Christian König
wrote:
Am 15.12.20 um 21:18 schrieb Andrey Grodzovsky:
On Mon, Dec 14, 2020 at 12:53 PM Ard Biesheuvel wrote:
>
> This reverts commit c38d444e44badc557cf29fdfdfb823604890ccfa.
>
> Simply disabling -mgeneral-regs-only left and right is risky, given that
> the standard AArch64 ABI permits the use of FP/SIMD registers anywhere,
> and GCC is known to use
On Wed, Dec 16, 2020 at 6:12 PM Daniel Vetter wrote:
>
> On Wed, Dec 16, 2020 at 5:18 PM Christian König
> wrote:
> >
> > Am 16.12.20 um 17:13 schrieb Andrey Grodzovsky:
> > >
> > > On 12/16/20 9:21 AM, Daniel Vetter wrote:
> > >> On Wed, Dec 16, 2020 at 9:04 AM Christian König
> > >> wrote:
> >
On Wed, Dec 16, 2020 at 5:18 PM Christian König
wrote:
>
> Am 16.12.20 um 17:13 schrieb Andrey Grodzovsky:
> >
> > On 12/16/20 9:21 AM, Daniel Vetter wrote:
> >> On Wed, Dec 16, 2020 at 9:04 AM Christian König
> >> wrote:
> >>> Am 15.12.20 um 21:18 schrieb Andrey Grodzovsky:
> [SNIP]
> >
There is no reserveration so set the size to 0. Fixes
a regression on SR-IOV.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c
b/drivers/gpu/drm/amd/amdgpu/amdgp
Am 16.12.20 um 17:13 schrieb Andrey Grodzovsky:
On 12/16/20 9:21 AM, Daniel Vetter wrote:
On Wed, Dec 16, 2020 at 9:04 AM Christian König
wrote:
Am 15.12.20 um 21:18 schrieb Andrey Grodzovsky:
[SNIP]
While we can't control user application accesses to the mapped
buffers explicitly and hence
On 12/16/20 9:21 AM, Daniel Vetter wrote:
On Wed, Dec 16, 2020 at 9:04 AM Christian König
wrote:
Am 15.12.20 um 21:18 schrieb Andrey Grodzovsky:
[SNIP]
While we can't control user application accesses to the mapped
buffers explicitly and hence we use page fault rerouting
I am thinking that i
On Wed, Dec 16, 2020 at 9:04 AM Christian König
wrote:
>
> Am 15.12.20 um 21:18 schrieb Andrey Grodzovsky:
> > [SNIP]
> >>>
> >>> While we can't control user application accesses to the mapped
> >>> buffers explicitly and hence we use page fault rerouting
> >>> I am thinking that in this case we
Am 15.12.20 um 21:18 schrieb Andrey Grodzovsky:
[SNIP]
While we can't control user application accesses to the mapped
buffers explicitly and hence we use page fault rerouting
I am thinking that in this case we may be able to sprinkle
drm_dev_enter/exit in any such sensitive place were we mig
25 matches
Mail list logo