From: Rob Herring <robh@kernel.org>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: jassisinghbrar@gmail.com, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, sudeep.holla@arm.com,
conor+dt@kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org, jonathan.cameron@huawei.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/2] dt-bindings: mailbox: arm,mhuv3: Add bindings
Date: Tue, 16 Apr 2024 08:22:43 -0500 [thread overview]
Message-ID: <171327375957.2147382.5296406072245589287.robh@kernel.org> (raw)
In-Reply-To: <20240412192801.554464-2-cristian.marussi@arm.com>
On Fri, 12 Apr 2024 20:28:00 +0100, Cristian Marussi wrote:
> Add bindings for the ARM MHUv3 Mailbox controller.
>
> Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> ---
> v3 -> v4
> - using ARM GIC defines in example
> - defined MHUv3 Extensions types in dt-bindings/arm/mhuv3-dt.h
> v2 -> v3
> - fixed spurious tabs in dt_binding_check
> v1 -> v2
> - clarified extension descriptions around configurability and discoverability
> - removed unused labels from the example
> - using pattern properties to define interrupt-names
> - bumped interrupt maxItems to 74 (allowing uo to 8 channels per extension)
> ---
> .../bindings/mailbox/arm,mhuv3.yaml | 224 ++++++++++++++++++
> include/dt-bindings/arm/mhuv3-dt.h | 13 +
> 2 files changed, 237 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mailbox/arm,mhuv3.yaml
> create mode 100644 include/dt-bindings/arm/mhuv3-dt.h
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2024-04-16 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 19:27 [PATCH v4 0/2] Add initial ARM MHUv3 mailbox support Cristian Marussi
2024-04-12 19:28 ` [PATCH v4 1/2] dt-bindings: mailbox: arm,mhuv3: Add bindings Cristian Marussi
2024-04-16 13:22 ` Rob Herring [this message]
2024-04-12 19:28 ` [PATCH v4 2/2] mailbox: arm_mhuv3: Add driver Cristian Marussi
2024-04-15 13:56 ` kernel test robot
2024-04-15 14:14 ` Cristian Marussi
2024-04-15 16:13 ` kernel test robot
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=171327375957.2147382.5296406072245589287.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=jonathan.cameron@huawei.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®