linux-kernel - Re: [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI) driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110225035857.GA9985@suse.de>
Date:	Thu, 24 Feb 2011 19:58:57 -0800
From:	Greg KH <gregkh@...e.de>
To:	David Brown <davidb@...eaurora.org>
Cc:	linux-kernel@...r.kernel.org, Dima Zavin <dima@...roid.com>,
	Daniel Walker <dwalker@...o99.com>,
	Kenneth Heitke <kheitke@...eaurora.org>,
	linux-arm-msm@...r.kernel.org, tsoni@...eaurora.org,
	linux-arm-kernel@...ts.infradead.org, swetland@...gle.com
Subject: Re: [PATCH v2 2/2] msm: add single-wire serial bus interface (SSBI)
 driver

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/