From: "Rafał Miłecki" <zajec5@gmail.com>
To: Kishon Vijay Abraham I <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Hauke Mehrtens" <hauke@hauke-m.de>,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
linux-phy@lists.infradead.org,
"Vivek Unune" <npcomplete13@gmail.com>
Subject: Re: [PATCH] dt-bindings: phy: bcm-ns-usb3-phy: convert to yaml
Date: Thu, 11 Mar 2021 21:31:58 +0100 [thread overview]
Message-ID: <ed093ddb-da37-c3c4-cdd9-3b8e8db776bb@gmail.com> (raw)
In-Reply-To: <20201116074650.16070-1-zajec5@gmail.com>
Hi,
On 16.11.2020 08:46, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> 1. Change syntax from txt to yaml
> 2. Drop "Driver for" from the title
> 3. Drop "reg = <0x0>;" from example (noticed by dt_binding_check)
> 4. Specify license
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> I think this should go through linux-phy tree. Kishon, Vinod, can you
> take this patch?
>
> This patch generates a false positive checkpatch.pl warning [0].
> Please ignore:
> WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.rst
>
> [0] https://lkml.org/lkml/2020/2/18/1084
Kishon, Vinod: I sent this patch back in December, it was Reviewed-by
Rob, but never accepted.
Could you push this patch to the linux-phy.git?
> ---
> .../bindings/phy/bcm-ns-usb3-phy.txt | 34 ----------
> .../bindings/phy/bcm-ns-usb3-phy.yaml | 62 +++++++++++++++++++
> 2 files changed, 62 insertions(+), 34 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.txt
> create mode 100644 Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.yaml
>
> diff --git a/Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.txt b/Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.txt
> deleted file mode 100644
> index 32f057260351..000000000000
> --- a/Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.txt
> +++ /dev/null
> @@ -1,34 +0,0 @@
> -Driver for Broadcom Northstar USB 3.0 PHY
> -
> -Required properties:
> -
> -- compatible: one of: "brcm,ns-ax-usb3-phy", "brcm,ns-bx-usb3-phy".
> -- reg: address of MDIO bus device
> -- usb3-dmp-syscon: phandle to syscon with DMP (Device Management Plugin)
> - registers
> -- #phy-cells: must be 0
> -
> -Initialization of USB 3.0 PHY depends on Northstar version. There are currently
> -three known series: Ax, Bx and Cx.
> -Known A0: BCM4707 rev 0
> -Known B0: BCM4707 rev 4, BCM53573 rev 2
> -Known B1: BCM4707 rev 6
> -Known C0: BCM47094 rev 0
> -
> -Example:
> - mdio: mdio@0 {
> - reg = <0x0>;
> - #size-cells = <1>;
> - #address-cells = <0>;
> -
> - usb3-phy@10 {
> - compatible = "brcm,ns-ax-usb3-phy";
> - reg = <0x10>;
> - usb3-dmp-syscon = <&usb3_dmp>;
> - #phy-cells = <0>;
> - };
> - };
> -
> - usb3_dmp: syscon@18105000 {
> - reg = <0x18105000 0x1000>;
> - };
> diff --git a/Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.yaml b/Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.yaml
> new file mode 100644
> index 000000000000..7fd419db45d0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/bcm-ns-usb3-phy.yaml
> @@ -0,0 +1,62 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/phy/bcm-ns-usb3-phy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Broadcom Northstar USB 3.0 PHY
> +
> +description: |
> + Initialization of USB 3.0 PHY depends on Northstar version. There are currently
> + three known series: Ax, Bx and Cx.
> + Known A0: BCM4707 rev 0
> + Known B0: BCM4707 rev 4, BCM53573 rev 2
> + Known B1: BCM4707 rev 6
> + Known C0: BCM47094 rev 0
> +
> +maintainers:
> + - Rafał Miłecki <rafal@milecki.pl>
> +
> +properties:
> + compatible:
> + enum:
> + - brcm,ns-ax-usb3-phy
> + - brcm,ns-bx-usb3-phy
> +
> + reg:
> + description: address of MDIO bus device
> + maxItems: 1
> +
> + usb3-dmp-syscon:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description:
> + Phandle to the DMP (Device Management Plugin) syscon
> +
> + "#phy-cells":
> + const: 0
> +
> +required:
> + - compatible
> + - reg
> + - usb3-dmp-syscon
> + - "#phy-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + usb3-phy@10 {
> + compatible = "brcm,ns-ax-usb3-phy";
> + reg = <0x10>;
> + usb3-dmp-syscon = <&usb3_dmp>;
> + #phy-cells = <0>;
> + };
> + };
> +
> + usb3_dmp: syscon@18105000 {
> + reg = <0x18105000 0x1000>;
> + };
>
next prev parent reply other threads:[~2021-03-11 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 7:46 [PATCH] dt-bindings: phy: bcm-ns-usb3-phy: convert to yaml Rafał Miłecki
2020-11-16 7:46 ` [PATCH] dt-bindings: phy: bcm-ns-usb2-phy: " Rafał Miłecki
2020-12-07 19:21 ` Rob Herring
2021-03-11 20:33 ` Rafał Miłecki
2020-11-19 6:30 ` [PATCH] dt-bindings: phy: bcm-ns-usb3-phy: " Vinod Koul
2020-11-30 15:43 ` Vinod Koul
2020-11-30 15:58 ` Rafał Miłecki
2020-11-30 16:01 ` Rafał Miłecki
2020-12-07 19:20 ` Rob Herring
2021-03-11 20:31 ` Rafał Miłecki [this message]
2021-03-15 10:41 ` Vinod Koul
2021-03-15 17:27 ` Rafał Miłecki
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=ed093ddb-da37-c3c4-cdd9-3b8e8db776bb@gmail.com \
--to=zajec5@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=npcomplete13@gmail.com \
--cc=rafal@milecki.pl \
--cc=vkoul@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).