From: Manuel Estrada Sainz <email@example.com> To: Michael Hunold <firstname.lastname@example.org> Cc: LKML <email@example.com>, Greg KH <firstname.lastname@example.org> Subject: [PATCH] request_firmware() private workqueue (was: Re: Using firmware_class with recent 2.6 kernels) Date: Sat, 26 Jul 2003 12:18:18 +0200 [thread overview] Message-ID: <20030726101818.GA25104@ranty.pantax.net> (raw) In-Reply-To: <3F1BD157.email@example.com> On Mon, Jul 21, 2003 at 01:41:11PM +0200, Michael Hunold wrote: [snip] > To get a start, I took your sample driver and compiled it as a module. > I commented out all firmware load methods, except the async > notification I'm most interested in. > > When I load the module, it prints the debug message and goes to sleep -- > ok. But now the system is completely frozen (no keyboard or mouse > interaction possible) until the timeout is reached and the async > notification function is called, which of course says that the firmware > could not been loaded. Using a private workqueue fixes the issue, sleeping for many seconds from the common workqueue was not nice. Note that the problem only happens when appropriate firmware hotplug support is not available and request_firmware_work_func() has to wait until the timeout. About the attached patch: - use a private workqueue so we can sleep without interfering with other subsystems. Have a nice day Manuel -- --- Manuel Estrada Sainz <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> ------------------------ <email@example.com> ------------------- Let us have the serenity to accept the things we cannot change, courage to change the things we can, and wisdom to know the difference.
next parent reply other threads:[~2003-07-26 10:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <3F1BD157.firstname.lastname@example.org> 2003-07-26 10:18 ` Manuel Estrada Sainz [this message] 2003-07-26 15:59 ` Manuel Estrada Sainz 2003-07-29 15:02 ` [PATCH] request_firmware() private workqueue Michael Hunold 2003-08-01 19:15 ` [PATCH] " Manuel Estrada Sainz
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=20030726101818.GA25104@ranty.pantax.net \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='[PATCH] request_firmware() private workqueue (was: Re: Using firmware_class with recent 2.6 kernels)' \ /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
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).