All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Guchun" <Guchun.Chen@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"tarequemd.hanif@yahoo.com" <tarequemd.hanif@yahoo.com>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: RE: [PATCH] drm/amdgpu: no DC support for headless chips
Date: Fri, 24 Dec 2021 08:19:04 +0000	[thread overview]
Message-ID: <DM5PR12MB2469B10EBEC2E753887089D0F17F9@DM5PR12MB2469.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CADnq5_M1uVqbdJyRyW0zZzKy3rF8FmRQseggr2g3arREKQQk2Q@mail.gmail.com>

[Public]

Hi Alex,

Thanks for clarification. The patch is: Reviewed-by: Guchun Chen <guchun.chen@amd.com> .

My concern is that amdgpu_device_has_dc_support is called at multiple places. Before this patch, for ARCTURUS and ALDEBARAN, it goes to default case, and returns true by default, but hardcoded IP discovery setting guarantees no DC is initialized on those two, so far, it's fine. However, after this patch, amdgpu_device_has_dc_support will explicitly return false, and accordingly it changed some setting/execution like driver_feature or in suspend/resume. I am not pretty sure about the impact. Anyway, we can re-visit it if there is regression.

Regards,
Guchun

-----Original Message-----
From: Alex Deucher <alexdeucher@gmail.com> 
Sent: Friday, December 24, 2021 2:16 PM
To: Chen, Guchun <Guchun.Chen@amd.com>
Cc: Deucher, Alexander <Alexander.Deucher@amd.com>; amd-gfx@lists.freedesktop.org; tarequemd.hanif@yahoo.com
Subject: Re: [PATCH] drm/amdgpu: no DC support for headless chips

On Thu, Dec 23, 2021 at 9:54 PM Chen, Guchun <Guchun.Chen@amd.com> wrote:
>
> [Public]
>
> For the first two CHIP_HAINAN and CHIP_TOPAZ, using asic_type is fine. But for CHIP_ARCTURUS and CHIP_ALDEBARAN, I wonder if there is any dc hardware harvesting info carried by harvest table in VBIOS. If that's the case, I think we can drop these two, as we can promise it by checking AMD_HARVEST_IP_DMU_MASK in amdgpu_device_has_dc_support.

There is no IP discovery table for these chips, but they don't have any display IPs in the hardcoded IP discovery info in the driver.  I don't think this should affect them, but I wasn't sure..

Alex


>
> Regards,
> Guchun
>
> -----Original Message-----
> From: amd-gfx <amd-gfx-bounces@lists.freedesktop.org> On Behalf Of 
> Alex Deucher
> Sent: Friday, December 24, 2021 3:20 AM
> To: amd-gfx@lists.freedesktop.org
> Cc: Deucher, Alexander <Alexander.Deucher@amd.com>; 
> tarequemd.hanif@yahoo.com
> Subject: [PATCH] drm/amdgpu: no DC support for headless chips
>
> Chips with no display hardware should return false for DC support.
>
> Fixes: f7f12b25823c0d ("drm/amdgpu: default to true in 
> amdgpu_device_asic_has_dc_support")
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> ---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c 
> b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> index 9dc86c5a1cad..58e2034984de 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
> @@ -3166,6 +3166,14 @@ static void amdgpu_device_detect_sriov_bios(struct amdgpu_device *adev)  bool amdgpu_device_asic_has_dc_support(enum amd_asic_type asic_type)  {
>         switch (asic_type) {
> +#ifdef CONFIG_DRM_AMDGPU_SI
> +       case CHIP_HAINAN:
> +#endif
> +       case CHIP_TOPAZ:
> +       case CHIP_ARCTURUS:
> +       case CHIP_ALDEBARAN:
> +               /* chips with no display hardware */
> +               return false;
>  #if defined(CONFIG_DRM_AMD_DC)
>         case CHIP_TAHITI:
>         case CHIP_PITCAIRN:
> --
> 2.33.1

  reply	other threads:[~2021-12-24  8:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 19:19 [PATCH] drm/amdgpu: no DC support for headless chips Alex Deucher
2021-12-24  2:54 ` Chen, Guchun
2021-12-24  6:15   ` Alex Deucher
2021-12-24  8:19     ` Chen, Guchun [this message]
2021-12-27 17:11 Alex Deucher
2021-12-28  1:54 ` Quan, Evan
2021-12-28  2:43 ` Chen, Guchun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM5PR12MB2469B10EBEC2E753887089D0F17F9@DM5PR12MB2469.namprd12.prod.outlook.com \
    --to=guchun.chen@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=tarequemd.hanif@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.