netdev - Re: [PATCH v4 0/4] can: rcar_canfd: Add support for V3U flavor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 10 Mar 2022 09:25:45 +0100
From:   Marc Kleine-Budde <mkl@...gutronix.de>
To:     Ulrich Hecht <uli+renesas@...nd.eu>
Cc:     linux-renesas-soc@...r.kernel.org, netdev@...r.kernel.org,
        davem@...emloft.net, linux-can@...r.kernel.org,
        prabhakar.mahadev-lad.rj@...renesas.com,
        biju.das.jz@...renesas.com, wsa@...nel.org,
        yoshihiro.shimoda.uh@...esas.com, wg@...ndegger.com,
        kuba@...nel.org, mailhol.vincent@...adoo.fr,
        socketcan@...tkopp.net, geert@...ux-m68k.org,
        kieran.bingham@...asonboard.com, horms@...ge.net.au
Subject: Re: [PATCH v4 0/4] can: rcar_canfd: Add support for V3U flavor

On 09.03.2022 17:26:05, Ulrich Hecht wrote:
> This adds CANFD support for V3U (R8A779A0) SoCs. The V3U's IP supports up
> to eight channels and has some other minor differences to the Gen3 variety:
> 
> - changes to some register offsets and layouts
> - absence of "classic CAN" registers, both modes are handled through the
>   CANFD register set
> 
> This patch set tries to accommodate these changes in a minimally intrusive
> way.
> 
> This revision tries to address the remaining style issues raised by
> reviewers. Thanks to Vincent, Marc and Simon for their reviews and
> suggestions.
> 
> It has been successfully tested remotely on a V3U Falcon board, but only
> with channels 0 and 1. We were not able to get higher channels to work in
> both directions yet. It is not currently clear if this is an issue with the
> driver, the board or the silicon, but the BSP vendor driver only works with
> channels 0 and 1 as well, so my bet is on one of the latter. For this
> reason, this series only enables known-working channels 0 and 1 on Falcon.

Should I take the whole series via linux-can/next?

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)