From: "Kumar, Udit" <u-kumar1@ti.com>
To: Bhavya Kapoor <b-kapoor@ti.com>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <vigneshr@ti.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <conor+dt@kernel.org>,
<krzk+dt@kernel.org>, <robh@kernel.org>, <kristo@kernel.org>,
<nm@ti.com>, Jayesh Choudhary <j-choudhary@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j784s4-evm: Add support for multiple CAN instances
Date: Mon, 20 May 2024 15:59:33 +0530 [thread overview]
Message-ID: <f10425b1-8b7c-45e2-9f69-285b3ae08c45@ti.com> (raw)
In-Reply-To: <ed7d36ba-56ab-43bd-8f3a-7556a2cba684@ti.com>
Hi Bhavya
On 4/23/2024 12:35 PM, Bhavya Kapoor wrote:
> Hi Udit
>
> On 19/04/24 15:11, Kumar, Udit wrote:
>> [...]
>> Let me check if that can be done .
if you are planning to manage it through overlay then for this patch
LGTM,
>>> Regards
>>>
>>>>> Thanks.
>>>>>
>>>>> ~B-Kapoor
>>>>>
>>>>>>> CAN instance 4 in the main domain is brought on the evm through header
>>>>>>> J45. The CAN High and Low lines from the SoC are routed through a mux
>>>>>>> on the evm. The select lines need to be set for the CAN signals to
>>>>>>> reach to its transceiver on the evm. Therefore, add transceiver 3
>>>>>>> dt node to add support for this CAN instance.
>>>>>>>
>>>>>>> [..]
next prev parent reply other threads:[~2024-05-20 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 20:17 [PATCH] arm64: dts: ti: k3-j784s4-evm: Add support for multiple CAN instances Bhavya Kapoor
2024-04-15 5:12 ` Kumar, Udit
2024-04-16 9:22 ` Bhavya Kapoor
2024-04-16 9:54 ` Kumar, Udit
2024-04-19 9:19 ` Bhavya Kapoor
2024-04-19 9:41 ` Kumar, Udit
2024-04-23 7:05 ` Bhavya Kapoor
2024-05-20 10:29 ` Kumar, Udit [this message]
2024-06-14 5:15 ` Vignesh Raghavendra
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=f10425b1-8b7c-45e2-9f69-285b3ae08c45@ti.com \
--to=u-kumar1@ti.com \
--cc=b-kapoor@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@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