From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] phy: miphy365x: Add Device Tree bindings for the MiPHY365x
Date: Wed, 2 Jul 2014 14:54:45 +0530 [thread overview]
Message-ID: <53B3CFDD.5090504@ti.com> (raw)
In-Reply-To: <1404133317-25953-2-git-send-email-lee.jones@linaro.org>
Hi,
On Monday 30 June 2014 06:31 PM, Lee Jones wrote:
> 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 | 76 ++++++++++++++++++++++
> 1 file changed, 76 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..d75f300
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/phy-miphy365x.txt
> @@ -0,0 +1,76 @@
> +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
I'm just thinking if we can directly give phandle to the sub-node
(channel0/channel1 or port0/port1) we won't need this information in the PHY
specifier. This might need some modification in the phy-core but that can be done.
> + 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
this information should be in the documentation of sub-nodes.
Cheers
Kishon
WARNING: multiple messages have this Message-ID (diff)
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/5] phy: miphy365x: Add Device Tree bindings for the MiPHY365x
Date: Wed, 2 Jul 2014 14:54:45 +0530 [thread overview]
Message-ID: <53B3CFDD.5090504@ti.com> (raw)
In-Reply-To: <1404133317-25953-2-git-send-email-lee.jones@linaro.org>
Hi,
On Monday 30 June 2014 06:31 PM, Lee Jones wrote:
> 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 | 76 ++++++++++++++++++++++
> 1 file changed, 76 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..d75f300
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/phy-miphy365x.txt
> @@ -0,0 +1,76 @@
> +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
I'm just thinking if we can directly give phandle to the sub-node
(channel0/channel1 or port0/port1) we won't need this information in the PHY
specifier. This might need some modification in the phy-core but that can be done.
> + 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
this information should be in the documentation of sub-nodes.
Cheers
Kishon
next prev parent reply other threads:[~2014-07-02 9:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 13:01 [PATCH 0/5] phy: miphy365x: Introduce support for MiPHY365x Lee Jones
2014-06-30 13:01 ` Lee Jones
2014-06-30 13:01 ` [PATCH 1/5] phy: miphy365x: Add Device Tree bindings for the MiPHY365x Lee Jones
2014-06-30 13:01 ` Lee Jones
2014-07-02 9:24 ` Kishon Vijay Abraham I [this message]
2014-07-02 9:24 ` Kishon Vijay Abraham I
2014-07-02 12:06 ` Lee Jones
2014-07-02 12:06 ` Lee Jones
2014-07-03 9:06 ` Kishon Vijay Abraham I
2014-07-03 9:06 ` Kishon Vijay Abraham I
2014-06-30 13:01 ` [PATCH 2/5] phy: miphy365x: Add MiPHY365x header file for DT x Driver defines Lee Jones
2014-06-30 13:01 ` Lee Jones
2014-07-02 9:28 ` Kishon Vijay Abraham I
2014-07-02 9:28 ` Kishon Vijay Abraham I
2014-07-02 12:02 ` Lee Jones
2014-07-02 12:02 ` Lee Jones
2014-06-30 13:01 ` [PATCH 3/5] phy: miphy365x: Provide support for the MiPHY356x Generic PHY Lee Jones
2014-06-30 13:01 ` Lee Jones
2014-07-02 10:19 ` Kishon Vijay Abraham I
2014-07-02 10:19 ` Kishon Vijay Abraham I
2014-07-02 12:00 ` Lee Jones
2014-07-02 12:00 ` Lee Jones
2014-07-03 8:07 ` Lee Jones
2014-07-03 8:07 ` Lee Jones
2014-07-03 10:06 ` Kishon Vijay Abraham I
2014-07-03 10:06 ` Kishon Vijay Abraham I
2014-07-04 13:55 ` Gabriel Fernandez
2014-07-04 13:55 ` Gabriel Fernandez
2014-07-08 7:15 ` Lee Jones
2014-07-08 7:15 ` Lee Jones
2014-06-30 13:01 ` [PATCH 4/5] phy: miphy365x: Represent each PHY channel as a subnode Lee Jones
2014-06-30 13:01 ` Lee Jones
2014-06-30 13:06 ` [STLinux Kernel] " Maxime Coquelin
2014-06-30 13:06 ` Maxime Coquelin
2014-06-30 13:52 ` Lee Jones
2014-06-30 13:52 ` Lee Jones
2014-06-30 14:41 ` [PATCH v2 " Lee Jones
2014-06-30 14:41 ` Lee Jones
2014-07-02 10:26 ` Kishon Vijay Abraham I
2014-07-02 10:26 ` Kishon Vijay Abraham I
2014-07-02 11:34 ` Lee Jones
2014-07-02 11:34 ` Lee Jones
2014-07-02 11:57 ` Kishon Vijay Abraham I
2014-07-02 11:57 ` Kishon Vijay Abraham I
2014-07-02 12:19 ` Lee Jones
2014-07-02 12:19 ` Lee Jones
2014-06-30 13:01 ` [PATCH 5/5] ARM: DT: STi: Add DT node for MiPHY365x Lee Jones
2014-06-30 13:01 ` Lee Jones
2014-07-03 14:08 ` Gabriel Fernandez
2014-07-03 14:08 ` Gabriel Fernandez
2014-07-02 9:19 ` [PATCH 0/5] phy: miphy365x: Introduce support " Kishon Vijay Abraham I
2014-07-02 9:19 ` Kishon Vijay Abraham I
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=53B3CFDD.5090504@ti.com \
--to=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 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.