From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: Location for a kind of GPIO bus driver
Date: Thu, 25 Jul 2013 15:16:15 -0700 [thread overview]
Message-ID: <20130725221615.GA30881@kroah.com> (raw)
In-Reply-To: <CACRpkdZWQQUCeHvgPPLmxL3O1sw55pc_KbzbnqTSFJx+0_QanQ@mail.gmail.com>
On Thu, Jul 25, 2013 at 11:46:42PM +0200, Linus Walleij wrote:
> On Tue, Jul 23, 2013 at 5:18 PM, Simon Guinot <simon.guinot@sequanux.org> wrote:
>
> > (...) I am
> > thinking about moving the GPIO extension bus support into a separate
> > driver. The problem is that I can't find a proper location for a such
> > driver. AFAIK, it doesn't fit with anything existing supported by Linux.
> > Maybe I should consider drivers/bus ? Or even drivers/misc ?
>
> This is a question to Greg, the device core maintainer.
> AFAICT they go into drivers/base/foo-bus.c
No, specific bus code does not go in drivers/base/ it goes where the
rest of the subsystem lives.
> In this case I would first consider using MFD though,
> please make a case for why this is not simply a multi
> function device with a few cells (== platform devices).
I agree with this as well.
thanks,
greg k-h
next prev parent reply other threads:[~2013-07-25 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 15:18 Location for a kind of GPIO bus driver Simon Guinot
2013-07-24 18:19 ` Jason Cooper
2013-07-25 15:49 ` Simon Guinot
2013-07-25 16:03 ` Jason Cooper
2013-07-26 8:56 ` Simon Guinot
2013-07-26 11:27 ` Jason Cooper
2013-07-26 16:18 ` Arnd Bergmann
2013-07-25 21:46 ` Linus Walleij
2013-07-25 22:16 ` Greg KH [this message]
2013-07-26 12:01 ` Jason Cooper
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=20130725221615.GA30881@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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