From: <Tudor.Ambarus@microchip.com>
To: <Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>, <robh+dt@kernel.org>,
<bbrezillon@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: at91: sama5d2: Fix PMERRLOC resource size
Date: Tue, 11 Jan 2022 09:36:10 +0000 [thread overview]
Message-ID: <1b302157-c30f-4aa5-c798-d1bb7990258e@microchip.com> (raw)
In-Reply-To: <Yd1KZC+dg5GHruju@ada.ifak-system.com>
On 1/11/22 11:14 AM, Alexander Dahl wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hello,
Hi!
>
> Am Tue, Jan 11, 2022 at 10:09:33AM +0200 schrieb Tudor Ambarus:
>> PMERRLOC resource size has been shrunk to 0x100,
>
> What do mean with "has been shrunk"? It was introduced like this for
> sama5d2, sama5d3, and sama5d4 in the first place with d9c41bf30cf8c.
I meant has been shrunk until now.
I will reword this for better clarity, maybe s/"has been shrunk"/"was set".
>
> FWIW, I had a look in the sama5d2, sama5d3 and sama5d4 series
> datasheets, and it seems sama5d2 differs from the two others here.
Indeed, this patch is for sama5d2 only. sama5d3 and sama5d4 PMERRLOC
registers fit in the 0x100 size, there's no need to update them.
>
>> which resulted in
>> HSMC_ERRLOCx register being truncated to offset x = 21, causing
>> error correction to fail if more than 22 bit errors where 24 or
>> 32 bit error correction was supported.
>>
>> Fixes: d9c41bf30cf8 ("ARM: dts: at91: Declare EBI/NAND controllers")
>
> This landed in 4.13. Is this fix needed for stable then? That would be
> 4.14, 4.19, 5.4, 5.10, and 5.15, right? Or is this covered by the
> fixes tag already?
Maybe indirectly. But best would be to add the following line according to
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Cc: <stable@vger.kernel.org> # 4.14.x
Will add it. Cheers,
ta
prev parent reply other threads:[~2022-01-11 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 8:09 [PATCH] ARM: dts: at91: sama5d2: Fix PMERRLOC resource size Tudor Ambarus
2022-01-11 9:14 ` Alexander Dahl
2022-01-11 9:36 ` Tudor.Ambarus [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=1b302157-c30f-4aa5-c798-d1bb7990258e@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 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).