From: Sergei Shtylyov <sergei.shtylyov@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Ulrich Hecht <uli+renesas@fpond.eu>,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: renesas: white-hawk: Add CAN-FD support
Date: Tue, 24 Jan 2023 11:20:22 +0300 [thread overview]
Message-ID: <c3816a2f-65c5-e201-35ea-0c6f5c3c3dd0@gmail.com> (raw)
In-Reply-To: <a19d0a70aacaf4c3517a226bf32ea49db3542da4.1674500205.git.geert+renesas@glider.be>
Hello!
On 1/23/23 10:06 PM, Geert Uytterhoeven wrote:
> Enable confirmed-working CAN-FD channels 0 and 1 on the White-Hawk
> development board:
> - Channel 0 uses an NXP TJR1443AT CAN transceiver, which is be enabled
Is be enabled? :-)
> through a GPIO,
> - Channels 1-7 use Microchip MCP2558FD-H/SN CAN transceivers (not
> mounted for channels 4-7), which do not need explicit description,
> but channels 2-3 do not seem to work.
>
> Inspired by a patch in the BSP by Kazuya Mizuguch.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
[...]
MBR, Sergey
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-01-24 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 19:06 [PATCH 0/2] arm64: dts: renesas: r8a779g0/white-hawk: Add CAN-FD support Geert Uytterhoeven
2023-01-23 19:06 ` [PATCH 1/2] arm64: dts: renesas: r8a779g0: Add CAN-FD node Geert Uytterhoeven
2023-01-23 19:06 ` [PATCH 2/2] arm64: dts: renesas: white-hawk: Add CAN-FD support Geert Uytterhoeven
2023-01-24 8:20 ` Sergei Shtylyov [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=c3816a2f-65c5-e201-35ea-0c6f5c3c3dd0@gmail.com \
--to=sergei.shtylyov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=uli+renesas@fpond.eu \
--cc=wsa+renesas@sang-engineering.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).