From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Simon Guinot <simon.guinot@sequanux.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Grant Likely <grant.likely@secretlab.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH v3] gpio: add GPIO support for F71882FG and F71889F
Date: Thu, 29 Aug 2013 16:37:38 +0100 [thread overview]
Message-ID: <20130829153738.GA16306@srcf.ucam.org> (raw)
In-Reply-To: <521F4F95.5080103@roeck-us.net>
On Thu, Aug 29, 2013 at 06:41:41AM -0700, Guenter Roeck wrote:
> On 08/29/2013 05:57 AM, Matthew Garrett wrote:
> >If a vendor doesn't provide any way to autoprobe a device, there's no
> >way to autoprobe a device. That usually means that you're not expected
> >to use that device.
> >
>
> Pretty radical. Following your advice, should we remove all watchdog
> and hwmon drivers for all SuperIO chips out there, plus any existing
> gpio drivers (drivers/char/pc8736x_gpio.c might be a candidate) ?
The majority of board vendors clearly don't expect the OS to drive the
hwmon chips - they're there for the benefit of ACPI and SMM code. That
doesn't mean that there's no benefit in having drivers for them, just
that the board vendors don't care about that use case and so won't do
anything to make it easier.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-08-29 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1374486633-9737-1-git-send-email-simon.guinot@sequanux.org>
[not found] ` <CACRpkda2bH_TkFR6c0cXvjye4SmFWN5xuzQSO=NqBq8mNDgV0g@mail.gmail.com>
[not found] ` <20130801134632.GY9916@kw.sim.vm.gnt>
[not found] ` <51FA8440.7050507@roeck-us.net>
2013-08-26 15:15 ` [PATCH v3] gpio: add GPIO support for F71882FG and F71889F Simon Guinot
2013-08-29 12:39 ` Linus Walleij
2013-08-29 12:57 ` Matthew Garrett
2013-08-29 13:41 ` Guenter Roeck
2013-08-29 15:37 ` Matthew Garrett [this message]
2013-08-29 16:08 ` Guenter Roeck
2013-08-29 16:25 ` Matthew Garrett
2013-08-29 17:31 ` Guenter Roeck
2013-08-29 22:20 ` Simon Guinot
2013-08-29 22:22 ` Matthew Garrett
2013-08-29 17:32 ` Linus Walleij
2013-08-29 17:35 ` Linus Walleij
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=20130829153738.GA16306@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=grant.likely@secretlab.ca \
--cc=hpa@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rjw@sisk.pl \
--cc=simon.guinot@sequanux.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).