From: Simon Guinot <simon.guinot@sequanux.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Linus Walleij <linus.walleij@linaro.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: Fri, 30 Aug 2013 00:20:54 +0200 [thread overview]
Message-ID: <20130829222053.GE13942@kw.sim.vm.gnt> (raw)
In-Reply-To: <20130829162551.GA17411@srcf.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]
On Thu, Aug 29, 2013 at 05:25:51PM +0100, Matthew Garrett wrote:
> On Thu, Aug 29, 2013 at 09:08:30AM -0700, Guenter Roeck wrote:
> > On Thu, Aug 29, 2013 at 04:37:38PM +0100, Matthew Garrett wrote:
> > > On Thu, Aug 29, 2013 at 06:41:41AM -0700, Guenter Roeck wrote:
> > > 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.
> > >
> > Actually, not entirely true. Some vendors even provide software running on
> > Windows to access those chips (including access to fans controlled through
> > GPIO pins) and to provide information to the user. It might be more accurate
> > to say that some board vendors don't care about Linux (or about providing
> > access through ACPI, for that matter).
>
> Eh. If they're really providing code that just assumes that hardware is
> present and bangs on it, what choice do we have? You've checked that the
> machines in question don't have a magic ACPI device that provides
> resource information?
>
> > Question here is what the Linux kernel community's policy is going to be
> > to handle such cases. Pragmatic or dogmatic ?
>
> I don't see any benefit in changing the status quo. Sometimes hardware
> is just shit. The majority of x86 vendors certainly don't care about
> anything we do, so it's not like we're in a position to force them to
> change.
Almost all the LaCie NASes are running a Linux based OS. I can assure
you that LaCie really takes care of Linux. Now, the main reason why the
Super-I/O ACPI support is missing on this boards is a lack of knowledge.
Thanks to this discussion, I am now aware of that. Then, for the next
products, I will do my best to get AMLs or at least ACPI IDs.
Thanks,
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-08-29 22:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 9:50 Simon Guinot
2013-07-29 15:59 ` Linus Walleij
2013-07-29 20:26 ` Rafael J. Wysocki
2013-08-01 13:46 ` Simon Guinot
2013-08-01 15:52 ` Guenter Roeck
2013-08-26 15:15 ` 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
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 [this message]
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=20130829222053.GE13942@kw.sim.vm.gnt \
--to=simon.guinot@sequanux.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=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
/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®