AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Wentland <harry.wentland@amd.com>
To: Alex Deucher <alexander.deucher@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu/display: protect dc_dsc_stream_bandwidth_in_kbps with CONFIG_DRM_AMD_DC_DCN
Date: Thu, 29 Jul 2021 15:23:28 -0400	[thread overview]
Message-ID: <b635ac5a-dbd3-f714-cb5e-2fdae2042876@amd.com> (raw)
In-Reply-To: <20210728203518.1460001-1-alexander.deucher@amd.com>

On 2021-07-28 4:35 p.m., Alex Deucher wrote:
> It's only used and enabled with DCN, so protect it.
> 
> Fixes: b6b76b0315ed7b ("drm/amd/display: Fixed EdidUtility build errors")
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

Reviewed-by: Harry Wentland <harry.wentland@amd.com>

Harry

> ---
>  drivers/gpu/drm/amd/display/dc/core/dc_link.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_link.c b/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> index 5be9d6c70ea6..8bd7f42a8053 100644
> --- a/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> +++ b/drivers/gpu/drm/amd/display/dc/core/dc_link.c
> @@ -3729,11 +3729,13 @@ uint32_t dc_bandwidth_in_kbps_from_timing(
>  	uint32_t bits_per_channel = 0;
>  	uint32_t kbps;
>  
> +#if defined(CONFIG_DRM_AMD_DC_DCN)
>  	if (timing->flags.DSC)
>  		return dc_dsc_stream_bandwidth_in_kbps(timing,
>  				timing->dsc_cfg.bits_per_pixel,
>  				timing->dsc_cfg.num_slices_h,
>  				timing->dsc_cfg.is_dp);
> +#endif
>  
>  	switch (timing->display_color_depth) {
>  	case COLOR_DEPTH_666:
> 

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      reply	other threads:[~2021-07-29 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 20:35 [PATCH] drm/amdgpu/display: protect dc_dsc_stream_bandwidth_in_kbps with CONFIG_DRM_AMD_DC_DCN Alex Deucher
2021-07-29 19:23 ` Harry Wentland [this message]

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=b635ac5a-dbd3-f714-cb5e-2fdae2042876@amd.com \
    --to=harry.wentland@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox