[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110816154021.GC15484@opensource.wolfsonmicro.com>
Date: Wed, 17 Aug 2011 00:40:22 +0900
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: David Brown <davidb@...eaurora.org>,
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 Tue, Aug 16, 2011 at 04:32:21PM +0200, Arnd Bergmann wrote:
> 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.
I wouldn't go that far - apart from anything else this is designed for
deployment into cellphones and simlar high end systems where you've got
external components to bolt on somehow, and as we're only just starting
to see silicon coming onto the market we'll have to see exactly what
things look like. This stuff is intended for markets where people bolt
their systems together in very custom ways so automatic discovery is not
a high priority.
--
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/
Powered by blists - more mailing lists