From: LW@KARO-electronics.de (Lothar Waßmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] dma: imx-sdma: clarify firmare not found warning
Date: Tue, 21 Jan 2014 07:59:22 +0100 [thread overview]
Message-ID: <20140121075922.2a83e076@ipc1.ka-ro> (raw)
In-Reply-To: <20140120151152.GE15937@n2100.arm.linux.org.uk>
Hi,
Russell King - ARM Linux wrote:
> On Mon, Jan 20, 2014 at 03:09:02PM +0100, Lothar Wa?mann wrote:
> > Hi,
> >
> > 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".
> > >
> > I can confirm that it does work, since I'm using it.
> > I have the following in my /etc/init.d/mdev.sh script:
> > | [ "$VERBOSE" = no ] || echo -n "Triggering firmware load"
> > | for dir in $(find /sys/class/firmware/ -type l);do
> > | echo add > "$dir/uevent"
> > | done
>
> I can't check on iMX6 at the moment, but I did look in that directory
> after the iMX6 SDMA reported that it hadn't found any firmware, and
> it was empty apart from the "timeout" file.
>
The file is automatically removed after the timeout has expired (or
the frimware has been loaded).
Thus you must check for it within the timeout period during boot.
Lothar Wa?mann
--
___________________________________________________________
Ka-Ro electronics GmbH | Pascalstra?e 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
Gesch?ftsf?hrer: Matthias Kaussen
Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
www.karo-electronics.de | info at karo-electronics.de
___________________________________________________________
next prev parent reply other threads:[~2014-01-21 6: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
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 [this message]
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=20140121075922.2a83e076@ipc1.ka-ro \
--to=lw@karo-electronics.de \
--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).