From: Greg KH <gregkh@suse.de>
To: David Brown <davidb@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, Dima Zavin <dima@android.com>,
Daniel Walker <dwalker@fifo99.com>,
Kenneth Heitke <kheitke@codeaurora.org>,
linux-arm-msm@vger.kernel.org, tsoni@codeaurora.org,
linux-arm-kernel@lists.infradead.org, swetland@google.com
Subject: Re: [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver
Date: Thu, 24 Feb 2011 19:58:57 -0800 [thread overview]
Message-ID: <20110225035857.GA9985@suse.de> (raw)
In-Reply-To: <8yavd08bwgi.fsf@huya.qualcomm.com>
On Thu, Feb 24, 2011 at 07:54:21PM -0800, David Brown wrote:
> On Thu, Feb 24 2011, Greg KH wrote:
>
> > drivers/ssbi? What's keeping this from later moving off of the msm
> > chips to run on others? USB started out only on one processor, as did a
> > lot of other bus-specific drivers, before the hardware became present on
> > other architectures. So no need to bury it under a msm specific
> > location.
>
> Not sure if anything is stopping it from moving off of MSM chips, but it
> doesn't seem very likely. There are too many similar interfaces that
> are standard that others would be likely to use. For the most part, it
> is the bus to communicate between the MSM and it's specialized
> peripherals.
>
> We can still put it there, but it will likely be the only driver ever in
> the directory.
Ah, so it's just one driver? Then how about drivers/platform/msm/ ?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@suse.de (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver
Date: Thu, 24 Feb 2011 19:58:57 -0800 [thread overview]
Message-ID: <20110225035857.GA9985@suse.de> (raw)
In-Reply-To: <8yavd08bwgi.fsf@huya.qualcomm.com>
On Thu, Feb 24, 2011 at 07:54:21PM -0800, David Brown wrote:
> On Thu, Feb 24 2011, Greg KH wrote:
>
> > drivers/ssbi? What's keeping this from later moving off of the msm
> > chips to run on others? USB started out only on one processor, as did a
> > lot of other bus-specific drivers, before the hardware became present on
> > other architectures. So no need to bury it under a msm specific
> > location.
>
> Not sure if anything is stopping it from moving off of MSM chips, but it
> doesn't seem very likely. There are too many similar interfaces that
> are standard that others would be likely to use. For the most part, it
> is the bus to communicate between the MSM and it's specialized
> peripherals.
>
> We can still put it there, but it will likely be the only driver ever in
> the directory.
Ah, so it's just one driver? Then how about drivers/platform/msm/ ?
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-25 3:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 22:19 [PATCH v2 0/2] msm: add single-wire serial bus interface (SSBI) driver Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-24 22:19 ` [PATCH v2 1/2] MAINTAINERS: Add drivers/msm to MSM subsystem Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-24 23:08 ` Nicolas Pitre
2011-02-24 23:08 ` Nicolas Pitre
2011-02-24 22:19 ` [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-24 22:19 ` Kenneth Heitke
2011-02-25 2:23 ` Daniel Walker
2011-02-25 2:23 ` Daniel Walker
2011-02-25 2:31 ` David Brown
2011-02-25 2:31 ` David Brown
2011-02-25 2:35 ` Daniel Walker
2011-02-25 2:35 ` Daniel Walker
2011-02-25 2:39 ` Dima Zavin
2011-02-25 2:39 ` Dima Zavin
2011-02-25 3:20 ` David Brown
2011-02-25 3:20 ` David Brown
2011-02-25 3:28 ` Greg KH
2011-02-25 3:28 ` Greg KH
2011-02-25 3:54 ` David Brown
2011-02-25 3:54 ` David Brown
2011-02-25 3:58 ` Greg KH [this message]
2011-02-25 3:58 ` Greg KH
2011-02-25 4:06 ` David Brown
2011-02-25 4:06 ` David Brown
2011-02-25 19:00 ` David Brown
2011-02-25 19:00 ` David Brown
2011-02-25 20:21 ` Brian Swetland
2011-02-25 20:21 ` Brian Swetland
2011-02-25 20:21 ` Brian Swetland
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=20110225035857.GA9985@suse.de \
--to=gregkh@suse.de \
--cc=davidb@codeaurora.org \
--cc=dima@android.com \
--cc=dwalker@fifo99.com \
--cc=kheitke@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
--cc=tsoni@codeaurora.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 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.