From: Kishon Vijay Abraham I <kishon@ti.com>
To: Lee Jones <lee.jones@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <kernel@stlinux.com>
Subject: Re: [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x
Date: Mon, 19 May 2014 19:30:19 +0530 [thread overview]
Message-ID: <537A0E73.9080006@ti.com> (raw)
In-Reply-To: <20140519135622.GL4978@lee--X1>
Hi,
On Monday 19 May 2014 07:26 PM, Lee Jones wrote:
> Kishon,
>
> Did you receive this set okay? I believe it's still unmerged?
I think I missed it. But I'm already done with the PULL REQUEST to greg for
3.16 merge window.
Can't we take it through dt tree for miphy?
Thanks
Kishon
>
>> The MiPHY365x is a Generic PHY which can serve various SATA or PCIe
>> devices. It has 2 ports which it can use for either; both SATA, both
>> PCIe or one of each in any configuration.
>>
>> Cc: Kishon Vijay Abraham I <kishon@ti.com>
>> Acked-by: Mark Rutland <mark.rutland@arm.com>
>> Acked-by: Alexandre Torgue <alexandre.torgue@st.com>
>> Signed-off-by: Lee Jones <lee.jones@linaro.org>
>> ---
>> .../devicetree/bindings/phy/phy-miphy365x.txt | 62 ++++++++++++++++++++++
>> 1 file changed, 62 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/phy/phy-miphy365x.txt
>>
>> diff --git a/Documentation/devicetree/bindings/phy/phy-miphy365x.txt b/Documentation/devicetree/bindings/phy/phy-miphy365x.txt
>> new file mode 100644
>> index 0000000..cb39de1
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/phy-miphy365x.txt
>> @@ -0,0 +1,62 @@
>> +STMicroelectronics STi MIPHY365x PHY binding
>> +============================================
>> +
>> +This binding describes a miphy device that is used to control PHY hardware
>> +for SATA and PCIe.
>> +
>> +Required properties:
>> +- compatible : Should be "st,miphy365x-phy"
>> +- #phy-cells : Should be 2 (See second example)
>> + First cell is the port number from:
>> + - MIPHY_PORT_0
>> + - MIPHY_PORT_1
>> + Second cell is device type from:
>> + - MIPHY_TYPE_SATA
>> + - MIPHY_TYPE_PCI
>> +- reg : Address and length of register sets for each device in
>> + "reg-names"
>> +- reg-names : The names of the register addresses corresponding to the
>> + registers filled in "reg", from:
>> + - sata0: For SATA port 0 registers
>> + - sata1: For SATA port 1 registers
>> + - pcie0: For PCIE port 0 registers
>> + - pcie1: For PCIE port 1 registers
>> +- st,syscfg : Should be a phandle of the system configuration register group
>> + which contain the SATA, PCIe mode setting bits
>> +
>> +Optional properties:
>> +- st,sata-gen : Generation of locally attached SATA IP. Expected values
>> + are {1,2,3). If not supplied generation 1 hardware will
>> + be expected
>> +- st,pcie-tx-pol-inv : Bool property to invert the polarity PCIe Tx (Txn/Txp)
>> +- st,sata-tx-pol-inv : Bool property to invert the polarity SATA Tx (Txn/Txp)
>> +
>> +Example:
>> +
>> + miphy365x_phy: miphy365x@fe382000 {
>> + compatible = "st,miphy365x-phy";
>> + #phy-cells = <2>;
>> + reg = <0xfe382000 0x100>,
>> + <0xfe38a000 0x100>,
>> + <0xfe394000 0x100>,
>> + <0xfe804000 0x100>;
>> + reg-names = "sata0", "sata1", "pcie0", "pcie1";
>> + st,syscfg = <&syscfg_rear>;
>> + };
>> +
>> +Specifying phy control of devices
>> +=================================
>> +
>> +Device nodes should specify the configuration required in their "phys"
>> +property, containing a phandle to the miphy device node, a port number
>> +and a device type.
>> +
>> +Example:
>> +
>> +#include <dt-bindings/phy/phy-miphy365x.h>
>> +
>> + sata0: sata@fe380000 {
>> + ...
>> + phys = <&miphy365x_phy MIPHY_PORT_0 MIPHY_TYPE_SATA>;
>> + ...
>> + };
>
next prev parent reply other threads:[~2014-05-19 14:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 7:21 [PATCH 0/4] phy: Introduce support for MiPHY365x Lee Jones
2014-04-29 7:21 ` [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-05-19 13:56 ` Lee Jones
2014-05-19 14:00 ` Kishon Vijay Abraham I [this message]
2014-05-19 14:07 ` Lee Jones
2014-04-29 7:21 ` [PATCH 2/4] phy: miphy365x: Add MiPHY365x header file for DT x Driver defines Lee Jones
2014-04-29 7:21 ` [PATCH 3/4] ARM: DT: STi: Add DT node for MiPHY365x Lee Jones
2014-05-19 15:42 ` [STLinux Kernel] " Maxime Coquelin
2014-05-19 15:51 ` Lee Jones
2014-05-20 7:19 ` Maxime Coquelin
2014-05-20 8:28 ` Lee Jones
2014-05-20 8:41 ` Maxime Coquelin
2014-04-29 7:21 ` [PATCH 4/4] phy: miphy365x: Provide support for the MiPHY356x Generic PHY Lee Jones
-- strict thread matches above, loose matches on Subject: below --
2014-05-22 13:53 [RESEND 0/4] phy: Introduce support for MiPHY365x Lee Jones
2014-05-22 13:53 ` [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-06-10 11:00 ` Kishon Vijay Abraham I
2014-06-17 11:23 ` Lee Jones
2014-06-18 9:50 ` Kishon Vijay Abraham I
2014-06-18 10:04 ` Lee Jones
2014-06-24 9:38 ` Arnd Bergmann
2014-06-24 12:46 ` Lee Jones
2014-06-24 14:08 ` Arnd Bergmann
2014-06-24 14:51 ` Lee Jones
2014-03-12 13:14 [PATCH 0/4] phy: Introduce support for MiPHY365x Lee Jones
2014-03-12 13:14 ` [PATCH 1/4] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-02-14 11:23 Lee Jones
2014-03-05 7:34 ` Mark Rutland
2014-03-05 8:40 ` Lee Jones
2014-03-05 9:12 ` Lee Jones
2014-02-12 16:03 Lee Jones
2014-02-12 16:40 ` Mark Rutland
2014-02-13 11:03 ` Lee Jones
2014-02-13 12: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=537A0E73.9080006@ti.com \
--to=kishon@ti.com \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).