From: Linus Walleij <linus.walleij@linaro.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: "William Breathitt Gray" <vilhelm.gray@gmail.com>,
"Andreas Bofjall" <andreas@gazonk.org>,
"Simon Guinot" <simon.guinot@sequanux.org>,
"Diego Elio Pettenò" <flameeyes@flameeyes.eu>,
"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: Wed, 28 Oct 2015 16:11:41 +0100 [thread overview]
Message-ID: <CACRpkdZBnmE2F7i2PYuxvO4cpYsGnrcGr0HMKg9WAPVMGnDBTw@mail.gmail.com> (raw)
In-Reply-To: <20151027165134.GK1548@lahna.fi.intel.com>
On Tue, Oct 27, 2015 at 5:51 PM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> On Tue, Oct 27, 2015 at 05:42:23PM +0100, Linus Walleij wrote:
>> On Tue, Oct 27, 2015 at 3:23 PM, Mika Westerberg
>> <mika.westerberg@linux.intel.com> wrote:
>> > On Tue, Oct 27, 2015 at 11:06:58AM +0100, Linus Walleij wrote:
>> >> > +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.)
>> >
>> > Not all of them actually require ISA. For example gpio-sch is part of an
>> > MFD device which is a PCI device. PCI bus also has notion of I/O ports.
>>
>> Hm, is there a more fitting symbol we should sort it under, which
>> means thingofabob-that-has-portmapped I/O?
>
> Well, there's already "Memory mapped GPIO drivers" so how about "I/O
> mapped GPIO drivers"?
Sure, "Port-mapped I/O GPIO drivers"
But what should I put as "depends" for that submenu, that is maybe
the real question.
Would (ISA || PCI) suffice?
Yours,
Linus Walleij
next prev parent reply other threads:[~2015-10-28 15:11 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
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 [this message]
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=CACRpkdZBnmE2F7i2PYuxvO4cpYsGnrcGr0HMKg9WAPVMGnDBTw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andreas@gazonk.org \
--cc=br1@einfach.org \
--cc=daniel.krueger@systec-electronic.com \
--cc=flameeyes@flameeyes.eu \
--cc=gnurou@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=simon.guinot@sequanux.org \
--cc=vilhelm.gray@gmail.com \
--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).