From: Andrew Lunn <andrew@lunn.ch>
To: Gilles Talis <gilles.talis@gmail.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
shawnguo@kernel.org, festevam@gmail.com, alex@voxelbotics.com
Subject: Re: [PATCH 3/3] arm64: dts: freescale: Add device tree for Emcraft Systems NavQ+ Kit
Date: Thu, 28 Mar 2024 21:42:04 +0100 [thread overview]
Message-ID: <147dfc5e-91e5-4ad4-b818-f6717e62df45@lunn.ch> (raw)
In-Reply-To: <20240328202320.187596-4-gilles.talis@gmail.com>
> +&eqos {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_eqos>;
> + phy-mode = "rgmii-id";
> + phy-handle = <ðphy0>;
> + status = "okay";
> +
> + mdio {
> + compatible = "snps,dwmac-mdio";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ethphy0: ethernet-phy@0 {
> + compatible = "ethernet-phy-ieee802.3-c22";
> + reg = <0>;
> + reset-gpios = <&gpio4 22 GPIO_ACTIVE_LOW>;
> + reset-assert-us = <1000>;
> + reset-deassert-us = <10000>;
> + qca,disable-smarteee;
> + qca,disable-hibernation-mode;
> + vddio-supply = <&vddio>;
> +
> + vddio: vddio-regulator {
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + };
Please could you explain what this last node is doing.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Gilles Talis <gilles.talis@gmail.com>
Cc: devicetree@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh@kernel.org,
shawnguo@kernel.org, festevam@gmail.com, alex@voxelbotics.com
Subject: Re: [PATCH 3/3] arm64: dts: freescale: Add device tree for Emcraft Systems NavQ+ Kit
Date: Thu, 28 Mar 2024 21:42:04 +0100 [thread overview]
Message-ID: <147dfc5e-91e5-4ad4-b818-f6717e62df45@lunn.ch> (raw)
In-Reply-To: <20240328202320.187596-4-gilles.talis@gmail.com>
> +&eqos {
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_eqos>;
> + phy-mode = "rgmii-id";
> + phy-handle = <ðphy0>;
> + status = "okay";
> +
> + mdio {
> + compatible = "snps,dwmac-mdio";
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + ethphy0: ethernet-phy@0 {
> + compatible = "ethernet-phy-ieee802.3-c22";
> + reg = <0>;
> + reset-gpios = <&gpio4 22 GPIO_ACTIVE_LOW>;
> + reset-assert-us = <1000>;
> + reset-deassert-us = <10000>;
> + qca,disable-smarteee;
> + qca,disable-hibernation-mode;
> + vddio-supply = <&vddio>;
> +
> + vddio: vddio-regulator {
> + regulator-min-microvolt = <1800000>;
> + regulator-max-microvolt = <1800000>;
> + };
Please could you explain what this last node is doing.
Andrew
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-28 20:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 20:23 [PATCH 0/3] Add support for Emcraft Systems NavQ+ kit Gilles Talis
2024-03-28 20:23 ` Gilles Talis
2024-03-28 20:23 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Emcraft Systems Gilles Talis
2024-03-28 20:23 ` Gilles Talis
2024-03-28 22:00 ` Krzysztof Kozlowski
2024-03-28 22:00 ` Krzysztof Kozlowski
2024-03-28 20:23 ` [PATCH 2/3] dt-bindings: arm: Add Emcraft Systems i.MX8M Plus NavQ+ Kit Gilles Talis
2024-03-28 20:23 ` Gilles Talis
2024-03-28 22:00 ` Krzysztof Kozlowski
2024-03-28 22:00 ` Krzysztof Kozlowski
2024-03-28 20:23 ` [PATCH 3/3] arm64: dts: freescale: Add device tree for Emcraft Systems " Gilles Talis
2024-03-28 20:23 ` Gilles Talis
2024-03-28 20:42 ` Andrew Lunn [this message]
2024-03-28 20:42 ` Andrew Lunn
2024-03-29 22:08 ` Gilles Talis
2024-03-29 22:08 ` Gilles Talis
2024-03-28 22:04 ` Krzysztof Kozlowski
2024-03-28 22:04 ` Krzysztof Kozlowski
2024-03-29 21:43 ` Gilles Talis
2024-03-28 22:55 ` Fabio Estevam
2024-03-28 22:55 ` Fabio Estevam
2024-03-29 21:44 ` Gilles Talis
2024-03-28 21:01 ` [PATCH 0/3] Add support for Emcraft Systems NavQ+ kit Rob Herring
2024-03-28 21:01 ` Rob Herring
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=147dfc5e-91e5-4ad4-b818-f6717e62df45@lunn.ch \
--to=andrew@lunn.ch \
--cc=alex@voxelbotics.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gilles.talis@gmail.com \
--cc=imx@lists.linux.dev \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=shawnguo@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 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.