From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Dan Sneddon <dan.sneddon@microchip.com>,
stable@vger.kernel.org,
Cristian Birsan <cristian.birsan@microchip.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: at91: sama5d2: fix CAN message ram offset and size
Date: Thu, 3 Dec 2020 20:47:53 +0100 [thread overview]
Message-ID: <160702486441.80366.4433626293403799322.b4-ty@bootlin.com> (raw)
In-Reply-To: <20201203091949.9015-1-nicolas.ferre@microchip.com>
On Thu, 3 Dec 2020 10:19:49 +0100, nicolas.ferre@microchip.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@bootlin.com>
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>
Cc: devicetree@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Dan Sneddon <dan.sneddon@microchip.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Cristian Birsan <cristian.birsan@microchip.com>
Subject: Re: [PATCH] ARM: dts: at91: sama5d2: fix CAN message ram offset and size
Date: Thu, 3 Dec 2020 20:47:53 +0100 [thread overview]
Message-ID: <160702486441.80366.4433626293403799322.b4-ty@bootlin.com> (raw)
In-Reply-To: <20201203091949.9015-1-nicolas.ferre@microchip.com>
On Thu, 3 Dec 2020 10:19:49 +0100, nicolas.ferre@microchip.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@bootlin.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-03 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 9:19 [PATCH] ARM: dts: at91: sama5d2: fix CAN message ram offset and size nicolas.ferre
2020-12-03 9:19 ` nicolas.ferre
2020-12-03 19:47 ` Alexandre Belloni [this message]
2020-12-03 19:47 ` Alexandre Belloni
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=160702486441.80366.4433626293403799322.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=cristian.birsan@microchip.com \
--cc=dan.sneddon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.