From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org,
Alex Deucher <alexander.deucher@amd.com>,
Borislav Petkov <bp@suse.de>,
Changcheng Deng <deng.changcheng@zte.com.cn>,
Hans de Goede <hdegoede@redhat.com>, Helge Deller <deller@gmx.de>,
Johan Hovold <johan@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Miaoqian Lin <linmq006@gmail.com>,
Peter Jones <pjones@redhat.com>, Sam Ravnborg <sam@ravnborg.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Yizhuo Zhai <yzhai003@ucr.edu>,
Zhen Lei <thunder.leizhen@huawei.com>,
linux-doc@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Fix some race conditions that exists between fbmem and sysfb
Date: Fri, 29 Apr 2022 10:06:52 +0200 [thread overview]
Message-ID: <97339148-9876-cfc1-8df8-dbb21a9c3c7c@redhat.com> (raw)
In-Reply-To: <YmuYE2t51lPIRT8p@phenom.ffwll.local>
Hello Daniel,
On 4/29/22 09:47, Daniel Vetter wrote:
[snip]
>>
>> Exactly, should be done when the device is registered rather than when
>> the driver is registered or a call is made to remove the conflicting FB.
>>
>> I'll rework this series with only the bits for sysfb_disable() and drop
>> the rest. We can go back to the discussion of the remaining parts later
>> if that makes sense (I still think that patch 3/5 is a better approach,
>> but let's defer that for a different series).
>
> We need to kill sysfb _before_ the driver loads, otherwise you can have
> two drivers fighting over each another. And yes that means you might end
> up with black screen if the driver load goes wrong, but the two drivers
> fighting over each another can also result in black screens. And the
> latter isn't fixable any other way (in general at least) than by making
> sure the fw stuff is gone before driver load starts in earnest.
Yes, you are correct. I didn't realize all the possible cases when agreed
with Thomas about doing this but tried and found that it's not enough.
I've a full patch-set now and will post as a RFC so we can discuss more.
> -Daniel
--
Best regards,
Javier Martinez Canillas
Linux Engineering
Red Hat
prev parent reply other threads:[~2022-04-29 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 8:52 Javier Martinez Canillas
2022-04-20 8:52 ` [PATCH v3 1/5] firmware: sysfb: Make sysfb_create_simplefb() return a pdev pointer Javier Martinez Canillas
2022-04-25 8:02 ` Thomas Zimmermann
2022-04-20 8:53 ` [PATCH v3 2/5] firmware: sysfb: Add helpers to unregister a pdev and disable registration Javier Martinez Canillas
2022-04-25 8:24 ` Thomas Zimmermann
2022-04-20 8:53 ` [PATCH v3 3/5] fbdev: Restart conflicting fb removal loop when unregistering devices Javier Martinez Canillas
2022-04-25 8:27 ` Thomas Zimmermann
2022-04-25 8:37 ` Javier Martinez Canillas
2022-04-20 8:53 ` [PATCH v3 4/5] fbdev: Fix some race conditions between fbmem and sysfb Javier Martinez Canillas
2022-04-25 8:30 ` Thomas Zimmermann
2022-04-22 15:17 ` [PATCH v3 0/5] Fix some race conditions that exists " Greg Kroah-Hartman
2022-04-25 8:54 ` Thomas Zimmermann
2022-04-25 9:15 ` Thomas Zimmermann
2022-04-25 9:49 ` Javier Martinez Canillas
2022-04-29 7:47 ` Daniel Vetter
2022-04-29 8:06 ` Javier Martinez Canillas [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=97339148-9876-cfc1-8df8-dbb21a9c3c7c@redhat.com \
--to=javierm@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=deller@gmx.de \
--cc=deng.changcheng@zte.com.cn \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=johan@kernel.org \
--cc=linmq006@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pjones@redhat.com \
--cc=sam@ravnborg.org \
--cc=thunder.leizhen@huawei.com \
--cc=tzimmermann@suse.de \
--cc=yzhai003@ucr.edu \
/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®