Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Jocelyn Falempe <jfalempe@redhat.com>
To: Kuo-Hsiang Chou <kuohsiang_chou@aspeedtech.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	"airlied@redhat.com" <airlied@redhat.com>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	"regressions@leemhuis.info" <regressions@leemhuis.info>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Luke Chen <luke_chen@aspeedtech.com>,
	Hungju Huang <hungju_huang@aspeedtech.com>,
	Charles Kuan <charles_kuan@aspeedtech.com>
Subject: Re: [PATCH] drm/ast: Treat AST2600 like AST2500 in most places
Date: Wed, 8 Jun 2022 15:16:58 +0200	[thread overview]
Message-ID: <c99f305f-ac4d-628b-b092-920af767a2e4@redhat.com> (raw)
In-Reply-To: <PSAPR06MB4805B23B053F80C0F23A8C6C8CA49@PSAPR06MB4805.apcprd06.prod.outlook.com>

On 08/06/2022 10:09, Kuo-Hsiang Chou wrote:
> Hi Thomas
> 
> Thanks for your suggestions!
> 
> I answer each revision inline that followed by [KH]:.

Thanks for reviewing this.
> 
> Regards,
> 
>          Kuo-Hsiang Chou
> 
> -----Original Message-----
> 
> From: Thomas Zimmermann [mailto:tzimmermann@suse.de]
> 
> Sent: Tuesday, June 07, 2022 8:03 PM
> 
> To: airlied@redhat.com; airlied@linux.ie; daniel@ffwll.ch; 
> jfalempe@redhat.com; regressions@leemhuis.info; Kuo-Hsiang Chou 
> <kuohsiang_chou@aspeedtech.com>
> 
> Subject: [PATCH] drm/ast: Treat AST2600 like AST2500 in most places
> 
> Include AST2600 in most of the branches for AST2500. Thereby revert most 
> effects of commit f9bd00e0ea9d ("drm/ast: Create chip AST2600").
> 
> The AST2600 used to be treated like an AST2500, which at least gave 
> usable display output. After introducing AST2600 in the driver without 
> further updates, lots of functions take the wrong branches.
> 
> Handling AST2600 in the AST2500 branches reverts back to the original 
> settings. The exception are cases where AST2600 meanwhile got its own 
> branch.
> 
> [KH]: Based on CVE_2019_6260 item3, P2A is disallowed anymore.
> 
> P2A (PCIe to AMBA) is a bridge that is able to revise any BMC registers.
> 
> Yes, P2A is dangerous on security issue, because Host open a backdoor 
> and someone malicious SW/APP will be easy to take control of BMC.
> 
> Therefore, P2A is disabled forever.
> 
> Now, return to this patch, there is no need to add AST2600 condition on 
> the P2A flow.
> 

[snip]
> 
> [KH]: Yes, the patch is "drm/ast: Create threshold values for AST2600" 
> that is the root cause of whites lines on AST2600
> 
> commit
> 
> 
> bcc77411e8a65929655cef7b63a36000724cdc4b 
> <https://cgit.freedesktop.org/drm/drm/commit/?id=bcc77411e8a65929655cef7b63a36000724cdc4b> (patch 
> <https://cgit.freedesktop.org/drm/drm/patch/?id=bcc77411e8a65929655cef7b63a36000724cdc4b>)
> 


So basically this commit should be enough to fix the white lines  and 
flickering with VGA output on AST2600 ?
I will try to have it tested, and if it's good, we may want to have it 
on stable kernel.

Best regards,

-- 

Jocelyn


  parent reply	other threads:[~2022-06-08 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 12:02 [PATCH] drm/ast: Treat AST2600 like AST2500 in most places Thomas Zimmermann
2022-06-07 12:07 ` Thomas Zimmermann
2022-06-08  7:41   ` Jocelyn Falempe
     [not found] ` <PSAPR06MB4805B23B053F80C0F23A8C6C8CA49@PSAPR06MB4805.apcprd06.prod.outlook.com>
2022-06-08 13:16   ` Jocelyn Falempe [this message]
2022-06-09  2:32     ` Kuo-Hsiang Chou
2022-06-09  7:06       ` Jocelyn Falempe
2022-06-09  7:13         ` Thomas Zimmermann

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=c99f305f-ac4d-628b-b092-920af767a2e4@redhat.com \
    --to=jfalempe@redhat.com \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=charles_kuan@aspeedtech.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hungju_huang@aspeedtech.com \
    --cc=kuohsiang_chou@aspeedtech.com \
    --cc=luke_chen@aspeedtech.com \
    --cc=regressions@leemhuis.info \
    --cc=stable@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    /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