public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brown <davidb@codeaurora.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Greg KH <gregkh@linuxfoundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nicolas Pitre <nico@fluxnic.net>,
	Richard Kuo <rkuo@codeaurora.org>,
	linux-hexagon@vger.kernel.org
Subject: Re: [GIT PATCH] char/misc patches for 3.10-rc1
Date: Mon, 29 Apr 2013 14:08:23 -0700	[thread overview]
Message-ID: <8yafvy92gfs.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <CA+55aFzefpRz2Y8oW9q0ArrR=XW0POBhy8NSNJ3DrCh9EowLqg@mail.gmail.com> (Linus Torvalds's message of "Mon, 29 Apr 2013 13:12:54 -0700")

Linus Torvalds <torvalds@linux-foundation.org> writes:

> There are other things wrong with that whole SSBI driver crap that you
> seem to be ignoring:
>
>  - it's not a bus, it's just a driver. Just because some people call
> it "serial bus" doesn't make it magically about a "bus". I can call an
> ethernet driver an "ethernet bus driver", and it may be technically
> correct, but it is still bullshit. And ethernet is damn more a real
> bus than that SSBI driver is. That's just a pure serial driver for a
> very specific piece of embedded hardware. Stop calling it a bus.

Correct.  Despite having "bus" in the name, it isn't really a bus.  It's
a point-to-point serial interface to a non-addressible device.

>  - The whole Kconfig thing is complete and utter garbage. There is no
> excuse what-so-ever for ever asking the user about it. Not on x86, not
> on ARM. The drivers that actually *use* that magical serial line
> driver should just have selected it.

Agreed

>  - I'm not seeing what commonalities this thing can have with anything
> else. Did anybody look at the code? There's nothing generic there.

This driver has one purpose, and will only ever have this one purpose:
to connect the MSM SOC to a small family of power management chips.  It
is theoretically possible to connect it to other things, and I think
there have been some obscure designs that do this, but not anything that
is going to be supported in the kernel.

> So move it to a saner place, fix the kconfig idiocy, and don't make
> noises as if it's some generic driver, much less some generic bus.
> It's not.

So, what is this saner place?  The hardware is theoretically shared
between ARM and Hexagon, but I don't know the hexagon plans to support
it, I've added them to the CC.

I'm not sure why this shouldn't be in the drivers/mfd directory
alongside the various pm*.c drivers that use it.  It isn't going to be
used for anything else.

Given the bikeshedding that happened when Ken pushed the driver out last
time, though, I'm sure this will create a firestorm of disagreement over
its location.

David

-- 
sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

  parent reply	other threads:[~2013-04-29 21:08 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
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 [this message]
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=8yafvy92gfs.fsf@huya.qualcomm.com \
    --to=davidb@codeaurora.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=rkuo@codeaurora.org \
    --cc=torvalds@linux-foundation.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