From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>,
"Hiremath, Vaibhav" <hvaibhav@ti.com>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Koen Kooi <koen@dominion.thruhere.net>,
Matt Porter <mporter@ti.com>, Russ Dill <Russ.Dill@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [RFC-v2 0/7] Capebus; a bus for SoCs using simple expansion connectors
Date: Mon, 14 Jan 2013 02:23:27 +0000 [thread overview]
Message-ID: <20130114022326.GA4928@sirena.org.uk> (raw)
In-Reply-To: <1351783952-11804-1-git-send-email-panto@antoniou-consulting.com>
On Thu, Nov 01, 2012 at 05:32:25PM +0200, Pantelis Antoniou wrote:
> Capebus is created to address the problem of many SoCs that can provide a
> multitude of hardware interfaces but in order to keep costs down the main
> boards only support a limited number of them. The rest are typically brought
> out to pin connectors on to which other boards, named capes are connected and
> allow those peripherals to be used.
>
> These capes connect to the SoC interfaces but might also contain various other
> parts that may need some kind of driver to work.
I've not yet actually looked at the code but this sounds very similar to
some work I wanted to do on handling coldpluggable modules on reference
designs. In that case it's not so much about pin count as about the
fact that we have to detect at runtime what's connected to the system
but I think the overall effect is very similar and there's definite
overlap.
Can you please CC me on future versions of the code?
prev parent reply other threads:[~2013-01-14 2:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 15:32 [RFC-v2 0/7] Capebus; a bus for SoCs using simple expansion connectors Pantelis Antoniou
2012-11-01 15:32 ` [RFC-v2 1/7] capebus: Core capebus support Pantelis Antoniou
[not found] ` <1351783952-11804-2-git-send-email-panto-wVdstyuyKrO8r51toPun2/C9HSW9iNxf@public.gmane.org>
2013-01-14 2:34 ` Mark Brown
2012-11-01 15:32 ` [RFC-v2 2/7] capebus: Add beaglebone board support Pantelis Antoniou
2012-10-31 17:55 ` Tony Lindgren
2012-10-31 18:06 ` Pantelis Antoniou
2012-11-01 15:32 ` [RFC-v3 3/7] capebus: Beaglebone generic cape support Pantelis Antoniou
2012-11-01 15:32 ` [RFC-v2 4/7] capebus: Beaglebone geiger " Pantelis Antoniou
2012-11-01 15:32 ` [RFC-v2 5/7] capebus: Beaglebone capebus DT update Pantelis Antoniou
2012-11-01 15:32 ` [RFC-v2 6/7] capebus: Document DT bindings Pantelis Antoniou
2012-11-01 15:32 ` [RFC-v2 7/7] capebus: Documentation; capebus-summary Pantelis Antoniou
2013-01-14 2:23 ` Mark Brown [this message]
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=20130114022326.GA4928@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Russ.Dill@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hvaibhav@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mporter@ti.com \
--cc=panto@antoniou-consulting.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).