From: Rob Herring <robh@kernel.org>
To: Nikunj Kela <quic_nkela@quicinc.com>
Cc: krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@quicinc.com, quic_psodagud@quicinc.com
Subject: Re: [PATCH v3] dt-bindings: arm: GIC: add ESPI and EPPI specifiers
Date: Mon, 9 Sep 2024 10:54:31 -0500 [thread overview]
Message-ID: <20240909155431.GA207498-robh@kernel.org> (raw)
In-Reply-To: <20240908010205.863701-1-quic_nkela@quicinc.com>
On Sat, Sep 07, 2024 at 06:02:05PM -0700, Nikunj Kela wrote:
> Add interrupt specifier for extended SPI and extended PPI interrupts.
Are extended SPI and PPI a GIC defined thing? What version of GIC?
Yes, I think I already asked these questions, but I only remember what
you put into the commit message.
>
> Qualcomm SA8255p platform uses extended SPI for SCMI 'a2p' doorbells.
>
> Signed-off-by: Nikunj Kela <quic_nkela@quicinc.com>
> ---
>
> Changes in v3:
> - Removed the patch from original series[1]
>
> Changes in v2:
> - Modified subject line and description
> - Added EPPI macro
>
> [1]: https://lore.kernel.org/all/20240903220240.2594102-1-quic_nkela@quicinc.com/
> ---
> include/dt-bindings/interrupt-controller/arm-gic.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/dt-bindings/interrupt-controller/arm-gic.h b/include/dt-bindings/interrupt-controller/arm-gic.h
> index 35b6f69b7db6..887f53363e8a 100644
> --- a/include/dt-bindings/interrupt-controller/arm-gic.h
> +++ b/include/dt-bindings/interrupt-controller/arm-gic.h
> @@ -12,6 +12,8 @@
>
> #define GIC_SPI 0
> #define GIC_PPI 1
> +#define GIC_ESPI 2
> +#define GIC_EPPI 3
>
> /*
> * Interrupt specifier cell 2.
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-09-09 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 1:02 [PATCH v3] dt-bindings: arm: GIC: add ESPI and EPPI specifiers Nikunj Kela
2024-09-09 15:54 ` Rob Herring [this message]
2024-09-09 16:27 ` Nikunj Kela
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=20240909155431.GA207498-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_nkela@quicinc.com \
--cc=quic_psodagud@quicinc.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.