mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Robert Marko <robert.marko@sartura.hr>,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	lars.povlsen@microchip.com, Steen.Hegelund@microchip.com,
	daniel.machon@microchip.com, UNGLinuxDriver@microchip.com,
	arnd@arndb.de, alexandre.belloni@bootlin.com,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Conor Dooley <conor@kernel.org>
Cc: luka.perkov@sartura.hr
Subject: Re: [PATCH v2 3/3] arm64: dts: microchip: sparx5: add missing L1/L2 cache information
Date: Wed, 17 May 2023 14:26:38 +0200	[thread overview]
Message-ID: <6c920568-4407-29d9-d7d9-3fd5c8d6e30b@linaro.org> (raw)
In-Reply-To: <20230221105039.316819-3-robert.marko@sartura.hr>

On 21/02/2023 11:50, Robert Marko wrote:
> Currently, when booting on SparX-5 you will get the following error:
> [    0.050132] Early cacheinfo failed, ret = -22
> 
> This is due to L2 cache node missing cache-level property to indicate its
> level, so populate it to let the kernel know its L2 cache.
> 
> However, that alone is enough to get rid of the error, but then the
> following warnings appear:
> [    0.050162] cacheinfo: Unable to detect cache hierarchy for CPU 0
> [    0.093256] cacheinfo: Unable to detect cache hierarchy for CPU 1
> 

This did not apply, skipped.

Best regards,
Krzysztof


  reply	other threads:[~2023-05-17 12:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-21 10:50 [PATCH v2 1/3] arm64: dts: microchip: sparx5: do not use PSCI on reference boards Robert Marko
2023-02-21 10:50 ` [PATCH v2 2/3] arm64: dts: microchip: sparx5: correct CPU address-cells Robert Marko
2023-05-17 12:26   ` Krzysztof Kozlowski
2023-02-21 10:50 ` [PATCH v2 3/3] arm64: dts: microchip: sparx5: add missing L1/L2 cache information Robert Marko
2023-05-17 12:26   ` Krzysztof Kozlowski [this message]
2023-02-21 13:59 ` [PATCH v2 1/3] arm64: dts: microchip: sparx5: do not use PSCI on reference boards Steen Hegelund
2023-05-17 12:25 ` Krzysztof Kozlowski

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=6c920568-4407-29d9-d7d9-3fd5c8d6e30b@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=Steen.Hegelund@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=conor@kernel.org \
    --cc=daniel.machon@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars.povlsen@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luka.perkov@sartura.hr \
    --cc=robert.marko@sartura.hr \
    --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

all inboxes | Powered by JetHome®