From: Rob Herring <robh@kernel.org>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: "Aleksandar Rikalo" <arikalo@gmail.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Vladimir Kondratiev" <vladimir.kondratiev@mobileye.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Tawfik Bayouk" <tawfik.bayouk@mobileye.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] dt-bindings: mips: mips-cm: Add property for broken HCI information
Date: Tue, 19 Nov 2024 10:28:21 -0600 [thread overview]
Message-ID: <20241119162821.GA1767692-robh@kernel.org> (raw)
In-Reply-To: <20241115-cluster-hci-broken-v1-2-00636800611d@bootlin.com>
On Fri, Nov 15, 2024 at 04:29:55PM +0100, Gregory CLEMENT wrote:
> Some CM3.5 reports show that Hardware Cache Initialization is
> complete, but in reality it's not the case. They also incorrectly
> indicate that Hardware Cache Initialization is supported. This
> optional property allows warning about this broken feature that cannot
> be detected at runtime.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> ---
> Documentation/devicetree/bindings/mips/mti,mips-cm.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml b/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
> index 03a5ba5624a429c428ee2afca73b3e29127e02f9..eab31a1022c8cbdee86081110516579ebe99e640 100644
> --- a/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
> +++ b/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
> @@ -23,6 +23,12 @@ properties:
> block. It is conventionally decided by the system integrator.
> maxItems: 1
>
> + cm3-l2-config-hci-broken:
> + type: boolean
> + description:
> + If present, indicates that the HCI (Hardware Cache Initialization)
> + information for the L2 cache in multi-cluster configuration is broken.
> +
This should be implied by a specific compatible.
> required:
> - compatible
>
>
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-11-19 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 15:29 [PATCH 0/5] MIPS: Allow using multi-cluster with a broken HCI Gregory CLEMENT
2024-11-15 15:29 ` [PATCH 1/5] dt-bindings: mips: Document mti,mips-cm Gregory CLEMENT
2024-11-15 18:13 ` Conor Dooley
2024-11-19 16:26 ` Rob Herring
2024-11-20 16:47 ` Gregory CLEMENT
2024-11-15 15:29 ` [PATCH 2/5] dt-bindings: mips: mips-cm: Add property for broken HCI information Gregory CLEMENT
2024-11-19 16:28 ` Rob Herring [this message]
2024-11-15 15:29 ` [PATCH 3/5] MIPS: cm: Detect CM quirks from device tree Gregory CLEMENT
2024-11-15 15:29 ` [PATCH 4/5] MIPS: CPS: Support broken HCI for multicluster Gregory CLEMENT
2024-11-15 15:29 ` [PATCH 5/5] MIPS: mobileye: dts: eyeq6h: Enable cluster support Gregory CLEMENT
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=20241119162821.GA1767692-robh@kernel.org \
--to=robh@kernel.org \
--cc=arikalo@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=jiaxun.yang@flygoat.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=tawfik.bayouk@mobileye.com \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tsbogend@alpha.franken.de \
--cc=vladimir.kondratiev@mobileye.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;
as well as URLs for NNTP newsgroup(s).