linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <akhil.goyal@freescale.com>
To: <gregkh@linuxfoundation.org>, <arnd@arndb.de>, <lars@metafoo.de>,
	<robin.getz@analog.com>, <Michael.Hennerich@analog.com>,
	<lars-peter.clausen@analog.com>
Cc: <linux-kernel@vger.kernel.org>, <pankaj.chauhan@freescale.com>,
	Akhil Goyal <akhil.goyal@freescale.com>
Subject: [PATCH v2 3/4] binding: Add device tree bindings for freescale AIC
Date: Mon, 12 Aug 2013 12:43:52 +0530	[thread overview]
Message-ID: <1376291633-4682-4-git-send-email-akhil.goyal@freescale.com> (raw)
In-Reply-To: <1376291633-4682-3-git-send-email-akhil.goyal@freescale.com>

From: Akhil Goyal <akhil.goyal@freescale.com>

For platforms like BSC9131 and BSC9132, a Radio framework for supporting
various network modes comprise of an Antenna interface controller driver
and a phy driver.
A combination of AIC lane and phy is called a rf device which can be used
to operate on a particular network mode.

This patch explain various device tree properties required for AIC driver

Signed-off-by: Akhil Goyal <akhil.goyal@freescale.com>
---
 Documentation/devicetree/bindings/rf/fsl-aic.txt |   47 ++++++++++++++++++++++
 1 files changed, 47 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/rf/fsl-aic.txt

diff --git a/Documentation/devicetree/bindings/rf/fsl-aic.txt b/Documentation/devicetree/bindings/rf/fsl-aic.txt
new file mode 100644
index 0000000..4f54a92
--- /dev/null
+++ b/Documentation/devicetree/bindings/rf/fsl-aic.txt
@@ -0,0 +1,47 @@
+Freescale Antenna Interface Controller
+
+AIC is the antenna interface controller found in bsc913x
+family of SOCs. It supports NCDMA, WCDMA-FDD, LTE-FDD, LTE-TDD
+and GSM-SNIFF network modes. AIC has multiple lanes on which RFICs
+can be connected. And AIC supports 4 RFICs working simultaneously.
+
+Required Properties:
+- #address-cells : should be 1
+- #size-cells : should be 1
+- compatible : should be fsl,bsc9131-aic or fsl,bsc9132-aic or both
+- reg : offset and length of common register set of AIC
+- interrupts : For AIC, first is capture complete interrupt
+		second is dsp general interrupt
+aic node can have multiple sub nodes of aiclanes for each lane.
+- aiclane : Required Properties
+	- reg : offset and length of common register set of AIC lane
+	- lane_id : it can be 0, 1, 2, 3, 4, 5
+	- interrupts : lane specific TTI interrupt line
+
+For Example:
+
+aic@50000 {
+	#address-cells = <1>;
+	#size-cells = <1>;
+	compatible = "fsl,bsc9131-aic", "fsl,bsc9132-aic";
+	reg = <0x50000 0x200>;
+	interrupts = <49 2 0 0 53 2 0 0>;
+	lane0: aiclane@200 {
+		reg = <0x200 0x200>;
+		lane_id = <0>;
+		interrupts = <45 2 0 0>;
+	};
+
+	lane1: aiclane@400 {
+		reg = <0x400 0x200>;
+		lane_id = <1>;
+		interrupts = <46 2 0 0>;
+	};
+
+	lane2: aiclane@600 {
+		reg = <0x600 0x200>;
+		lane_id = <2>;
+		interrupts = <47 2 0 0>;
+	};
+};
+
-- 
1.6.3.1




  reply	other threads:[~2013-08-12  7:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12  7:13 [PATCH v2 0/4][Resend] Radio device framework akhil.goyal
2013-08-12  7:13 ` [PATCH v2 1/4] drivers/misc: Support for RF interface " akhil.goyal
2013-08-12  7:13   ` [PATCH v2 2/4] drivers/misc/rf: AIC: Freescale Antenna Interface controller driver akhil.goyal
2013-08-12  7:13     ` akhil.goyal [this message]
2013-08-12  7:13       ` [PATCH v2 4/4] BSC9131rdb/dts: Add nodes for supporting AIC akhil.goyal
2013-08-12 22:53   ` [PATCH v2 1/4] drivers/misc: Support for RF interface device framework Greg KH
2013-08-14  5:59     ` Akhil Goyal
  -- strict thread matches above, loose matches on Subject: below --
2013-07-08  9:49 [PATCH v2 0/4] Radio " akhil.goyal
2013-07-08  9:49 ` [PATCH v2 1/4] drivers/misc: Support for RF interface " akhil.goyal
2013-07-08  9:50   ` [PATCH v2 2/4] drivers/misc/rf: AIC: Freescale Antenna Interface controller driver akhil.goyal
2013-07-08  9:50     ` [PATCH v2 3/4] binding: Add device tree bindings for freescale AIC akhil.goyal

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=1376291633-4682-4-git-send-email-akhil.goyal@freescale.com \
    --to=akhil.goyal@freescale.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=lars-peter.clausen@analog.com \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pankaj.chauhan@freescale.com \
    --cc=robin.getz@analog.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).