From: Francesco Dolcini <francesco@dolcini.it>
To: Frank Li <frank.li@nxp.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
"Ivan T. Ivanov" <iivanov@suse.de>,
Jason Liu <jason.hui.liu@nxp.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Aisheng Dong <aisheng.dong@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [EXT] Re: [PATCH v2] arm64: errata: Add NXP iMX8QM workaround for A53 Cache coherency issue
Date: Thu, 11 Dec 2025 11:43:32 +0100 [thread overview]
Message-ID: <20251211104332.GA9632@francesco-nb> (raw)
In-Reply-To: <DU2PR04MB8951DEE7CB2D29D7E83CE03388A0A@DU2PR04MB8951.eurprd04.prod.outlook.com>
Hello Frank,
On Wed, Dec 10, 2025 at 02:55:12PM +0000, Frank Li wrote:
> > On Thu, Apr 20, 2023 at 02:29:52PM +0300, Ivan T. Ivanov wrote:
> > > According to NXP errata document[1] i.MX8QuadMax SoC suffers from
> > > serious cache coherence issue. It was also mentioned in initial
> > > support[2] for imx8qm mek machine.
> >
> > Ivan, from what I can see this patch was never merged and there was not any
> > follow-up on this. What's the status? Are you planning to work on it?
> >
> > Frank, it would be nice to have this issue sorted out in mainline, any
> > chance that NXP can help move this forward?
>
> Jason worked the original solution, what's difficult of upstream accept the
> Solution?
Was it ever sent to mainline for inclusion?
Can NXP help on having a workaround for this errata implemented in
mainline Linux, whatever is the actual final technical solution?
Francesco
prev parent reply other threads:[~2025-12-11 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 11:29 [PATCH v2] arm64: errata: Add NXP iMX8QM workaround for A53 Cache coherency issue Ivan T. Ivanov
2023-05-18 11:59 ` Ivan T. Ivanov
2023-06-02 10:34 ` Will Deacon
2023-06-08 13:39 ` Ivan T. Ivanov
2023-06-08 14:16 ` Mark Rutland
2023-06-08 15:05 ` Ivan T. Ivanov
2023-06-08 15:32 ` Mark Rutland
2023-06-08 18:22 ` Ivan T. Ivanov
[not found] ` <ZIbmNNc6/pfYG92D@FVFF77S0Q05N>
[not found] ` <y5lcrztej6th7z3eoihiiazwwlidyhi3t2tkdjrmgcghqwt6bs@dzxxpmwfynj6>
2023-06-26 12:15 ` Will Deacon
2023-07-13 14:29 ` Ivan T. Ivanov
2025-12-10 7:45 ` Francesco Dolcini
2025-12-10 11:39 ` Ivan T. Ivanov
2025-12-10 14:55 ` [EXT] " Frank Li
2025-12-11 10:43 ` Francesco Dolcini [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=20251211104332.GA9632@francesco-nb \
--to=francesco@dolcini.it \
--cc=aisheng.dong@nxp.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=frank.li@nxp.com \
--cc=iivanov@suse.de \
--cc=jason.hui.liu@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=shawnguo@kernel.org \
--cc=will@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).