From: liuxinliang <z.liuxinliang@hisilicon.com>
To: John Stultz <john.stultz@linaro.org>,
lkml <linux-kernel@vger.kernel.org>
Cc: Rongrong Zou <zourongrong@gmail.com>,
Xinwei Kong <kong.kongxinwei@hisilicon.com>,
Chen Feng <puck.chen@hisilicon.com>,
"David Airlie" <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Sean Paul <seanpaul@chromium.org>,
<dri-devel@lists.freedesktop.org>
Subject: Re: [RFC][PATCH v2] drm: kirin: Add a mutex to avoid fb initialization race
Date: Sat, 25 Feb 2017 09:45:45 +0800 [thread overview]
Message-ID: <58B0E1C9.7020807@hisilicon.com> (raw)
In-Reply-To: <58B0E044.6010905@hisilicon.com>
On 2017/2/25 9:39, liuxinliang wrote:
> Hi John,
>
> The patch seems good to me, except one minus comment.
> Maybe change fb_lock to fbdev_lock would be better.
>
> Thanks,
> -xinliang
>
> On 2017/2/25 9:25, John Stultz wrote:
>> In some cases I've been seeing a race where two framebuffers
>> would be initialized, as kirin_fbdev_output_poll_changed()
>> might get called quickly in succession, resulting in the
>> initialization happening twice. This could cause the system
>> to boot up with a blank screen.
>>
>> This patch adds a simple mutex to serialize it and seems to
>> avoid the race.
>>
>> Suggestions or feedback would be greatly appreciated!
>>
>> Cc: Xinliang Liu <z.liuxinliang@hisilicon.com>
>> Cc: Rongrong Zou <zourongrong@gmail.com>
>> Cc: Xinwei Kong <kong.kongxinwei@hisilicon.com>
>> Cc: Chen Feng <puck.chen@hisilicon.com>
>> Cc: David Airlie <airlied@linux.ie>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Cc: Sean Paul <seanpaul@chromium.org>
>> Cc: dri-devel@lists.freedesktop.org
>> Signed-off-by: John Stultz <john.stultz@linaro.org>
>> ---
>> drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.c | 4 ++++
>> drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.h | 1 +
>> 2 files changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.c
>> b/drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.c
>> index 7ec93ae..b83556a 100644
>> --- a/drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.c
>> +++ b/drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.c
>> @@ -55,6 +55,7 @@ static void kirin_fbdev_output_poll_changed(struct
>> drm_device *dev)
>> {
>> struct kirin_drm_private *priv = dev->dev_private;
>> + mutex_lock(&priv->fb_lock);
>> if (priv->fbdev) {
>> drm_fbdev_cma_hotplug_event(priv->fbdev);
>> } else {
>> @@ -63,6 +64,7 @@ static void kirin_fbdev_output_poll_changed(struct
>> drm_device *dev)
>> if (IS_ERR(priv->fbdev))
>> priv->fbdev = NULL;
>> }
>> + mutex_unlock(&priv->fb_lock);
>> }
>> #endif
>> @@ -95,6 +97,8 @@ static int kirin_drm_kms_init(struct drm_device
>> *dev)
>> if (!priv)
>> return -ENOMEM;
>> + mutex_init(&priv->fb_lock);
And put this line in CONFIG_DRM_FBDEV_EMULATION
>> +
>> dev->dev_private = priv;
>> dev_set_drvdata(dev->dev, dev);
>> diff --git a/drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.h
>> b/drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.h
>> index 7f60c649..9b6d2b1 100644
>> --- a/drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.h
>> +++ b/drivers/gpu/drm/hisilicon/kirin/kirin_drm_drv.h
>> @@ -23,6 +23,7 @@ struct kirin_drm_private {
>> #ifdef CONFIG_DRM_FBDEV_EMULATION
>> struct drm_fbdev_cma *fbdev;
>> #endif
>> + struct mutex fb_lock;
And here.
-xinliang
>> };
>> extern const struct kirin_dc_ops ade_dc_ops;
>
next prev parent reply other threads:[~2017-02-25 1:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 1:25 John Stultz
2017-02-25 1:39 ` liuxinliang
2017-02-25 1:43 ` John Stultz
2017-02-25 1:45 ` liuxinliang [this message]
2017-02-25 1:52 ` John Stultz
2017-02-25 19:36 ` Daniel Vetter
2017-02-27 23:33 ` John Stultz
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=58B0E1C9.7020807@hisilicon.com \
--to=z.liuxinliang@hisilicon.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=john.stultz@linaro.org \
--cc=kong.kongxinwei@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=puck.chen@hisilicon.com \
--cc=seanpaul@chromium.org \
--cc=zourongrong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®