From: Marc Zyngier <maz@kernel.org>
To: "Lim, Jit Loon" <jit.loon.lim@intel.com>
Cc: "Vasut, Marek" <marex@denx.de>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
Jagan Teki <jagan@amarulasolutions.com>,
Simon <simon.k.r.goldschmidt@gmail.com>,
"Chee,\ Tien Fong" <tien.fong.chee@intel.com>,
"Hea, Kok Kiang" <kok.kiang.hea@intel.com>,
"Lokanathan, Raaj" <raaj.lokanathan@intel.com>,
"Maniyam, Dinesh" <dinesh.maniyam@intel.com>,
"Ng, Boon Khai" <boon.khai.ng@intel.com>,
"Yuslaimi, Alif Zakuan" <alif.zakuan.yuslaimi@intel.com>,
"Chong, Teik Heng" <teik.heng.chong@intel.com>,
"Zamri,
Muhammad Hazim Izzat" <muhammad.hazim.izzat.zamri@intel.com>,
"Tang, Sieu Mun" <sieu.mun.tang@intel.com>,
Ying-Chun Liu <paul.liu@linaro.org>,
"Lee, Kah\ Jing" <kah.jing.lee@intel.com>
Subject: Re: [PATCH v1] cache_v8: agilex5: Disable Dcache in the SPL
Date: Mon, 26 Jun 2023 10:32:50 +0100 [thread overview]
Message-ID: <86ilbabmbh.wl-maz@kernel.org> (raw)
In-Reply-To: <CO1PR11MB49454A0AA2FA41C811586E4FD226A@CO1PR11MB4945.namprd11.prod.outlook.com>
On Mon, 26 Jun 2023 10:00:09 +0100,
"Lim, Jit Loon" <jit.loon.lim@intel.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Marek Vasut <marex@denx.de>
> > Sent: Wednesday, 21 June, 2023 10:20 PM
> > To: Marc Zyngier <maz@kernel.org>; Lim, Jit Loon <jit.loon.lim@intel.com>
> > Cc: u-boot@lists.denx.de; Jagan Teki <jagan@amarulasolutions.com>; Simon
> > <simon.k.r.goldschmidt@gmail.com>; Chee, Tien Fong
> > <tien.fong.chee@intel.com>; Hea, Kok Kiang <kok.kiang.hea@intel.com>;
> > Lokanathan, Raaj <raaj.lokanathan@intel.com>; Maniyam, Dinesh
> > <dinesh.maniyam@intel.com>; Ng, Boon Khai <boon.khai.ng@intel.com>;
> > Yuslaimi, Alif Zakuan <alif.zakuan.yuslaimi@intel.com>; Chong, Teik Heng
> > <teik.heng.chong@intel.com>; Zamri, Muhammad Hazim Izzat
> > <muhammad.hazim.izzat.zamri@intel.com>; Tang, Sieu Mun
> > <sieu.mun.tang@intel.com>; Ying-Chun Liu <paul.liu@linaro.org>; Lee, Kah
> > Jing <kah.jing.lee@intel.com>
> > Subject: Re: [PATCH v1] cache_v8: agilex5: Disable Dcache in the SPL
> >
> > On 6/21/23 16:15, Marc Zyngier wrote:
> > > On Wed, 21 Jun 2023 15:06:51 +0100,
> > > Jit Loon Lim <jit.loon.lim@intel.com> wrote:
> > >>
> > >> From: Kah Jing Lee <kah.jing.lee@intel.com>
> > >>
> > >> Dcache feature is not enabled in SPL and enable it will cause ISR
> > >> exception. Since the Dcache is not supported in SPL, new
> > >> CONFIG_SPL_SYS_DISABLE_DCACHE_OPS is added to Kconfig to disable
> > >> Dcache in SPL.
> > >>
> > >> Signed-off-by: Kah Jing Lee <kah.jing.lee@intel.com>
> > >
> > > This is missing your own SoB.
> > >
> > > Now, I'd like to understand what you are actually trying to fix. What
> > > is this 'ISR' exception? This isn't something the architecture
> > > describes. Unless you are using CMOs on something that isn't memory or
> > > for which you don't have a mapping, this should never generate an
> > > exception.
> >
> > You beat me to it, indeed, thanks !
>
> The intention of doing this is because when we init SDMMC driver,
> the driver will call the invalidate_dcache_range. However, during
> that time, the dcache is not available in SPL yet thus causing
> exception.
Again: which exception?
There is no such thing as "the dcache isn't available". It is always
valid to invalidate it, irrespective of it being enabled or not.
My impression is that you are papering over another bug (such as
feeding non-memory to the CMOs), and are getting an SError back, which
would be entirely justified.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-06-26 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 14:06 [PATCH v1] cache_v8: agilex5: Disable Dcache in the SPL Jit Loon Lim
2023-06-21 14:15 ` Marc Zyngier
2023-06-21 14:19 ` Marek Vasut
2023-06-26 9:00 ` Lim, Jit Loon
2023-06-26 9:32 ` Marc Zyngier [this message]
2023-06-21 14:19 ` Marek Vasut
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=86ilbabmbh.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=alif.zakuan.yuslaimi@intel.com \
--cc=boon.khai.ng@intel.com \
--cc=dinesh.maniyam@intel.com \
--cc=jagan@amarulasolutions.com \
--cc=jit.loon.lim@intel.com \
--cc=kah.jing.lee@intel.com \
--cc=kok.kiang.hea@intel.com \
--cc=marex@denx.de \
--cc=muhammad.hazim.izzat.zamri@intel.com \
--cc=paul.liu@linaro.org \
--cc=raaj.lokanathan@intel.com \
--cc=sieu.mun.tang@intel.com \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=teik.heng.chong@intel.com \
--cc=tien.fong.chee@intel.com \
--cc=u-boot@lists.denx.de \
/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