From: Takashi Iwai <tiwai@suse.de>
To: Ming Lei <ming.lei@canonical.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Prarit Bhargava <prarit@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
x86@kernel.org, amd64-microcode@amd64.org
Subject: Re: [PATCH 1/2] firmware: Introduce request_firmware_direct()
Date: Mon, 11 Nov 2013 16:10:06 +0100 [thread overview]
Message-ID: <s5hvbzzq8j5.wl%tiwai@suse.de> (raw)
In-Reply-To: <CACVXFVMAoKrVVG6fAfmSCGE7QuntF=uwA21bGNrEQEZnfheD2g@mail.gmail.com>
At Mon, 11 Nov 2013 15:44:38 +0800,
Ming Lei wrote:
>
> Hi Takashi,
>
> On Tue, Nov 5, 2013 at 7:57 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > When CONFIG_FW_LOADER_USER_HELPER is set, request_firmware() falls
> > back to the usermode helper for loading via udev when the direct
> > loading fails. But the recent udev takes way too long timeout (60
> > seconds) for non-existing firmware. This is unacceptable for the
> > drivers like microcode loader where they load firmwares optionally,
> > i.e. it's no error even if no requested file exists.
> >
> > This patch provides a new helper function, request_firmware_direct().
> > It behaves as same as request_firmware() except for that it doesn't
> > fall back to usermode helper but returns an error immediately if the
> > f/w can't be loaded directly in kernel.
> >
> > Without CONFIG_FW_LOADER_USER_HELPER=y, request_firmware_direct() is
> > just an alias of request_firmware(), due to obvious reason.
> >
> > Tested-by: Prarit Bhargava <prarit@redhat.com>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
>
> The patch is fine, except it should be against -next, so you can feel
> free to add my Acked-by in your next submission.
OK, I'm going to resubmit the patch series based on next.
BTW, looking at linux-next code, I found another issue in the relevant
place; the fallback warning is shown no matter whether
CONFIG_FIRMWAMRE_USERMODE_HELPER is set or not. I'll put the fix into
the next series, too.
thanks,
Takashi
next prev parent reply other threads:[~2013-11-11 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 11:57 [PATCH 0/2] Add request_firmware_direct() for microcode loader Takashi Iwai
2013-11-05 11:57 ` [PATCH 1/2] firmware: Introduce request_firmware_direct() Takashi Iwai
2013-11-11 7:44 ` Ming Lei
2013-11-11 15:10 ` Takashi Iwai [this message]
2013-11-05 11:57 ` [PATCH 2/2] microcode: Use request_firmware_direct() Takashi Iwai
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=s5hvbzzq8j5.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=amd64-microcode@amd64.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=prarit@redhat.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®