From: Lokesh Vutla <lokeshvutla@ti.com>
To: Marc Zyngier <maz@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/9] irqchip/gic-v3: Add ESPI range support
Date: Tue, 23 Jul 2019 18:20:05 +0530 [thread overview]
Message-ID: <a54dfa07-2f3b-def7-fec4-b6dab2bcd84c@ti.com> (raw)
In-Reply-To: <20190723104437.154403-5-maz@kernel.org>
On 23/07/19 4:14 PM, Marc Zyngier wrote:
> Add the required support for the ESPI range, which behave exactly like
> the SPIs of old, only with new funky INTIDs.
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> ---
> drivers/irqchip/irq-gic-v3.c | 85 ++++++++++++++++++++++++------
> include/linux/irqchip/arm-gic-v3.h | 17 +++++-
> 2 files changed, 85 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
> index 2371e0a70215..d328a8de533f 100644
> --- a/drivers/irqchip/irq-gic-v3.c
> +++ b/drivers/irqchip/irq-gic-v3.c
> @@ -51,13 +51,16 @@ struct gic_chip_data {
> u32 nr_redist_regions;
> u64 flags;
> bool has_rss;
> - unsigned int irq_nr;
> struct partition_desc *ppi_descs[16];
> };
>
> static struct gic_chip_data gic_data __read_mostly;
> static DEFINE_STATIC_KEY_TRUE(supports_deactivate_key);
>
> +#define GIC_ID_NR (1U << GICD_TYPER_ID_BITS(gic_data.rdists.gicd_typer))
> +#define GIC_LINE_NR GICD_TYPER_SPIS(gic_data.rdists.gicd_typer)
> +#define GIC_ESPI_NR GICD_TYPER_ESPIS(gic_data.rdists.gicd_typer)
> +
> /*
> * The behaviours of RPR and PMR registers differ depending on the value of
> * SCR_EL3.FIQ, and the behaviour of non-secure priority registers of the
> @@ -100,6 +103,7 @@ static DEFINE_PER_CPU(bool, has_rss);
> enum gic_intid_range {
> PPI_RANGE,
> SPI_RANGE,
> + ESPI_RANGE,
> LPI_RANGE,
> __INVALID_RANGE__
> };
> @@ -111,6 +115,8 @@ static enum gic_intid_range __get_intid_range(irq_hw_number_t hwirq)
> return PPI_RANGE;
> case 32 ... 1019:
> return SPI_RANGE;
> + case ESPI_BASE_INTID ... 8191:
as per dt documentation, shouldn't the range be
case ESPI_BASE_INTID ... 5119:
> + return ESPI_RANGE;
> case 8192 ... GENMASK(23, 0):
> return LPI_RANGE;
> default:
> @@ -141,6 +147,7 @@ static inline void __iomem *gic_dist_base(struct irq_data *d)
> return gic_data_rdist_sgi_base();
>
> case SPI_RANGE:
> + case ESPI_RANGE:
> /* SPI -> dist_base */
> return gic_data.dist_base;
>
> @@ -234,6 +241,31 @@ static u32 convert_offset_index(struct irq_data *d, u32 offset, u32 *index)
> case SPI_RANGE:
> *index = d->hwirq;
> return offset;
> + case ESPI_RANGE:
> + *index = d->hwirq - ESPI_BASE_INTID;
> + switch (offset) {
> + case GICD_ISENABLER:
> + return GICD_ISENABLERnE;
> + case GICD_ICENABLER:
> + return GICD_ICENABLERnE;
> + case GICD_ISPENDR:
> + return GICD_ISPENDRnE;
> + case GICD_ICPENDR:
> + return GICD_ICPENDRnE;
> + case GICD_ISACTIVER:
> + return GICD_ISACTIVERnE;
> + case GICD_ICACTIVER:
> + return GICD_ICACTIVERnE;
> + case GICD_IPRIORITYR:
> + return GICD_IPRIORITYRnE;
> + case GICD_ICFGR:
> + return GICD_ICFGRnE;
> + case GICD_IROUTER:
> + return GICD_IROUTERnE;
> + default:
> + break;
> + }
> + break;
> default:
> break;
> }
> @@ -316,7 +348,7 @@ static int gic_irq_set_irqchip_state(struct irq_data *d,
> {
> u32 reg;
>
> - if (d->hwirq >= gic_data.irq_nr) /* PPI/SPI only */
> + if (d->hwirq >= 8192) /* PPI/SPI only */
> return -EINVAL;
>
> switch (which) {
> @@ -343,7 +375,7 @@ static int gic_irq_set_irqchip_state(struct irq_data *d,
> static int gic_irq_get_irqchip_state(struct irq_data *d,
> enum irqchip_irq_state which, bool *val)
> {
> - if (d->hwirq >= gic_data.irq_nr) /* PPI/SPI only */
> + if (d->hwirq >= 8192) /* PPI/SPI only */
> return -EINVAL;
>
> switch (which) {
> @@ -567,7 +599,12 @@ static asmlinkage void __exception_irq_entry gic_handle_irq(struct pt_regs *regs
> gic_arch_enable_irqs();
> }
>
> - if (likely(irqnr > 15 && irqnr < 1020) || irqnr >= 8192) {
> + /* Check for special IDs first */
> + if ((irqnr >= 1020 && irqnr <= 1023))
> + return;
May be I am missing something here, what is special about these 4 interrupts? or
you meant to check for reserved range here?
Thanks and regards,
Lokesh
next prev parent reply other threads:[~2019-07-23 12:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 10:44 [PATCH 0/9] irqchip/gic-v3: Add support for GICv3.1 extended PPI/SPI ranges Marc Zyngier
2019-07-23 10:44 ` [PATCH 1/9] irqchip/gic: Rework gic_configure_irq to take the full ICFGR base Marc Zyngier
2019-07-23 10:44 ` [PATCH 2/9] irqchip/gic-v3: Add INTID range and convertion primitives Marc Zyngier
2019-07-23 10:44 ` [PATCH 3/9] dt-bindings: interrupt-controller: arm,gic-v3: Describe ESPI range support Marc Zyngier
2019-07-23 12:59 ` [PATCH 3/9] dt-bindings: interrupt-controller: arm, gic-v3: " Lokesh Vutla
2019-07-23 13:15 ` Marc Zyngier
2019-07-23 13:35 ` Lokesh Vutla
2019-07-23 10:44 ` [PATCH 4/9] irqchip/gic-v3: Add " Marc Zyngier
2019-07-23 12:50 ` Lokesh Vutla [this message]
2019-07-23 13:04 ` Marc Zyngier
2019-07-23 10:44 ` [PATCH 5/9] irqchip/gic: Prepare for more than 16 PPIs Marc Zyngier
2019-07-23 10:44 ` [PATCH 6/9] irqchip/gic-v3: Dynamically allocate PPI NMI refcounts Marc Zyngier
2019-07-23 10:44 ` [PATCH 7/9] irqchip/gic-v3: Dynamically allocate PPI partition descriptors Marc Zyngier
2019-07-23 10:44 ` [PATCH 8/9] dt-bindings: interrupt-controller: arm,gic-v3: Describe EPPI range support Marc Zyngier
2019-07-23 10:44 ` [PATCH 9/9] irqchip/gic-v3: Add " Marc Zyngier
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=a54dfa07-2f3b-def7-fec4-b6dab2bcd84c@ti.com \
--to=lokeshvutla@ti.com \
--cc=jason@lakedaemon.net \
--cc=julien.thierry.kdev@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®