From: "Kumar, Udit" <u-kumar1@ti.com>
To: "Kapoor, Bhavya" <b-kapoor@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Menon, Nishanth" <nm@ti.com>,
"Raghavendra, Vignesh" <vigneshr@ti.com>,
"kristo@kernel.org" <kristo@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>, "Mendez, Judith" <jm@ti.com>
Subject: RE: [PATCH v3] arm64: dts: ti: k3-j721s2: Add support for CAN instances 3 and 5 in main domain
Date: Tue, 20 Jun 2023 07:37:52 +0000 [thread overview]
Message-ID: <7699edaaa4be4b08bede1b1913ac1020@ti.com> (raw)
In-Reply-To: <20230526165505.45172-1-b-kapoor@ti.com>
Hi Bhavya,
> [...]
>+ mux0: mux-controller0 {
>+ compatible = "gpio-mux";
>+ #mux-state-cells = <1>;
>+ mux-gpios = <&exp_som 1 GPIO_ACTIVE_HIGH>;
>+ };
>+
>+ mux1: mux-controller1 {
>+ compatible = "gpio-mux";
>+ #mux-state-cells = <1>;
>+ mux-gpios = <&exp_som 2 GPIO_ACTIVE_HIGH>;
>+ };
>+
/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dtb: mux-controller0: $nodename:0: 'mux-controller0' does not match '^mux-controller(@.*|-[0-9a-f]+)?$'
Documentation/devicetree/bindings/mux/mux-controller.yaml
arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dtb: mux-controller1: $nodename:0: 'mux-controller1' does not match '^mux-controller(@.*|-[0-9a-f]+)?$'
Please fix above dtbs_check warning
For rest
Reviewed-by: Udit Kumar <u-kumar1@ti.com>
> transceiver0: can-phy0 {
> /* standby pin has been grounded by default */
> compatible = "ti,tcan1042";
>--
>2.39.2
prev parent reply other threads:[~2023-06-20 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 16:55 [PATCH v3] arm64: dts: ti: k3-j721s2: Add support for CAN instances 3 and 5 in main domain Bhavya Kapoor
2023-06-20 7:37 ` Kumar, Udit [this message]
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=7699edaaa4be4b08bede1b1913ac1020@ti.com \
--to=u-kumar1@ti.com \
--cc=b-kapoor@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jm@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@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=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;
as well as URLs for NNTP newsgroup(s).