From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Alexandre Mergnat <amergnat@baylibre.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH v8 07/10] arm64: dts: mediatek: add ethernet support for mt8365-evk
Date: Thu, 25 May 2023 10:49:26 +0200 [thread overview]
Message-ID: <b80ceed1-0c5a-0875-dab0-309e2318d88e@collabora.com> (raw)
In-Reply-To: <20230203-evk-board-support-v8-7-7019f3fd0adf@baylibre.com>
Il 25/05/23 10:33, Alexandre Mergnat ha scritto:
> - Enable "vibr" and "vsim2" regulators to power the ethernet chip.
>
> Tested-by: Kevin Hilman <khilman@baylibre.com>
> Signed-off-by: Alexandre Mergnat <amergnat@baylibre.com>
> ---
> arch/arm64/boot/dts/mediatek/mt8365-evk.dts | 48 +++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8365-evk.dts b/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> index 1a5769c397c2..86524cbf4354 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> @@ -88,6 +88,29 @@ optee_reserved: optee@43200000 {
> };
> };
>
> +ðernet {
> + pinctrl-0 = <ðernet_pins>;
> + pinctrl-names = "default";
> + phy-handle = <ð_phy>;
> + phy-mode = "rmii";
> + /*
> + * Ethernet and HDMI (DSI0) are sharing pins.
> + * Only one can be enabled at a time and require the physical switch
> + * SW2101 to be set on LAN position
> + * mt6357_vibr_reg and mt6357_vsim2_reg are needed to supply ethernet
> + */
> + status = "disabled";
Ouh, that's sad :-(
...but you're left with no other choice, so I agree with providing at least
the full node in case anyone wants to actually enable it by flipping the
switch on the board, so you get my
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cheers!
> +
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + eth_phy: ethernet-phy@0 {
> + reg = <0>;
> + };
> + };
> +};
> +
> &i2c0 {
> clock-frequency = <100000>;
> pinctrl-0 = <&i2c0_pins>;
> @@ -138,6 +161,31 @@ &mt6357_pmic {
> };
>
> &pio {
> + ethernet_pins: ethernet-pins {
> + phy_reset_pins {
> + pinmux = <MT8365_PIN_133_TDM_TX_DATA1__FUNC_GPIO133>;
> + };
> +
> + rmii_pins {
> + pinmux = <MT8365_PIN_0_GPIO0__FUNC_EXT_TXD0>,
> + <MT8365_PIN_1_GPIO1__FUNC_EXT_TXD1>,
> + <MT8365_PIN_2_GPIO2__FUNC_EXT_TXD2>,
> + <MT8365_PIN_3_GPIO3__FUNC_EXT_TXD3>,
> + <MT8365_PIN_4_GPIO4__FUNC_EXT_TXC>,
> + <MT8365_PIN_5_GPIO5__FUNC_EXT_RXER>,
> + <MT8365_PIN_6_GPIO6__FUNC_EXT_RXC>,
> + <MT8365_PIN_7_GPIO7__FUNC_EXT_RXDV>,
> + <MT8365_PIN_8_GPIO8__FUNC_EXT_RXD0>,
> + <MT8365_PIN_9_GPIO9__FUNC_EXT_RXD1>,
> + <MT8365_PIN_10_GPIO10__FUNC_EXT_RXD2>,
> + <MT8365_PIN_11_GPIO11__FUNC_EXT_RXD3>,
> + <MT8365_PIN_12_GPIO12__FUNC_EXT_TXEN>,
> + <MT8365_PIN_13_GPIO13__FUNC_EXT_COL>,
> + <MT8365_PIN_14_GPIO14__FUNC_EXT_MDIO>,
> + <MT8365_PIN_15_GPIO15__FUNC_EXT_MDC>;
> + };
> + };
> +
> gpio_keys: gpio-keys-pins {
> pins {
> pinmux = <MT8365_PIN_24_KPCOL0__FUNC_KPCOL0>;
>
next prev parent reply other threads:[~2023-05-25 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 8:33 [PATCH v8 00/10] Improve the MT8365 SoC and EVK board support Alexandre Mergnat
2023-05-25 8:33 ` [PATCH v8 01/10] arm64: defconfig: enable MT6357 regulator Alexandre Mergnat
2023-05-30 13:28 ` Krzysztof Kozlowski
2023-05-25 8:33 ` [PATCH v8 02/10] arm64: defconfig: enable Mediatek PMIC key Alexandre Mergnat
2023-05-25 8:33 ` [PATCH v8 03/10] arm64: dts: mediatek: add watchdog support for mt8365 SoC Alexandre Mergnat
2023-05-25 8:33 ` [PATCH v8 04/10] arm64: dts: mediatek: add mt6357 PMIC support for mt8365-evk Alexandre Mergnat
2023-05-25 8:33 ` [PATCH v8 05/10] arm64: dts: mediatek: add mmc " Alexandre Mergnat
2023-05-25 8:33 ` [PATCH v8 06/10] arm64: dts: mediatek: add usb controller " Alexandre Mergnat
2023-05-25 8:33 ` [PATCH v8 07/10] arm64: dts: mediatek: add ethernet " Alexandre Mergnat
2023-05-25 8:49 ` AngeloGioacchino Del Regno [this message]
2023-05-25 8:33 ` [PATCH v8 08/10] arm64: dts: mediatek: add OPP support for mt8365 SoC Alexandre Mergnat
2023-05-25 8:33 ` [PATCH v8 09/10] arm64: dts: mediatek: add cpufreq support for mt8365-evk Alexandre Mergnat
2023-05-25 8:33 ` [PATCH v8 10/10] arm64: dts: mediatek: Add CPU Idle support amergnat
2023-05-29 13:22 ` [PATCH v8 00/10] Improve the MT8365 SoC and EVK board support Matthias Brugger
2023-05-29 14:00 ` Alexandre Mergnat
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=b80ceed1-0c5a-0875-dab0-309e2318d88e@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=amergnat@baylibre.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=will@kernel.org \
--cc=wim@linux-watchdog.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