From: "Henrik Rydberg" <rydberg@euromail.se>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: Alessandro Rubini <rubini@cvml.unipv.it>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Olof Johansson <olof@lixom.net>,
Benson Leung <bleung@chromium.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Input: synaptics - print firmware ID and board number at init
Date: Mon, 2 Jul 2012 14:37:15 +0200 [thread overview]
Message-ID: <20120702123715.GA1898@polaris.bitmath.org> (raw)
In-Reply-To: <CAGS+omCy9g8Q6gJhcgMatr+jWPkAzHge6sZOR8HOM92+-xBhXA@mail.gmail.com>
> > Is there a specific usecase for this, except the nice-to-have?
>
> Use cases (these are all very real use cases, that we use today, they
> are not hypothetical):
> * To include firmware and hardware versions in user feedback reports.
> * Used by factory tests to ensure systems are being built and
> deployed correctly.
> * Lastly, these are also precursor patches for a larger set that
> adds firmware update capability. A userspace firmware update script
> can use these APIs to determine which file to load and/or whether such
> a load is necessary.
Thanks. Future firmware update patches is the prime reason for the
sysfs interface, IOW.
> If there is a standard non-driver-specific way of achieving these use
> cases, I'd be happy to modify the implementation to adopt that
> standard. From what I've seen, however, it looks like most drivers
> have their own ad hoc way of exposing device/vendor specific
> properties.
Precisely. If there is no standard, it is quite alright to try to come
up with one. Otherwise we might as well leave all firmware-related
code in userspace.
Thanks,
Henrik
prev parent reply other threads:[~2012-07-02 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 4:51 Daniel Kurtz
2012-06-28 4:51 ` [PATCH 2/2] Input: synaptics - add sysfs access to firmware ID & board ID Daniel Kurtz
2012-07-02 7:36 ` Henrik Rydberg
2012-07-02 7:27 ` [PATCH 1/2] Input: synaptics - print firmware ID and board number at init Henrik Rydberg
2012-07-02 11:17 ` Daniel Kurtz
2012-07-02 12:37 ` Henrik Rydberg [this message]
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=20120702123715.GA1898@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=bleung@chromium.org \
--cc=djkurtz@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rubini@cvml.unipv.it \
/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®