From: Zhenhua Huang <quic_zhenhuah@quicinc.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <rafael@kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_pkondeti@quicinc.com>, <quic_tingweiz@quicinc.com>,
<saravanak@google.com>
Subject: Re: [RESEND PATCH] driver core: Clear FWNODE_FLAG_LINKS_ADDED in device_links_purge()
Date: Wed, 27 Sep 2023 14:34:43 +0800 [thread overview]
Message-ID: <9f04d29e-bd83-e8c1-7e55-b5a0441abc9b@quicinc.com> (raw)
In-Reply-To: <2023092722-proofread-vindicate-f26c@gregkh>
On 2023/9/27 13:57, Greg KH wrote:
> On Wed, Sep 27, 2023 at 10:30:10AM +0800, Zhenhua Huang wrote:
>> Flag FWNODE_FLAG_LINKS_ADDED stops fwnode links creation. Current kernel
>> only adds it once after fwnode links creation in fw_devlink_parse_fwnode().
>> After that even device links being purged, the flag will not be cleared.
>>
>> Fwnode links are converted to device links and will not be added back
>> forever in normal case. Essentially if a device is registered and
>> unregisted (also deleted) before it is probed (due to missing fwlink
>> dependencies, abort in device_links_check_suppliers), the fwlink is not
>> setup next when device is newly created again. This means the probe gets
>> called without meeting all dependencies.
>>
>> It usuallly happens in the case of a glue driver. Of_platform_populate()
>> allows us to populate subnodes. We may do it in ancestor node probing
>> function, then check subnode's probing status because there may be chances
>> that suppliers of subnode are not ready. We may further need to do
>> of_platform_depopulate(which purges device links) and in some time
>> of_platform_populate() again. Such case we miss fwnode links(so that device
>> links) during second time of populating subnodes.
>>
>> Fix it by Clearing FWNODE_FLAG_LINKS_ADDED flag in purging device link
>> func, indicates both fwnode links and device links are absent.
>>
>> Signed-off-by: Zhenhua Huang <quic_zhenhuah@quicinc.com>
>> ---
>> drivers/base/core.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/base/core.c b/drivers/base/core.c
>> index b7d7f41..2a1975d 100644
>> --- a/drivers/base/core.c
>> +++ b/drivers/base/core.c
>> @@ -1630,6 +1630,10 @@ static void device_links_purge(struct device *dev)
>> __device_link_del(&link->kref);
>> }
>>
>> + /* Clear flags in fwnode. Give a chance to create fwnode link again */
>> + if (dev->fwnode)
>> + dev->fwnode->flags &= ~FWNODE_FLAG_LINKS_ADDED;
>> +
>> device_links_write_unlock();
>> }
>>
>> --
>> 2.7.4
>>
>
> Why is this a RESEND? What was wrong with the first version?
As per request of codes author, I CCed saravanak this time :)
Nothing else changed.
Thanks,
Zhenhua
next prev parent reply other threads:[~2023-09-27 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 2:30 Zhenhua Huang
2023-09-27 5:57 ` Greg KH
2023-09-27 6:32 ` Zhenhua Huang
2023-09-27 8:08 ` Greg KH
2023-09-27 5:57 ` Greg KH
2023-09-27 6:34 ` Zhenhua Huang [this message]
2023-09-27 8:08 ` Greg KH
2023-09-27 9:53 ` Zhenhua Huang
2023-10-02 21:40 ` Saravana Kannan
2023-10-03 3:34 ` Pavan Kondeti
2023-10-05 9:32 ` Greg KH
2023-10-05 10:49 ` Pavan Kondeti
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=9f04d29e-bd83-e8c1-7e55-b5a0441abc9b@quicinc.com \
--to=quic_zhenhuah@quicinc.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_pkondeti@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=rafael@kernel.org \
--cc=saravanak@google.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®