linux-kernel - Re: [RFC PATCH] slimbus: Linux driver framework for SLIMbus.

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]

Date:	Tue, 16 Aug 2011 16:32:21 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	David Brown <davidb@...eaurora.org>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Kenneth Heitke <kheitke@...eaurora.org>, bryanh@...eaurora.org,
	linux-arm-msm@...r.kernel.org,
	Sagar Dharia <sdharia@...eaurora.org>, rdunlap@...otime.net,
	rmk+kernel@....linux.org.uk, john.stultz@...aro.org,
	akpm@...ux-foundation.org, ohad@...ery.com, gregkh@...e.de,
	stefanr@...6.in-berlin.de, lethal@...ux-sh.org,
	linville@...driver.com, zajec5@...il.com,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] slimbus: Linux driver framework for SLIMbus.

On Tuesday 16 August 2011, David Brown wrote:
> On Tue, Aug 16, 2011 at 03:37:28PM +0200, Arnd Bergmann wrote:

> > This is theoretically true, but IIRC David mentioned that the bus is
> > only present on few SoCs and has since been abandoned in favor of standard
> > busses for new devices.
> 
> Actually, this is a different one than the one I was mentioning at the
> Linaro Connect.  I believe SLIMbus is more active
> http://en.wikipedia.org/wiki/SLIMbus
> 
> The other bus I was mentioning is called SSBI, which as far as I know
> is only used to communicate between MSMs and certain Qualcomm
> peripheral chips.

Thanks for the clarification! I assumed these were the same thing because
the patches were posted just after we had talked about the other one.

> Kenneth would better be able to clarify how dynamic the SLIMbus is.

That would definitely be helpful. Also, I'd be very interested to hear
what kind of device probing is available on slimbus. If Mark was
right about devices being discoverable, we need don't need any board
description (dts or hardcoded) but instead a way to match the devices
to drivers based on their HW ID.

	Arnd
--
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/