From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Nick Dyer <nick.dyer@itdev.co.uk>,
Stephen Warren <swarren@wwwdotorg.org>,
Benson Leung <bleung@chromium.org>,
Yufeng Shen <miletus@chromium.org>,
Daniel Kurtz <djkurtz@chromium.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>,
"Bowens, Alan" <Alan.Bowens@atmel.com>
Subject: Re: [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra
Date: Mon, 12 May 2014 18:17:47 -0700 [thread overview]
Message-ID: <20140513011747.GC26152@core.coreip.homeip.net> (raw)
In-Reply-To: <20140509184908.GX12304@sirena.org.uk>
On Fri, May 09, 2014 at 07:49:08PM +0100, Mark Brown wrote:
> On Thu, May 08, 2014 at 08:56:04PM +0100, Nick Dyer wrote:
>
> > Thanks! I had wondered why you had left it, you never communicated this to
> > me unfortunately. Would it be preferable for me to switch to
> > request_firmware_nowait() and complete the probe asynchronously after it
> > returns?
>
> Another common option is to defer the firmware request/load until the
> device is opened, but that doesn't work for all devices. That should
> mean that userspace is up and running.
That would not work for input devices as firmware quite often defines
capabilities of the devices and we need them before registering input
device (which is the object that userspace opens).
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-05-13 1:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 22:13 [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra Stephen Warren
2014-05-06 22:13 ` [PATCH 1/4] Input: atmel_mxt_ts - Set pointer emulation if is_tp Stephen Warren
2014-05-06 22:13 ` [PATCH 2/4] Input: atmel_mxt_ts - Read resolution from device memory Stephen Warren
2014-05-06 22:13 ` [PATCH 3/4] Input: atmel_mxt_ts: define a device tree binding Stephen Warren
2014-05-06 22:13 ` [PATCH 4/4] Input: atmel_mxt_ts: implement device tree parsing Stephen Warren
2014-05-06 22:16 ` [PATCH 0/4] Input: atmel_mxt_ts - make it work on Tegra Benson Leung
2014-05-06 22:35 ` Stephen Warren
2014-05-08 16:01 ` Nick Dyer
2014-05-08 16:41 ` Stephen Warren
2014-05-08 17:26 ` Dmitry Torokhov
2014-05-08 19:56 ` Nick Dyer
2014-05-09 18:49 ` Mark Brown
2014-05-13 1:17 ` Dmitry Torokhov [this message]
2014-05-08 19:50 ` Nick Dyer
2014-05-12 20:02 ` Stephen Warren
2014-05-13 1:16 ` Dmitry Torokhov
2014-05-13 2:31 ` Stephen Warren
2014-05-16 16:21 ` Nick Dyer
2014-05-16 16:40 ` Stephen Warren
2014-05-20 16:19 ` Nick Dyer
2014-06-11 18:17 ` Stephen Warren
2014-06-12 11:25 ` Nick Dyer
2014-06-12 17:12 ` Stephen Warren
2014-06-12 17:37 ` Stephen Warren
2014-06-30 16:11 ` Stephen Warren
2014-06-02 9:50 ` Sekhar Nori
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=20140513011747.GC26152@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Alan.Bowens@atmel.com \
--cc=bleung@chromium.org \
--cc=broonie@kernel.org \
--cc=djkurtz@chromium.org \
--cc=linux-input@vger.kernel.org \
--cc=miletus@chromium.org \
--cc=nick.dyer@itdev.co.uk \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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).