linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marouen Ghodhbane <marouen.ghodhbane@nxp.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	Daniel Wagner <wagi@monom.org>
Subject: Re: [EXT] Re: complete_all warning with 3 waiters
Date: Tue, 17 Mar 2020 23:51:06 +0000	[thread overview]
Message-ID: <DB3PR0402MB3708CE604A639117EDA4588DF6F60@DB3PR0402MB3708.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200317120817.zm3a2zr4bsvpcbsn@linutronix.de>

Thanks Sebastian and Daniel for your answers.

>> In fact, there is 3 sdma controller devices on the target pointing to

>> the same firmware file and the imx-sdma driver is requesting the

>> firmware asynchronously with request_firmware_nowait(). The

>> request_firmware API in linux is making all waiters, requesting the

>> same firmware file, wait on the same completion which triggers this

>> warning.


> This looks like something that happens at boot / hardware setup time and

> not while the system is running "production". Thanks for the feedback.

Indeed, this happens only on system boot (more precisely on the imx-sdma 
driver probe). So, no RT workload is impacted here.


> Feel free to raise the bar here to avoid the warning in your case here.

> I'm currently thinking about removing the warning due to lack of new

> cases.

That's exactly what I implemented for the moment.

Thanks,
Marouen. 

      reply	other threads:[~2020-03-17 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11 16:32 complete_all warning with 3 waiters Marouen Ghodhbane
2020-03-12  8:10 ` Daniel Wagner
2020-03-17 12:08 ` Sebastian Andrzej Siewior
2020-03-17 23:51   ` Marouen Ghodhbane [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=DB3PR0402MB3708CE604A639117EDA4588DF6F60@DB3PR0402MB3708.eurprd04.prod.outlook.com \
    --to=marouen.ghodhbane@nxp.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=wagi@monom.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;
as well as URLs for NNTP newsgroup(s).