From: Rob Herring <robh@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: p.zabel@pengutronix.de, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: reset: lan966x phy reset driver bindings
Date: Tue, 26 Oct 2021 22:13:58 -0500 [thread overview]
Message-ID: <YXjD9o8ws5KWlafb@robh.at.kernel.org> (raw)
In-Reply-To: <20211019115205.1516311-2-horatiu.vultur@microchip.com>
On Tue, Oct 19, 2021 at 01:52:04PM +0200, Horatiu Vultur wrote:
> Document the lan966x phy reset device driving bindings.
> It is using register access for the internal PHYs and toggles
> GPIO for external PHYs.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> .../bindings/reset/lan966x-phy,rst.yaml | 53 +++++++++++++++++++
> 1 file changed, 53 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reset/lan966x-phy,rst.yaml
>
> diff --git a/Documentation/devicetree/bindings/reset/lan966x-phy,rst.yaml b/Documentation/devicetree/bindings/reset/lan966x-phy,rst.yaml
> new file mode 100644
> index 000000000000..35a32458cafe
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/reset/lan966x-phy,rst.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/reset/lan966x-phy,rst.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Microchip Lan966x PHY Reset
> +
> +maintainers:
> + - Horatiu Vultur <horatiu.vultur@microchip.com>
> +
> +description: |
> + The Microchip Lan966x Switch provides 2 internal PHY which needs to be
> + released from reset before they can be accessed. Also it might have external
> + PHYs which requires to toggle a GPIO before the access to the PHYs.
> +
> +properties:
> + $nodename:
> + pattern: "^phy-reset@[0-9a-f]+$"
^reset-controller@[0-9a-f]+$
> +
> + compatible:
> + const: microchip,lan966x-phy-reset
> +
> + reg:
> + items:
> + - description: internal phy reset registers
Just: maxItems: 1
> +
> + reg-names:
> + const: phy
Not all that useful with only 1 entry.
> +
> + "#reset-cells":
> + const: 1
> +
> + external-phy-reset-gpios:
> + description: used for release of reset of the external PHY
> + maxItems: 1
This belongs in the external PHY's node.
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - "#reset-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + phy_reset: phy-reset@e2010010 {
> + compatible = "microchip,lan966x-phy-reset";
> + reg = <0xe2010010 0x14>;
> + reg-names = "phy";
> + #reset-cells = <1>;
> + };
> --
> 2.33.0
>
>
next prev parent reply other threads:[~2021-10-27 3:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 11:52 [PATCH 0/2] reset: lan996x: Add reset driver for lan966x phys Horatiu Vultur
2021-10-19 11:52 ` [PATCH 1/2] dt-bindings: reset: lan966x phy reset driver bindings Horatiu Vultur
2021-10-27 3:13 ` Rob Herring [this message]
2021-10-29 12:58 ` Horatiu Vultur
2022-03-13 16:00 ` Michael Walle
2021-10-19 11:52 ` [PATCH 2/2] reset: lan966x: Add support for the phy reset on lan966x Horatiu Vultur
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=YXjD9o8ws5KWlafb@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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