From: Conor Dooley <conor@kernel.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Paul Burton <paulburton@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Serge Semin <fancer.lancer@gmail.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 5/6] dt-bindings: mips: Document mti,mips-cm
Date: Wed, 12 Jun 2024 18:01:34 +0100 [thread overview]
Message-ID: <20240612-napping-feel-c12d52787c6d@spud> (raw)
In-Reply-To: <20240612-cm_probe-v2-5-a5b55440563c@flygoat.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Wed, Jun 12, 2024 at 11:08:57AM +0100, Jiaxun Yang wrote:
> Add devicetree binding documentation for MIPS Coherence Manager.
>
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
> v2:
> - Better wording for register desc
> - cm -> coherency-manager
> - schema matches compatible
> ---
> .../devicetree/bindings/mips/mti,mips-cm.yaml | 38 ++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml b/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
> new file mode 100644
> index 000000000000..9f500804737d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mips/mti,mips-cm.yaml
> @@ -0,0 +1,38 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mips/mti,mips-cm.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MIPS Coherence Manager
> +
> +description: |
The | is not needed here.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-12 17:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 10:08 [PATCH v2 0/6] MIPS: cm: Probe GCR address from devicetree Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 1/6] MIPS: generic: Do __dt_setup_arch in prom_init Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 2/6] MIPS: malta: Move SMP initialisation to device_tree_init Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 3/6] MIPS: cm: Prefix probe functions with __init Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 4/6] MIPS: Move mips_cm_probe after prom_init Jiaxun Yang
2024-06-12 10:08 ` [PATCH v2 5/6] dt-bindings: mips: Document mti,mips-cm Jiaxun Yang
2024-06-12 17:01 ` Conor Dooley [this message]
2024-08-06 19:56 ` Serge Semin
2024-06-12 10:08 ` [PATCH v2 6/6] MIPS: cm: Probe GCR address from DeviceTree Jiaxun Yang
2024-09-10 12:36 ` Serge Semin
2024-09-10 19:23 ` Jiaxun Yang
2024-09-10 20:07 ` Serge Semin
2024-09-10 20:48 ` Jiaxun Yang
2024-09-10 22:16 ` Serge Semin
2024-07-06 5:13 ` [PATCH v2 0/6] MIPS: cm: Probe GCR address from devicetree Jiaxun Yang
2024-07-20 7:30 ` Jiaxun Yang
2024-08-06 19:49 ` Serge Semin
2024-09-09 13:32 ` Thomas Bogendoerfer
2024-09-10 8:06 ` Serge Semin
2024-09-10 12:20 ` Serge Semin
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=20240612-napping-feel-c12d52787c6d@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@kernel.org \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.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;
as well as URLs for NNTP newsgroup(s).