All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: tiancyin <tianci.yin@amd.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.1.y] Revert "drm/amd/display: Remove Phantom Pipe Check When Calculating K1 and K2"
Date: Mon, 7 Aug 2023 07:51:32 +0200	[thread overview]
Message-ID: <2023080727-constant-recreate-8742@gregkh> (raw)
In-Reply-To: <20230807021812.2797828-1-tianci.yin@amd.com>

On Mon, Aug 07, 2023 at 10:18:12AM +0800, tiancyin wrote:
> This reverts commit a2ef3163c3604788abdc060cab74c95ed44fec1a.
> ---
>  drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c b/drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c
> index f5fa7abd97fc..2f4afe40f3e6 100644
> --- a/drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c
> +++ b/drivers/gpu/drm/amd/display/dc/dcn32/dcn32_hwseq.c
> @@ -1165,6 +1165,10 @@ unsigned int dcn32_calculate_dccg_k1_k2_values(struct pipe_ctx *pipe_ctx, unsign
>  	unsigned int odm_combine_factor = 0;
>  	bool two_pix_per_container = false;
>  
> +	// For phantom pipes, use the same programming as the main pipes
> +	if (pipe_ctx->stream->mall_stream_config.type == SUBVP_PHANTOM) {
> +		stream = pipe_ctx->stream->mall_stream_config.paired_stream;
> +	}
>  	two_pix_per_container = optc2_is_two_pixels_per_containter(&stream->timing);
>  	odm_combine_factor = get_odm_config(pipe_ctx, NULL);
>  
> -- 
> 2.34.1
> 

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

      reply	other threads:[~2023-08-07  5:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  2:18 [PATCH 6.1.y] Revert "drm/amd/display: Remove Phantom Pipe Check When Calculating K1 and K2" tiancyin
2023-08-07  5:51 ` Greg KH [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=2023080727-constant-recreate-8742@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=tianci.yin@amd.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.