From: Pantelis Antoniou <panto@antoniou-consulting.com> To: Tony Lindgren <tony@atomide.com> Cc: Pantelis Antoniou <panto@antoniou-consulting.com>, linux-arm-kernel@lists.infradead.org, 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: [RFC 7/7] capebus: Documentation; capebus-summary Date: Wed, 31 Oct 2012 18:52:13 +0200 [thread overview] Message-ID: <1351702333-8456-8-git-send-email-panto@antoniou-consulting.com> (raw) In-Reply-To: <1351702333-8456-1-git-send-email-panto@antoniou-consulting.com> Small summary of capebus. Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com> --- Documentation/capebus/capebus-summary | 40 +++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 Documentation/capebus/capebus-summary diff --git a/Documentation/capebus/capebus-summary b/Documentation/capebus/capebus-summary new file mode 100644 index 0000000..742e33c --- /dev/null +++ b/Documentation/capebus/capebus-summary @@ -0,0 +1,40 @@ +Overview of Linux kernel Capebus support +======================================== + +30-Oct-2012 + +What is Capebus? +---------------- +Capebus is an abstract concept. There's no such thing as a vanilla physical +capebus, what is there is a concept and a method on how various capebus +based implementations can be made. + +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. + +Since SoCs have limited pins and pin muxing options, not all capes can work +together so some kind of resource tracking (at least for the pins in use) is +required. + +Before capebus all of this took place in the board support file, and frankly +for boards with too many capes it was becoming unmanageable. + +Capebus provides a virtual bus, which along with a board specific controller, +cape drivers can be written using the standard Linux device model. + +What kind of systems/boards capebus supports? +--------------------------------------------- + +The core capebus infrastructure is not depended on any specific board. +However capebus needs a board controller to provide services to the cape devices +it controls. Services like addressing and resource reservation are provided +by the board controller. + +Capebus at the moment only support TI's Beaglebone platform. + -- 1.7.12
WARNING: multiple messages have this Message-ID (diff)
From: panto@antoniou-consulting.com (Pantelis Antoniou) To: linux-arm-kernel@lists.infradead.org Subject: [RFC 7/7] capebus: Documentation; capebus-summary Date: Wed, 31 Oct 2012 18:52:13 +0200 [thread overview] Message-ID: <1351702333-8456-8-git-send-email-panto@antoniou-consulting.com> (raw) In-Reply-To: <1351702333-8456-1-git-send-email-panto@antoniou-consulting.com> Small summary of capebus. Signed-off-by: Pantelis Antoniou <panto@antoniou-consulting.com> --- Documentation/capebus/capebus-summary | 40 +++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 Documentation/capebus/capebus-summary diff --git a/Documentation/capebus/capebus-summary b/Documentation/capebus/capebus-summary new file mode 100644 index 0000000..742e33c --- /dev/null +++ b/Documentation/capebus/capebus-summary @@ -0,0 +1,40 @@ +Overview of Linux kernel Capebus support +======================================== + +30-Oct-2012 + +What is Capebus? +---------------- +Capebus is an abstract concept. There's no such thing as a vanilla physical +capebus, what is there is a concept and a method on how various capebus +based implementations can be made. + +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. + +Since SoCs have limited pins and pin muxing options, not all capes can work +together so some kind of resource tracking (at least for the pins in use) is +required. + +Before capebus all of this took place in the board support file, and frankly +for boards with too many capes it was becoming unmanageable. + +Capebus provides a virtual bus, which along with a board specific controller, +cape drivers can be written using the standard Linux device model. + +What kind of systems/boards capebus supports? +--------------------------------------------- + +The core capebus infrastructure is not depended on any specific board. +However capebus needs a board controller to provide services to the cape devices +it controls. Services like addressing and resource reservation are provided +by the board controller. + +Capebus at the moment only support TI's Beaglebone platform. + -- 1.7.12
next prev parent reply other threads:[~2012-10-30 18:59 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-31 16:52 [RFC 0/7] Capebus; a bus for SoCs using simple expansion connectors Pantelis Antoniou 2012-10-31 16:52 ` Pantelis Antoniou 2012-10-31 16:52 ` [RFC 1/7] capebus: Core capebus support Pantelis Antoniou 2012-10-31 16:52 ` Pantelis Antoniou 2012-10-31 21:55 ` Russ Dill 2012-10-31 21:55 ` Russ Dill 2012-10-31 22:07 ` Pantelis Antoniou 2012-10-31 22:07 ` Pantelis Antoniou 2012-11-01 0:55 ` Russ Dill 2012-11-01 0:55 ` Russ Dill 2012-10-31 16:52 ` [RFC 2/7] capebus: Add beaglebone board support Pantelis Antoniou 2012-10-31 16:52 ` Pantelis Antoniou 2012-10-30 19:36 ` Tony Lindgren 2012-10-30 19:36 ` Tony Lindgren 2012-10-30 19:39 ` Tony Lindgren 2012-10-30 19:39 ` Tony Lindgren 2012-10-30 20:16 ` Pantelis Antoniou 2012-10-30 20:16 ` Pantelis Antoniou 2012-10-30 23:57 ` Tony Lindgren 2012-10-30 23:57 ` Tony Lindgren 2012-10-31 16:52 ` [RFC 3/7] capebus: Beaglebone generic cape support Pantelis Antoniou 2012-10-31 16:52 ` Pantelis Antoniou 2012-10-31 16:52 ` [RFC 4/7] capebus: Beaglebone geiger " Pantelis Antoniou 2012-10-31 16:52 ` Pantelis Antoniou 2012-10-31 16:52 ` [RFC 5/7] capebus: Beaglebone capebus DT update Pantelis Antoniou 2012-10-31 16:52 ` Pantelis Antoniou 2012-10-31 16:52 ` [RFC 6/7] capebus: Document DT bindings Pantelis Antoniou 2012-10-31 16:52 ` Pantelis Antoniou 2012-10-31 16:52 ` Pantelis Antoniou [this message] 2012-10-31 16:52 ` [RFC 7/7] capebus: Documentation; capebus-summary Pantelis Antoniou 2012-10-31 21:56 ` [RFC 0/7] Capebus; a bus for SoCs using simple expansion connectors Russ Dill 2012-10-31 21:56 ` Russ Dill 2012-10-31 22:03 ` Pantelis Antoniou 2012-10-31 22:03 ` Pantelis Antoniou
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=1351702333-8456-8-git-send-email-panto@antoniou-consulting.com \ --to=panto@antoniou-consulting.com \ --cc=Russ.Dill@ti.com \ --cc=devicetree-discuss@lists.ozlabs.org \ --cc=koen@dominion.thruhere.net \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=mporter@ti.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.