From: Linus Torvalds <torvalds@linux-foundation.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: David Brown <davidb@codeaurora.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] char/misc patches for 3.10-rc1
Date: Mon, 29 Apr 2013 11:55:34 -0700 [thread overview]
Message-ID: <CA+55aFwU-bXZ7wn2dOcLNfPMcjDv3Jvqx_LTt7B+-tj4WcP8Mg@mail.gmail.com> (raw)
In-Reply-To: <20130429183851.GA8106@kroah.com>
On Mon, Apr 29, 2013 at 11:38 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> It's a "bus" type, that has individual drivers connecting to it.
No it isn't, and no it doesn't.
It's a "bus" exactly the same way the PS2 driver is a "bus", and it
has individual devices connecting to it exactly the same way we have
keyboards and mice connecting to the PS2 driver.
Except at least the PS2 driver is documented somewhere, and has been
done by multiple different vendors. Afaik, ssbi is a single
implementation by qualcomm or something.
Yes, we could have "drivers/ps2" too. Except we don't. It's actually
hidden down in drivers/input/serio/.
Now, maybe I'm wrong, and maybe SSBI is some next-gen super-bus that
just hides all the information about itself from me better than most
hardware tends to. And hey, maybe it will eventually grow to replace
something like i2c entirely. Maybe David can explain why it's such a
big deal. But right now it smells like somethign that should not be at
the top level.
Linus
next prev parent reply other threads:[~2013-04-29 18:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 16:21 [GIT PATCH] char/misc patches for 3.10-rc1 Greg KH
2013-04-29 18:28 ` Linus Torvalds
2013-04-29 18:38 ` Greg KH
2013-04-29 18:55 ` Linus Torvalds [this message]
2013-04-29 19:02 ` Linus Torvalds
2013-04-29 19:15 ` Linus Torvalds
2013-04-29 19:54 ` Arnd Bergmann
2013-04-29 20:12 ` Linus Torvalds
2013-04-29 20:50 ` Arnd Bergmann
2013-04-29 21:13 ` Linus Torvalds
2013-04-29 21:22 ` Arnd Bergmann
2013-05-01 16:12 ` Mark Brown
2013-04-29 21:08 ` David Brown
2013-04-29 21:16 ` Arnd Bergmann
2013-05-01 16:13 ` Mark Brown
2013-05-02 20:53 ` David Brown
2013-05-03 8:06 ` Mark Brown
2013-04-29 21:18 ` Linus Torvalds
2013-04-29 21:29 ` Arnd Bergmann
2013-04-29 22:00 ` MFD: move ssbi driver into drivers/mfd Arnd Bergmann
2013-04-29 22:10 ` Greg KH
2013-04-29 22:48 ` Nicolas Pitre
2013-04-30 0:00 ` David Brown
2013-04-30 10:18 ` Samuel Ortiz
2013-04-30 10:26 ` Arnd Bergmann
2013-05-16 9:49 ` Samuel Ortiz
2013-04-29 20:45 ` [GIT PATCH] char/misc patches for 3.10-rc1 Nicolas Pitre
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=CA+55aFwU-bXZ7wn2dOcLNfPMcjDv3Jvqx_LTt7B+-tj4WcP8Mg@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=davidb@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).