From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Simon Guinot <simon.guinot@sequanux.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: "Andreas Bofjall" <andreas@gazonk.org>,
"Diego Elio Pettenò" <flameeyes@flameeyes.eu>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Daniel Krueger" <daniel.krueger@systec-electronic.com>,
"Bruno Randolf" <br1@einfach.org>,
"Vivien Didelot" <vivien.didelot@savoirfairelinux.com>,
"Alexandre Courbot" <gnurou@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v10] gpio: Add GPIO support for the ACCES 104-IDIO-16
Date: Tue, 27 Oct 2015 08:37:37 -0400 [thread overview]
Message-ID: <562F7011.9040309@gmail.com> (raw)
In-Reply-To: <20151027111303.GD4665@kw.sim.vm.gnt>
On 10/27/2015 07:13 AM, Simon Guinot wrote:
> On Tue, Oct 27, 2015 at 11:06:58AM +0100, Linus Walleij wrote:
>> On Mon, Oct 19, 2015 at 6:59 PM, William Breathitt Gray
>> <vilhelm.gray@gmail.com> wrote:
>>
>>> The ACCES 104-IDIO-16 family of PC/104 utility boards feature 16
>>> optically isolated inputs and 16 optically isolated FET solid state
>>> outputs. This driver provides GPIO support for these 32 channels of
>>> digital I/O. Change-of-State detection interrupts are not supported.
>>>
>>> GPIO 0-15 correspond to digital outputs 0-15, while GPIO 16-31
>>> correspond to digital inputs 0-15. The base port address for the device
>>> may be set via the idio_16_base module parameter.
>>>
>>> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>
>>> ---
>>> Changes in v10:
>>> - Rename symbols to be more concise
>>> - Allocate GPIO device private data structure in probe function
>>
>> Yes, exactly like this. :)
>>
>> Patcha applied for kernel v4.4.
>>
>>> +menu "ISA GPIO drivers"
>>> +
>>> +config GPIO_104_IDIO_16
>>> + tristate "ACCES 104-IDIO-16 GPIO support"
>>> + depends on X86
>>> + help
>>> + Enables GPIO support for the ACCES 104-IDIO-16 family.
>>> +
>>> +endmenu
>>
>> I have five other drivers using port-based I/O:
>>
>> gpio-f7188x.c
>> gpio-it87.c
>> gpio-sch.c
>> gpio-sch311x.c
>> gpio-ts5500.c
>>
>> Do you think it makes sense to move all of these in under
>> the "ISA GPIO drivers" menu as well? I guess they all require
>> ISA after all.
>>
>> (Added their maintainers to the To: line so I can get some input
>> on this.)
>
> Hi Linus,
>
> The Super-I/Os are connected to a LPC bridge. And since LPC is much like
> ISA for software, then I guess it makes sense to move the drivers
> gpio-f7188x and gpio-it87 under a "ISA GPIO drivers" menu.
>
> Simon
>
Part of my purpose in suggesting the "ISA GPIO drivers" menu is my
intention to submit a couple more PC/104 drivers for merging into the Linux
baseline. Perhaps it may make sense to create subdirectories within the
"ISA GPIO Driver" to further organize drivers between "Super-I/O,"
"PC/104," and other ISA-based buses.
- William Breathitt Gray
next prev parent reply other threads:[~2015-10-27 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 16:59 [PATCH v10] gpio: Add GPIO support for the ACCES 104-IDIO-16 William Breathitt Gray
2015-10-27 10:06 ` Linus Walleij
2015-10-27 11:13 ` Simon Guinot
2015-10-27 12:37 ` William Breathitt Gray [this message]
2015-10-27 14:23 ` Mika Westerberg
2015-10-27 14:40 ` Simon Guinot
2015-10-27 14:43 ` Mika Westerberg
2015-10-27 16:42 ` Linus Walleij
2015-10-27 16:51 ` Mika Westerberg
2015-10-28 15:11 ` Linus Walleij
2015-10-29 8:22 ` Mika Westerberg
2015-10-30 9:22 ` 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=562F7011.9040309@gmail.com \
--to=vilhelm.gray@gmail.com \
--cc=andreas@gazonk.org \
--cc=br1@einfach.org \
--cc=daniel.krueger@systec-electronic.com \
--cc=flameeyes@flameeyes.eu \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=simon.guinot@sequanux.org \
--cc=vivien.didelot@savoirfairelinux.com \
/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).