From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Simon Guinot <simon.guinot@sequanux.org>,
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>
Subject: Re: [PATCH v3] gpio: add GPIO support for F71882FG and F71889F
Date: Mon, 29 Jul 2013 22:26:09 +0200 [thread overview]
Message-ID: <10218498.b5WOCmgjXj@vostro.rjw.lan> (raw)
In-Reply-To: <CACRpkda2bH_TkFR6c0cXvjye4SmFWN5xuzQSO=NqBq8mNDgV0g@mail.gmail.com>
On Monday, July 29, 2013 05:59:08 PM Linus Walleij wrote:
> On Mon, Jul 22, 2013 at 11:50 AM, Simon Guinot
> <simon.guinot@sequanux.org> wrote:
>
> > This patch adds support for the GPIOs found on the Fintek super-I/O
> > chips F71882FG and F71889F.
> >
> > A super-I/O is a legacy I/O controller embedded on x86 motherboards. It
> > is used to connect the low-bandwidth devices. Among others functions the
> > F71882FG/F71889F provides: a parallel port, two serial ports, a keyboard
> > controller, an hardware monitoring controller and some GPIO pins.
> >
> > Note that this super-I/Os are embedded on some Atom-based LaCie NASes.
> > The GPIOs are used to control the LEDs and the hard drive power.
> >
> > Signed-off-by: Simon Guinot <simon.guinot@sequanux.org>
> > ---
> > Changes since v2:
> > - Remove useless NULL setters for driver data.
>
> Given the recent discussion with Rafael I want to have an
> extended discussion of this patch.
>
> It is my current understanding that:
>
> - It is possible to define the whereabouts of the SuperIO
> chips using ACPI
> - It is possible for developers to influence the source
> AML for the DSDT tables of these systems.
> - It is the proper thing to do.
> - So we should atleast support ACPI probing with the
> port-based detection as a final fallback if all else fails.
>
> Why can I not get something like:
>
> #include <linux/acpi.h>
> (...)
> static const struct acpi_device_id gpio_acpi_match[] = {
> { "FOOBAR", 0 },
> { }
> };
> MODULE_DEVICE_TABLE(acpi, gpio_acpi_match);
>
> static struct platform_driver gpio_driver = {
> (...)
> .driver = {
> (...)
> .acpi_match_table = ACPI_PTR(gpio_acpi_match),
> },
> };
>
> ?
>
> If there is something wrong in my reasoning above, please
> share it!
In addition to that, the "FOOBAR" PNP ID needs to be added to the
acpi_platform_device_ids[] table in drivers/acpi/acpi_platform.c.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-07-29 20:16 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 [this message]
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
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=10218498.b5WOCmgjXj@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®