From: "Kumar, Udit" <u-kumar1@ti.com>
To: <sabiya.d@mistralsolutions.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <linus.walleij@linaro.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Dasnavis Sabiya <sabiya.d@ti.com>
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-am69-sk: Enable CAN interfaces for AM69 SK board
Date: Fri, 19 Jan 2024 18:50:09 +0530 [thread overview]
Message-ID: <5605f593-8526-46b8-9a71-4cbbf013e96e@ti.com> (raw)
In-Reply-To: <20240118153524.4135901-2-sabiya.d@ti.com>
On 1/18/2024 9:05 PM, sabiya.d@mistralsolutions.com wrote:
> From: Dasnavis Sabiya <sabiya.d@ti.com>
>
> AM69 SK board has several CAN bus interfaces on both MCU and MAIN domains.
> This enables the CAN interfaces on MCU and MAIN domain.
>
> Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am69-sk.dts | 85 +++++++++++++++++++++++++++
> 1 file changed, 85 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am69-sk.dts b/arch/arm64/boot/dts/ti/k3-am69-sk.dts
> index 370980eb59b0..feb571a5a0f5 100644
> --- a/arch/arm64/boot/dts/ti/k3-am69-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am69-sk.dts
> @@ -29,6 +29,10 @@ aliases {
> i2c0 = &wkup_i2c0;
> i2c3 = &main_i2c0;
> ethernet0 = &mcu_cpsw_port1;
> + can0 = &mcu_mcan0;
> + can1 = &mcu_mcan1;
> + can2 = &main_mcan6;
> + can3 = &main_mcan7;
AFAIK, can sub system does not support aliasing.
IMO, you can remove these.
> };
>
> memory@80000000 {
> @@ -321,6 +325,31 @@ tfp410_out: endpoint {
> };
> };
> };
> +
> + transceiver1: can-phy0 {
> + compatible = "ti,tcan1042";
> + #phy-cells = <0>;
> + max-bitrate = <5000000>;
> + };
> +
> + transceiver2: can-phy1 {
> + compatible = "ti,tcan1042";
> + #phy-cells = <0>;
> + max-bitrate = <5000000>;
> + };
> +
> + transceiver3: can-phy2 {
> + compatible = "ti,tcan1042";
> + #phy-cells = <0>;
> + max-bitrate = <5000000>;
> + };
> +
> + transceiver4: can-phy3 {
> + compatible = "ti,tcan1042";
> + #phy-cells = <0>;
> + max-bitrate = <5000000>;
> + };
> +
> };
>
> &main_pmx0 {
> @@ -429,6 +458,20 @@ hdmi_hpd_pins_default: hdmi-hpd-default-pins {
> J784S4_IOPAD(0x000, PIN_INPUT, 7) /* (AN35) EXTINTN.GPIO0_0 */
> >;
> };
> +
> + main_mcan6_pins_default: main-mcan6-default-pins {
> + pinctrl-single,pins = <
> + J784S4_IOPAD(0x098, PIN_INPUT, 0) /* (AH36) MCAN6_RX */
> + J784S4_IOPAD(0x094, PIN_OUTPUT, 0) /* (AG35) MCAN6_TX */
> + >;
> + };
> +
> + main_mcan7_pins_default: main-mcan7-default-pins {
> + pinctrl-single,pins = <
> + J784S4_IOPAD(0x0A0, PIN_INPUT, 0) /* (AD34) MCAN7_RX */
> + J784S4_IOPAD(0x09C, PIN_OUTPUT, 0) /* (AF35) MCAN7_TX */
> + >;
> + };
> };
>
> &wkup_pmx2 {
> @@ -525,6 +568,20 @@ hdmi_pdn_pins_default: hdmi-pdn-default-pins {
> J784S4_WKUP_IOPAD(0x090, PIN_INPUT, 7) /* (H37) WKUP_GPIO0_14 */
> >;
> };
> +
> + mcu_mcan0_pins_default: mcu-mcan0-default-pins {
> + pinctrl-single,pins = <
> + J784S4_WKUP_IOPAD(0x054, PIN_INPUT, 0) /* (F38) MCU_MCAN0_RX */
> + J784S4_WKUP_IOPAD(0x050, PIN_OUTPUT, 0) /* (K33) MCU_MCAN0_TX */
> + >;
> + };
> +
> + mcu_mcan1_pins_default: mcu-mcan1-default-pins {
> + pinctrl-single,pins = <
> + J784S4_WKUP_IOPAD(0x06c, PIN_INPUT, 0) /* (K36) WKUP_GPIO0_5.MCU_MCAN1_RX */
> + J784S4_WKUP_IOPAD(0x068, PIN_OUTPUT, 0)/* (H35) WKUP_GPIO0_4.MCU_MCAN1_TX */
> + >;
> + };
> };
>
> &wkup_pmx3 {
> @@ -988,3 +1045,31 @@ dp0_out: endpoint {
> };
> };
> };
> +
> +&mcu_mcan0 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&mcu_mcan0_pins_default>;
> + phys = <&transceiver1>;
> +};
> +
> +&mcu_mcan1 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&mcu_mcan1_pins_default>;
> + phys = <&transceiver2>;
> +};
> +
> +&main_mcan6 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&main_mcan6_pins_default>;
> + phys = <&transceiver3>;
> +};
> +
> +&main_mcan7 {
> + status = "okay";
> + pinctrl-names = "default";
> + pinctrl-0 = <&main_mcan7_pins_default>;
> + phys = <&transceiver4>;
> +};
next prev parent reply other threads:[~2024-01-19 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 15:35 [PATCH 0/2] Add CAN and OSPI support for AM69-SK platform sabiya.d
2024-01-18 15:35 ` [PATCH 1/2] arm64: dts: ti: k3-am69-sk: Enable CAN interfaces for AM69 SK board sabiya.d
2024-01-19 13:20 ` Kumar, Udit [this message]
2024-01-18 15:35 ` [PATCH 2/2] arm64: dts: ti: k3-am69-sk: Add support for OSPI flash sabiya.d
2024-01-19 13:14 ` Nishanth Menon
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=5605f593-8526-46b8-9a71-4cbbf013e96e@ti.com \
--to=u-kumar1@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=sabiya.d@mistralsolutions.com \
--cc=sabiya.d@ti.com \
--cc=vigneshr@ti.com \
/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
all inboxes | Powered by JetHome®