From: Linus Walleij <linus.walleij@linaro.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sascha Silbe <x-linux@infra-silbe.de>,
Johan Hovold <jhovold@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB: ftdi_sio: add GPIO support
Date: Thu, 16 Jul 2015 13:56:00 +0200 [thread overview]
Message-ID: <CACRpkdatvRVQFP12wuohOF8Z_bcsdhq622f+Kej8wM2B05-Wcw@mail.gmail.com> (raw)
In-Reply-To: <CACxGe6v6+v+NA8UmOb0P7ohAUHmQgXtFHJFBammk5SDrrf8jsA@mail.gmail.com>
On Sat, Jul 4, 2015 at 12:13 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Tue, Jun 2, 2015 at 2:18 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
>> On Sat, May 30, 2015 at 10:29 PM, Grant Likely
>> <grant.likely@secretlab.ca> wrote:
>>> On Mon, Jul 7, 2014 at 6:31 PM, Greg Kroah-Hartman
>>> <gregkh@linuxfoundation.org> wrote:
>>
>>>>> However is the MFD cell approach acceptable?
>>>>
>>>> Yes it is.
>>>
>>> Going back to this old conversation... Actually, I disagree. There is
>>> absolutely no need to go the MFD approach for this driver. That just
>>> adds layers of abstraction for no purpose. GPIOLIB is an interface,
>>> and it is completely fine for a driver to hook up to the GPIOLIB
>>> interface at the same time as exposing a serial port. MFD doesn't buy
>>> the driver anything useful here.
>>
>> What is buys is centralizing code into the proper drivers/gpio
>> folder of the kernel. So more of a maintenance point than a
>> mechanics/performance point.
>>
>> We do have GPIO drivers scattered all over the kernel so one
>> more or less wouldn't matter so much...
>
> Yeah, I would say that's a non-reason. When it comes to a single
> device, it is far better in my opinion to have the entire driver
> located together rather than splitting it up into parts so that each
> part lives with it's subsystem. We've got tools for find users of
> interfaces, whereas spliting a driver up can make maintenance a lot
> more complicated.
Yeah I already gave up on this in some other thread :D
Yours,
Linus Walleij
prev parent reply other threads:[~2015-07-16 11:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 13:21 [PATCH] USB: ftdi_sio: add GPIO support Sascha Silbe
2014-06-09 14:23 ` One Thousand Gnomes
2014-06-09 18:36 ` Sergei Shtylyov
2014-06-10 10:56 ` Johan Hovold
2014-06-16 7:15 ` Philipp Hachtmann
2014-06-13 7:25 ` Linus Walleij
2014-06-13 18:31 ` Greg Kroah-Hartman
2014-07-07 10:44 ` Linus Walleij
2014-07-07 17:31 ` Greg Kroah-Hartman
[not found] ` <20140707173142.GB8693-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-05-30 20:29 ` Grant Likely
[not found] ` <CACxGe6uskWcBU0MhO=EupU=2VKmDhX01-_LDJ-n91XAnRYiqbw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-06-02 13:18 ` Linus Walleij
[not found] ` <CACRpkdbDAWq42pkwTfi98invy0ov=XD8WzfX0dwnjeRXVpQ8Ow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-03 22:13 ` Grant Likely
2015-07-16 11:56 ` Linus Walleij [this message]
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=CACRpkdatvRVQFP12wuohOF8Z_bcsdhq622f+Kej8wM2B05-Wcw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=gnurou@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=jhovold@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=x-linux@infra-silbe.de \
/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).