public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Frank Li <Frank.li@nxp.com>, Fabio Estevam <festevam@gmail.com>,
	peng.fan@nxp.com, peng.fan@oss.nxp.com,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	imx@lists.linux.dev,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: mx93: No cache hierachy definitions for ARM cores
Date: Wed, 24 Jul 2024 17:55:29 +0200	[thread overview]
Message-ID: <8c4e26f5-cf28-44f6-8b76-c80832cfe1a2@gmx.net> (raw)
In-Reply-To: <ZqEQ4vOVvMIazIKc@bogus>

Am 24.07.24 um 16:34 schrieb Sudeep Holla:
> On Wed, Jul 24, 2024 at 11:48:13AM +0200, Stefan Wahren wrote:
>> Hi Frank,
>>
>> Am 19.07.24 um 16:52 schrieb Frank Li:
>>> On Thu, Jul 18, 2024 at 11:38:20PM -0300, Fabio Estevam wrote:
>>>> On Wed, Jul 17, 2024 at 2:49 PM Stefan Wahren <wahrenst@gmx.net> wrote:
>>>>> Hi,
>>>>> today i noticed that imx93.dtsi lacks the cache definitions for the
>>>>> Cortex-A55 cores:
>>>>>
>>>>> cacheinfo: Unable to detect cache hierarchy for CPU 0
>>>>>
>>>>> Maybe someone with more insight can add this to the imx93.dtsi file.
>>>> Frank, can you help?
>>> Peng:
>>> 	Some informatin missed at public RM. Can you help this? I found
>>> it also missed in internal tree.
>> does the official ARM documentation [1] provide the missing information?
>>
>> [1] - https://developer.arm.com/documentation/101051/0101
> I assume you meant [2] instead of [1], as Cortex A55 and M55 are different.
Sorry, you are absolutely right.
>
> --
> Regards,
> Sudeep
>
> [2] https://developer.arm.com/documentation/100442/0200/



  reply	other threads:[~2024-07-24 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-17 17:49 mx93: No cache hierachy definitions for ARM cores Stefan Wahren
2024-07-19  2:38 ` Fabio Estevam
2024-07-19  4:40   ` Stefan Wahren
2024-07-19 14:52   ` Frank Li
2024-07-24  9:48     ` Stefan Wahren
2024-07-24 14:34       ` Sudeep Holla
2024-07-24 15:55         ` Stefan Wahren [this message]
2024-08-01  2:52           ` Peng Fan

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=8c4e26f5-cf28-44f6-8b76-c80832cfe1a2@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=Frank.li@nxp.com \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=sudeep.holla@arm.com \
    /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