From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jon Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 02/11] dt-bindings: mailbox: tegra-hsp: Bump number of shared interrupts
Date: Wed, 14 May 2025 11:13:35 -0500 [thread overview]
Message-ID: <20250514161335.GA2456913-robh@kernel.org> (raw)
In-Reply-To: <20250506133118.1011777-3-thierry.reding@gmail.com>
On Tue, May 06, 2025 at 03:31:09PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> It turns out that some instances of the HSP block on Tegra264 can have
> up to 16 shared interrupts, so bump the maximum number of allowed
> interrupts.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../bindings/mailbox/nvidia,tegra186-hsp.yaml | 21 ++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml b/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml
> index 2d14fc948999..df6784a7c96a 100644
> --- a/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml
> +++ b/Documentation/devicetree/bindings/mailbox/nvidia,tegra186-hsp.yaml
> @@ -76,7 +76,7 @@ properties:
>
> interrupts:
> minItems: 1
> - maxItems: 9
> + maxItems: 17
>
> interrupt-names:
> oneOf:
> @@ -84,6 +84,25 @@ properties:
> - items:
> - const: doorbell
>
> + - items:
> + - const: doorbell
> + - pattern: "^shared[1]?[0-9]$"
shared1?[0-9] works
Though really it should be: "^shared([0-9]|1[0-5])$"
With that,
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> + - pattern: "^shared[1]?[0-9]$"
> +
> - items:
> - const: doorbell
> - pattern: "^shared[0-7]$"
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-05-14 17:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 13:31 [PATCH 00/11] Add Tegra264 support Thierry Reding
2025-05-06 13:31 ` [PATCH 01/11] dt-bindings: tegra: pmc: Add Tegra264 compatible Thierry Reding
2025-05-14 16:09 ` Rob Herring (Arm)
2025-07-07 10:20 ` Thierry Reding
2025-05-06 13:31 ` [PATCH 02/11] dt-bindings: mailbox: tegra-hsp: Bump number of shared interrupts Thierry Reding
2025-05-14 16:13 ` Rob Herring [this message]
2025-07-07 10:20 ` Thierry Reding
2025-05-06 13:31 ` [PATCH 03/11] dt-bindings: mailbox: tegra-hsp: Properly sort compatible string list Thierry Reding
2025-05-14 16:17 ` Rob Herring
2025-05-06 13:31 ` [PATCH 04/11] dt-bindings: firmware: Document Tegra264 BPMP Thierry Reding
2025-05-14 16:17 ` Rob Herring (Arm)
2025-05-06 13:31 ` [PATCH 05/11] dt-bindings: misc: Document Tegra264 APBMISC compatible Thierry Reding
2025-05-14 16:18 ` Rob Herring (Arm)
2025-05-06 13:31 ` [PATCH 06/11] soc/tegra: Enable support for Tegra264 Thierry Reding
2025-05-06 13:31 ` [PATCH 07/11] soc/tegra: pmc: Add Tegra264 support Thierry Reding
2025-05-07 11:03 ` Jon Hunter
2025-05-07 14:32 ` Thierry Reding
2025-05-06 13:31 ` [PATCH 08/11] soc/tegra: Add Tegra264 APBMISC compatible string Thierry Reding
2025-05-06 13:31 ` [PATCH 09/11] firmware: tegra: Fix IVC dependency problems Thierry Reding
2025-05-06 13:31 ` [PATCH 10/11] firmware: tegra: bpmp: Add support on Tegra264 Thierry Reding
2025-05-06 13:31 ` [PATCH 11/11] arm64: defconfig: Enable Tegra HSP and BPMP Thierry Reding
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=20250514161335.GA2456913-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.