From: Mark Rutland <mark.rutland@arm.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"haifeng.yan@linaro.org" <haifeng.yan@linaro.org>,
"jchxue@gmail.com" <jchxue@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Jiancheng Xue <xuejiancheng@huawei.com>
Subject: Re: [PATCH 1/2] Documentation: Document Hisilicon hix5hd2 sata PHY
Date: Tue, 17 Jun 2014 18:13:57 +0100 [thread overview]
Message-ID: <20140617171357.GH8930@leverpostej> (raw)
In-Reply-To: <1402991881-27676-2-git-send-email-zhangfei.gao@linaro.org>
On Tue, Jun 17, 2014 at 08:58:00AM +0100, Zhangfei Gao wrote:
> From: Jiancheng Xue <xuejiancheng@huawei.com>
>
> Add necessary binding documentation SATA PHY on Hisilicon hix5hd2 soc.
>
> Signed-off-by: Jiancheng Xue <xuejiancheng@huawei.com>
> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
> ---
> .../devicetree/bindings/phy/hix5hd2-sata-phy.txt | 26 ++++++++++++++++++++
> 1 file changed, 26 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/hix5hd2-sata-phy.txt
>
> diff --git a/Documentation/devicetree/bindings/phy/hix5hd2-sata-phy.txt b/Documentation/devicetree/bindings/phy/hix5hd2-sata-phy.txt
> new file mode 100644
> index 0000000..ed15123
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/hix5hd2-sata-phy.txt
> @@ -0,0 +1,26 @@
> +Hisilicon hix5hd2 SATA PHY
> +-----------------------
> +
> +Required properties:
> +- compatible: should be "hisilicon,hix5hd2-sata-phy"
> +- reg: offset and length of the PHY registers
> +- #phy-cells: must be 0
> +Refer to phy/phy-bindings.txt for the generic PHY binding properties
> +
> +Optional Properties:
> +- hisilicon,peri-syscon: phandle of syscon used to control peripheral.
"peri" is a rather strange contraction of "peripheral".
> +- hisilicon,power-reg: offset and bit number of the sata power supply register.
> + Only effective when hisilicon,peri-syscon is supplied.
This is the offset within the system controller? It would be good to
state that.
> +- hisilicon,reg-init: one of more sets of 4 cells. The first cell
> + is the register offset address, the second cell is the start bit in register,
> + the third cell means the bit width, and the fourth cell is the value to set.
Which registers is this meant to be initialising?
Why does this need to be in the DT? How much is this expected to vary?
Mark.
next prev parent reply other threads:[~2014-06-17 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 7:57 [PATCH 0/2] phy: add hix5hd2-sata-phy driver Zhangfei Gao
2014-06-17 7:58 ` [PATCH 1/2] Documentation: Document Hisilicon hix5hd2 sata PHY Zhangfei Gao
2014-06-17 17:13 ` Mark Rutland [this message]
2014-06-20 5:45 ` zhangfei
2014-06-17 7:58 ` [PATCH 2/2] phy: add hix5hd2-sata-phy driver Zhangfei Gao
2014-06-17 17:23 ` Mark Rutland
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=20140617171357.GH8930@leverpostej \
--to=mark.rutland@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=haifeng.yan@linaro.org \
--cc=jchxue@gmail.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xuejiancheng@huawei.com \
--cc=zhangfei.gao@linaro.org \
/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