From: chenxb_99091 <chenxb_99091@126.com>
To: "Daniel Vetter" <daniel@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re:Re: [PATCH] drm: fix setting of plane_mask in pan_display_atomic() function for linux-4.4
Date: Tue, 26 May 2020 10:56:23 +0800 (CST) [thread overview]
Message-ID: <5182e8de.260f.1724ee8dcc6.Coremail.chenxb_99091@126.com> (raw)
In-Reply-To: <20200525143428.GG206103@phenom.ffwll.local>
[-- Attachment #1.1: Type: text/plain, Size: 2024 bytes --]
--
发自我的网易邮箱手机智能版
<br/><br/><br/>
----- Original Message -----
From: "Daniel Vetter" <daniel@ffwll.ch>
To: chenxb_99091@126.com
Cc: "David Airlie" <airlied@linux.ie>, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Sent: Mon, 25 May 2020 16:34:28 +0200
Subject: Re: [PATCH] drm: fix setting of plane_mask in pan_display_atomic() function for linux-4.4
>On Sat, May 23, 2020 at 11:49:07AM +0800, chenxb_99091@126.com wrote:
> >From: Xuebing Chen <chenxb_99091@126.com>
> >
>>The <include/drm/drm_crtc.h> provides drm_for_each_plane_mask macro and
>>plane_mask is defined as bitmask of plane indices, such as
>>1<<drm_plane_index(plane). This patch fixes error setting of plane_mask
> >in pan_display_atomic() function.
> >
> >Signed-off->>by: Xuebing Chen <chenxb_99091@126.com>
>What kernel is this patch against? Latest upstream doesn't have any such
>code anymore ... I'm assuming that Ville fixed this in one of his patches,
>but I can't find the right one just now.
>-Danie
This bug is still present in the long-supported versions of kernel 4.4.y, including the latest kernel 4.4.224,see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/?h=v4.4.224
> >---
> > drivers/gpu/drm/drm_fb_helper.c | 2 +-
> >1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
> >index e449f22..6a9f7ee 100644
>> --- a/drivers/gpu/drm/drm_fb_helper.c
> >+++ b/drivers/gpu/drm/drm_fb_helper.c
>> @@ -1256,7 +1256,7 @@ retry:
> > goto fail;
>>
> > plane = mode_set->crtc->primary;
>> - plane_mask |= drm_plane_index(plane);
> >+ plane_mask |= 1 << drm_plane_index(plane);
>> plane->old_fb = plane->fb;
> > }
> >
>> --
> >2.7.4
> >
>> _______________________________________________
>> dri-devel mailing list
> >dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
>Daniel Vetter
>Software Engineer, Intel Corporation
>http://blog.ffwll.ch
[-- Attachment #1.2: Type: text/html, Size: 3452 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-05-26 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 3:49 [PATCH] drm: fix setting of plane_mask in pan_display_atomic() function for linux-4.4 chenxb_99091
2020-05-25 14:34 ` Daniel Vetter
2020-05-25 14:56 ` Ville Syrjälä
2020-05-26 2:56 ` chenxb_99091 [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-27 13:33 chenxb_99091
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=5182e8de.260f.1724ee8dcc6.Coremail.chenxb_99091@126.com \
--to=chenxb_99091@126.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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