linux-kernel - Re: [PATCH] ARM: dts: at91: sama5d2: fix CAN message ram offset and size

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] [day] [month] [year] [list]

Message-Id: <160702486441.80366.4433626293403799322.b4-ty@bootlin.com>
Date:   Thu,  3 Dec 2020 20:47:53 +0100
From:   Alexandre Belloni <alexandre.belloni@...tlin.com>
To:     "nicolas.ferre@...rochip.com" <nicolas.ferre@...rochip.com>,
        Ludovic Desroches <ludovic.desroches@...rochip.com>
Cc:     Alexandre Belloni <alexandre.belloni@...tlin.com>,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Dan Sneddon <dan.sneddon@...rochip.com>,
        stable@...r.kernel.org,
        Cristian Birsan <cristian.birsan@...rochip.com>,
        devicetree@...r.kernel.org
Subject: Re: [PATCH] ARM: dts: at91: sama5d2: fix CAN message ram offset and size

On Thu, 3 Dec 2020 10:19:49 +0100, nicolas.ferre@...rochip.com wrote:
> CAN0 and CAN1 instances share the same message ram configured
> at 0x210000 on sama5d2 Linux systems.
> According to current configuration of CAN0, we need 0x1c00 bytes
> so that the CAN1 don't overlap its message ram:
> 64 x RX FIFO0 elements => 64 x 72 bytes
> 32 x TXE (TX Event FIFO) elements => 32 x 8 bytes
> 32 x TXB (TX Buffer) elements => 32 x 72 bytes
> So a total of 7168 bytes (0x1C00).
> 
> [...]

Applied, thanks!

[1/1] ARM: dts: at91: sama5d2: fix CAN message ram offset and size
      commit: bee3d7266dc3658d40c3d36074873b1299591f11

Best regards,
-- 
Alexandre Belloni <alexandre.belloni@...tlin.com>