From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: 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: Mon, 7 Jul 2014 10:31:42 -0700 [thread overview]
Message-ID: <20140707173142.GB8693@kroah.com> (raw)
In-Reply-To: <CACRpkdYRm1gE5ai05TK17T3bVHKSVEkXeL5Qci8G=Lpt+UYsug@mail.gmail.com>
On Mon, Jul 07, 2014 at 12:44:28PM +0200, Linus Walleij wrote:
> On Fri, Jun 13, 2014 at 8:31 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Fri, Jun 13, 2014 at 09:25:07AM +0200, Linus Walleij wrote:
>
> >> But I also want to bring the device model into question: normally
> >> when a mother device spawns children across different subsystems
> >> we model them as MFD devices (drivers/mfd) that instantiate
> >> children for the different subsystems. So you could spawn a
> >> serial and a GPIO device from a USB-based hub device there.
> >>
> >> I do not know if that is really apropriate in this case. It seems the
> >> device is first and foremost FTDI.
> >>
> >> But it could still spawn a child platform device for the GPIO stuff
> >> so that this can live as a separate driver under drivers/gpio/gpio-ftdi.c
> >> or similar.
> >>
> >> You could then use something like:
> >>
> >> struct platform_device *gdev;
> >
> > Ick, no, it's a USB device, do not abuse the platform_device code any
> > more than it currently is (note, I HATE the platform device code,
> > someday I'll delete it entirely... Well, I can dream...)
>
> Haha yeah :-)
>
> However is the MFD cell approach acceptable?
Yes it is.
next prev parent reply other threads:[~2014-07-07 17:27 UTC|newest]
Thread overview: 17+ 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 13:21 ` 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 [this message]
[not found] ` <20140707173142.GB8693-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-05-30 20:29 ` Grant Likely
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
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-03 22:13 ` Grant Likely
2015-07-16 11:56 ` 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=20140707173142.GB8693@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=gnurou@gmail.com \
--cc=jhovold@gmail.com \
--cc=linus.walleij@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.