From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] dma: imx-sdma: clarify firmare not found warning
Date: Mon, 20 Jan 2014 17:29:20 +0530 [thread overview]
Message-ID: <20140120115919.GD26823@intel.com> (raw)
In-Reply-To: <20140120123849.GC15937@n2100.arm.linux.org.uk>
On Mon, Jan 20, 2014 at 12:38:50PM +0000, Russell King - ARM Linux wrote:
> On Mon, Jan 20, 2014 at 12:36:27PM +0100, Lothar Wa?mann wrote:
> > In case user space firmware loading support (CONFIG_FW_LOADER) is
> > enabled, this message may still be inadequate, since the firmware may
> > very well be loaded lateron.
>
> I haven't worked out whether that's actually possible - I saw no way to
> re-trigger the firmware request, and once the firmware request expires,
> there seems to be no way for userspace to say "okay, the firmware is now
> available, please load it".
In that case why don't we use async version and wait till the userspace is
availble and firmware is loaded.
So request_firmware_nowait() seems to do the job, I have used in a device where
I call it in probe() so that not to slow booting and make firmware bloc availble
userpsace is availble.
Sounds too good, did I miss anything obvious for this case here?
--
~Vinod
next prev parent reply other threads:[~2014-01-20 11:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 10:07 [PATCH v2] dma: imx-sdma: clarify firmare not found warning Sascha Hauer
2014-01-20 11:28 ` Lothar Waßmann
2014-01-20 11:36 ` Lothar Waßmann
2014-01-20 12:38 ` Russell King - ARM Linux
2014-01-20 11:59 ` Vinod Koul [this message]
2014-01-20 13:09 ` Sascha Hauer
2014-01-20 14:09 ` Lothar Waßmann
2014-01-20 15:11 ` Russell King - ARM Linux
2014-01-21 6:59 ` Lothar Waßmann
2014-01-21 11:01 ` Russell King - ARM Linux
2014-01-21 11:52 ` Lothar Waßmann
2014-01-21 11:57 ` Russell King - ARM Linux
2014-01-21 13:36 ` Lothar Waßmann
2014-01-21 14:10 ` Russell King - ARM Linux
2014-01-21 7:06 ` Sascha Hauer
2014-01-21 8:31 ` Lothar Waßmann
2014-10-25 12:28 ` Fabio Estevam
2014-11-12 11:13 ` Vinod Koul
2014-11-12 22:05 ` Fabio Estevam
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=20140120115919.GD26823@intel.com \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.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).