From: Xinwei Kong <kong.kongxinwei@hisilicon.com>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Liguozhu (Kenneth)" <liguozhu@hisilicon.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/1] drm/sti: fix master bind bug for using component
Date: Thu, 16 Jul 2015 09:13:58 +0800 [thread overview]
Message-ID: <55A70556.2020005@hisilicon.com> (raw)
In-Reply-To: <CA+M3ks7WYE7UX2p=TnxXJ3rwKVk-O2-iPsiGBU5Pnf8Do=2zXQ@mail.gmail.com>
Thank you for Russel.
It is Right, when this sti_tvout (component) finish executing component ".bind"
function while sti_hdmi or sti_hda is not registered. the bug will occur .
this patch will prepare this bug by calling master .bind of sti_tvout after
sti_hdmi or sti_hda is register to finish binding sti_hdmi or sti_hda component,
however, it also slove to bring the "drm_dev" struct into the sti_hdmi or sti_hda.
Thank you
Xinwei
On 2015/7/15 21:17, Benjamin Gaignard wrote:
> Thanks a lot Russell, I have now understand where was my mistake.
>
>
> 2015-07-15 12:42 GMT+02:00 Russell King - ARM Linux <linux@arm.linux.org.uk>:
>> On Wed, Jul 15, 2015 at 12:19:01PM +0200, Benjamin Gaignard wrote:
>>> The build order in Makefile hasn't been change so the bug doesn't occur...
>>>
>>> In addition of taking care of not changing build order in Makefile,
>>> I would like to understand what is the expected behavior of component
>>> framework when
>>> master call component_bind_all() before any component_add() calls.
>>>
>>> Should component bind function be called in component_add() ?
>>> Is up to component to detect that master is already bounded ?
>>>
>>> Russell can you tell us what to do in this case ?
>>
>> I don't follow, and you certainly should never get into the situation
>> you're alluding to (where the master is already bound but a component
>> is not.)
>>
>> The way this should work is:
>>
>> - master and components register themselves into the component helper
>> in a random order.
>> - when the master registers, it gives the component helper a set of
>> matches which it uses to determine which components are required.
>> - when the component helper determines that all components and the
>> master have been registered, it calls the master bind function.
>> - the master bind function is responsible for the classical subsystem
>> initialisation, calling component_bind_all() to cause the individual
>> components bind() method to be called.
>>
>> So, you should never _ever_ be in the situation where initcall ordering
>> matters, or where the master is already bound but a component hasn't
>> registered.
>>
>> --
>> FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
>> according to speedtest.net.
>
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-07-16 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 9:28 [PATCH 1/1] drm/sti: fix master bind bug for using component Xinwei Kong
2015-07-15 10:19 ` Benjamin Gaignard
2015-07-15 10:42 ` Russell King - ARM Linux
2015-07-15 13:17 ` Benjamin Gaignard
2015-07-16 1:13 ` Xinwei Kong [this message]
2015-07-16 7:17 ` Benjamin Gaignard
2015-07-16 9:06 ` Xinwei Kong
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=55A70556.2020005@hisilicon.com \
--to=kong.kongxinwei@hisilicon.com \
--cc=benjamin.gaignard@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=liguozhu@hisilicon.com \
--cc=linux@arm.linux.org.uk \
/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