From: Frank Li <Frank.li@nxp.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Aswath Govindraju <a-govindraju@ti.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Haibo Chen <haibo.chen@nxp.com>,
linux-can@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/5] arm64: dts: imx8mp-evk: Use phys to replace xceiver-supply
Date: Mon, 25 Aug 2025 11:55:38 -0400 [thread overview]
Message-ID: <aKyHehTGrQHWQJaD@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250825-can-v2-4-c461e9fcbc14@nxp.com>
On Mon, Aug 25, 2025 at 04:36:45PM +0800, Peng Fan wrote:
> The TJA1048 used on i.MX8MP-EVK is actually high-speed CAN
> transceiver, not a regulator supply. So use phys to reflect the truth.
nit: wrap at 75 chars. 'transceiver', should be at first line.
Reviewed-by: Frank Li <Frank.Li@nxp.com>
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx8mp-evk.dts | 43 +++++++++-------------------
> 1 file changed, 13 insertions(+), 30 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mp-evk.dts b/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> index c0cc5611048e6a739f13c14bbd2e7b26f2715696..d238d419d87cc7c99d472720c96aade90275cb0f 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> +++ b/arch/arm64/boot/dts/freescale/imx8mp-evk.dts
> @@ -56,6 +56,16 @@ memory@40000000 {
> <0x1 0x00000000 0 0xc0000000>;
> };
>
> + flexcan_phy: can-phy {
> + compatible = "nxp,tja1048";
> + #phy-cells = <1>;
> + max-bitrate = <5000000>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&pinctrl_flexcan_phy>;
> + standby-gpios = <&gpio5 5 GPIO_ACTIVE_LOW>,
> + <&gpio4 27 GPIO_ACTIVE_LOW>;
> + };
> +
> native-hdmi-connector {
> compatible = "hdmi-connector";
> label = "HDMI OUT";
> @@ -103,28 +113,6 @@ reg_audio_pwr: regulator-audio-pwr {
> enable-active-high;
> };
>
> - reg_can1_stby: regulator-can1-stby {
> - compatible = "regulator-fixed";
> - regulator-name = "can1-stby";
> - pinctrl-names = "default";
> - pinctrl-0 = <&pinctrl_flexcan1_reg>;
> - regulator-min-microvolt = <3300000>;
> - regulator-max-microvolt = <3300000>;
> - gpio = <&gpio5 5 GPIO_ACTIVE_HIGH>;
> - enable-active-high;
> - };
> -
> - reg_can2_stby: regulator-can2-stby {
> - compatible = "regulator-fixed";
> - regulator-name = "can2-stby";
> - pinctrl-names = "default";
> - pinctrl-0 = <&pinctrl_flexcan2_reg>;
> - regulator-min-microvolt = <3300000>;
> - regulator-max-microvolt = <3300000>;
> - gpio = <&gpio4 27 GPIO_ACTIVE_HIGH>;
> - enable-active-high;
> - };
> -
> reg_pcie0: regulator-pcie {
> compatible = "regulator-fixed";
> pinctrl-names = "default";
> @@ -431,14 +419,14 @@ ethphy1: ethernet-phy@1 {
> &flexcan1 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_flexcan1>;
> - xceiver-supply = <®_can1_stby>;
> + phys = <&flexcan_phy 0>;
> status = "okay";
> };
>
> &flexcan2 {
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_flexcan2>;
> - xceiver-supply = <®_can2_stby>;
> + phys = <&flexcan_phy 1>;
> status = "disabled";/* can2 pin conflict with pdm */
> };
>
> @@ -903,14 +891,9 @@ MX8MP_IOMUXC_SAI5_RXD3__CAN2_TX 0x154
> >;
> };
>
> - pinctrl_flexcan1_reg: flexcan1reggrp {
> + pinctrl_flexcan_phy: flexcanphygrp {
> fsl,pins = <
> MX8MP_IOMUXC_SPDIF_EXT_CLK__GPIO5_IO05 0x154 /* CAN1_STBY */
> - >;
> - };
> -
> - pinctrl_flexcan2_reg: flexcan2reggrp {
> - fsl,pins = <
> MX8MP_IOMUXC_SAI2_MCLK__GPIO4_IO27 0x154 /* CAN2_STBY */
> >;
> };
>
> --
> 2.37.1
>
next prev parent reply other threads:[~2025-08-25 17:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 8:36 [PATCH v2 0/5] phy: phy-can-transceiver: Support TJA1048/TJA1051 Peng Fan
2025-08-25 8:36 ` [PATCH v2 1/5] dt-bindings: phy: ti,tcan104x-can: Document NXP TJA1051/1048 Peng Fan
2025-08-25 15:39 ` Frank Li
2025-08-25 8:36 ` [PATCH v2 2/5] phy: phy-can-transceiver: Add dual channel support for TJA1048 Peng Fan
2025-08-25 15:52 ` Frank Li
2025-08-25 8:36 ` [PATCH v2 3/5] arm64: dts: imx95-15x15-evk: Use phys to replace xceiver-supply Peng Fan
2025-08-25 15:53 ` Frank Li
2025-08-26 2:19 ` Sherry Sun
2025-08-26 2:28 ` Bough Chen
2025-08-25 8:36 ` [PATCH v2 4/5] arm64: dts: imx8mp-evk: " Peng Fan
2025-08-25 15:55 ` Frank Li [this message]
2025-08-25 8:36 ` [PATCH v2 5/5] arm64: dts: imx93-11x11-evk: " Peng Fan
2025-08-25 15:58 ` Frank Li
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=aKyHehTGrQHWQJaD@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=a-govindraju@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--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).