[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50A2919D.5030006@wwwdotorg.org>
Date: Tue, 13 Nov 2012 11:29:49 -0700
From: Stephen Warren <swarren@...dotorg.org>
To: Mitch Bradley <wmb@...mworks.com>
CC: David Gibson <david@...son.dropbear.id.au>,
Kevin Hilman <khilman@...com>, Matt Porter <mporter@...com>,
Koen Kooi <koen@...inion.thruhere.net>,
Pantelis Antoniou <panto@...oniou-consulting.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Felipe Balbi <balbi@...com>,
Deepak Saxena <dsaxena@...aro.org>,
Russ Dill <Russ.Dill@...com>,
Scott Wood <scottwood@...escale.com>,
linux-omap@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org
Subject: Re: [RFC] Device Tree Overlays Proposal (Was Re: capebus moving omap_devices
to mach-omap2)
On 11/13/2012 11:10 AM, Mitch Bradley wrote:
> It seems to me that this capebus discussion is missing an important
> point. The name capebus suggests that it is a bus, so there should be a
> parent node to represent that bus. It should have a driver whose API
> implements all of the system-interface functions a cape needs.
It was discussed earlier that capebus isn't actually a bus. It's simply
a collection of a bunch of pins from the SoC hooked up to connectors.
I'd agree that it's mis-named.
--
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