From: Alibek Omarov <a1ba.omarov@gmail.com>
To: mkl@pengutronix.de, linux-rockchip@lists.infradead.org
Cc: Alibek Omarov <a1ba.omarov@gmail.com>
Subject: Re: [can-next,v3,00/20] can: rockchip_canfd: add support for CAN-FD IP core found on Rockchip RK3568
Date: Mon, 2 Sep 2024 06:28:37 +0300 [thread overview]
Message-ID: <20240902032837.1513090-1-a1ba.omarov@gmail.com> (raw)
In-Reply-To: <20240830-rockchip-canfd-v3-0-d426266453fa@pengutronix.de>
>The IP core is a bit complicated and has several documented errata.
>The driver is added in several stages, first the base driver including
>the RX-path. Then several workarounds for errata and the TX-path, and
>finally features like hardware time stamping, loop-back mode and
>bus error reporting.
We've tried this on v2, with a custom board with Radxa CM3I connected and
it's even more stable than BSP driver we backported ourselves.
Tested-by: Alibek Omarov <a1ba.omarov@gmail.com>
Cheers,
Alibek.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-09-02 3:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 19:25 [PATCH can-next v3 00/20] can: rockchip_canfd: add support for CAN-FD IP core found on Rockchip RK3568 Marc Kleine-Budde
2024-08-30 19:25 ` [PATCH can-next v3 01/20] dt-bindings: can: rockchip_canfd: add rockchip CAN-FD controller Marc Kleine-Budde
2024-08-30 20:16 ` Rob Herring (Arm)
2024-08-30 19:25 ` [PATCH can-next v3 02/20] arm64: dts: rockchip: add CAN-FD controller nodes to rk3568 Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 03/20] arm64: dts: rockchip: mecsbc: add CAN0 and CAN1 interfaces Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 04/20] can: rockchip_canfd: add driver for Rockchip CAN-FD controller Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 05/20] can: rockchip_canfd: add quirks for errata workarounds Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 06/20] can: rockchip_canfd: add quirk for broken CAN-FD support Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 07/20] can: rockchip_canfd: add support for rk3568v3 Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 08/20] can: rockchip_canfd: add notes about known issues Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 09/20] can: rockchip_canfd: rkcanfd_handle_rx_int_one(): implement workaround for erratum 5: check for empty FIFO Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 10/20] can: rockchip_canfd: rkcanfd_register_done(): add warning for erratum 5 Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 11/20] can: rockchip_canfd: add TX PATH Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 12/20] can: rockchip_canfd: implement workaround for erratum 6 Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 13/20] can: rockchip_canfd: implement workaround for erratum 12 Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 14/20] can: rockchip_canfd: rkcanfd_get_berr_counter_corrected(): work around broken {RX,TX}ERRORCNT register Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 15/20] can: rockchip_canfd: add stats support for errata workarounds Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 16/20] can: rockchip_canfd: prepare to use full TX-FIFO depth Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 17/20] can: rockchip_canfd: enable full TX-FIFO depth of 2 Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 18/20] can: rockchip_canfd: add hardware timestamping support Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 19/20] can: rockchip_canfd: add support for CAN_CTRLMODE_LOOPBACK Marc Kleine-Budde
2024-08-30 19:26 ` [PATCH can-next v3 20/20] can: rockchip_canfd: add support for CAN_CTRLMODE_BERR_REPORTING Marc Kleine-Budde
2024-08-31 6:02 ` [PATCH can-next v3 00/20] can: rockchip_canfd: add support for CAN-FD IP core found on Rockchip RK3568 Krzysztof Kozlowski
2024-09-03 9:17 ` Marc Kleine-Budde
2024-09-02 3:28 ` Alibek Omarov [this message]
2024-09-02 7:01 ` [can-next,v3,00/20] " Marc Kleine-Budde
2024-09-02 7:29 ` Alibek Omarov
2024-09-02 7:40 ` Marc Kleine-Budde
2024-09-02 7:24 ` Marc Kleine-Budde
2024-09-02 7:31 ` Alibek Omarov
2024-09-02 7:41 ` Marc Kleine-Budde
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=20240902032837.1513090-1-a1ba.omarov@gmail.com \
--to=a1ba.omarov@gmail.com \
--cc=linux-rockchip@lists.infradead.org \
--cc=mkl@pengutronix.de \
/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