Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: Michael Turquette <mturquette@baylibre.com>,
	 Stephen Boyd <sboyd@kernel.org>,  Rob Herring <robh@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Thomas Gleixner <tglx@kernel.org>,
	 Olivia Mackall <olivia@selenic.com>,
	 Herbert Xu <herbert@gondor.apana.org.au>,
	 Jayesh Choudhary <j-choudhary@ti.com>,
	"David S. Miller" <davem@davemloft.net>,
	 Christian Marangi <ansuelsmth@gmail.com>,
	 Antoine Tenart <atenart@kernel.org>,
	 Geert Uytterhoeven <geert+renesas@glider.be>,
	 Magnus Damm <magnus.damm@gmail.com>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Pascal EBERHARD <pascal.eberhard@se.com>,
	 Wolfram Sang <wsa+renesas@sang-engineering.com>,
	 linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	 linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 02/16] dt-bindings: interrupt-controller: Describe EIP-201 AIC
Date: Fri, 10 Jul 2026 11:48:38 +0200	[thread overview]
Message-ID: <87y0fjgop5.fsf@bootlin.com> (raw)
In-Reply-To: <444b4349-3873-4da6-aadd-3605e738ad0d@wp.pl> (Aleksander Jan Bajkowski's message of "Thu, 16 Apr 2026 20:04:03 +0200")

Hello,

>> --- /dev/null
>> +++ b/include/dt-bindings/interrupt-controller/inside-secure,safexcel-eip201.h
>> @@ -0,0 +1,14 @@
>> +/* SPDX-License-Identifier: (GPL-2.0-only OR MIT) */
>> +
>> +#ifndef _DT_BINDINGS_IRQ_SAFEXCEL_EIP201_AIC_H
>> +#define _DT_BINDINGS_IRQ_SAFEXCEL_EIP201_AIC_H
>> +
>> +#define AIC_PKA_INT0 0
>> +#define AIC_PKA_INT1 1
>> +#define AIC_PKA_INT2 2
>> +#define AIC_TRNG_INT 3
>> +#define AIC_RESERVED 4
>> +#define AIC_SL_ERR_INT  5
>> +#define AIC_PROTECTION_INT 6
>> +
>> +#endif
>
> This interrupt mapping is specific to the EIP-150. The EIP-201 is also
> integrated
> into other accelerators, such as the EIP-97, EIP-196, and EIP-197, and the
> interrupt mapping is likely different there. Maybe it would be better to use
> eip150 name instead of eip201?

I was about to rename the file (and the ifndef/define section), but in
the end I feel like it does not actually make sense to do that, because
it would require to include one header per container in the
driver. Instead, I propose another way: let's keep the file name as-is,
but mention with a comment above the definitions that these are specific
to the EIP-150 implementation. This way, if someone want to reuse the
controller for another integration, they can just add their own
interrupt names/numbers below, with another comment stating the name of
the container they apply to.

For future people who would like to extend this driver to another
container: mind that there is currently a list of "unused" interrupts in
the v2 of the driver (in the generic chip structure). This list may
simply go away if one needs one of the three interrupts currently
listed.

Thanks,
Miquèl

  parent reply	other threads:[~2026-07-10  9:48 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27 20:09 [PATCH 00/16] Add support for Inside-Secure EIP-150 crypto block Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 01/16] dt-bindings: clock: Introduce nexus nodes Miquel Raynal (Schneider Electric)
2026-04-07 19:29   ` Rob Herring
2026-07-10  9:35     ` Miquel Raynal
2026-04-12  1:16   ` Stephen Boyd
2026-07-10  9:33     ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 02/16] dt-bindings: interrupt-controller: Describe EIP-201 AIC Miquel Raynal (Schneider Electric)
2026-04-07 19:45   ` Rob Herring (Arm)
2026-04-16 18:04   ` Aleksander Jan Bajkowski
2026-04-17  7:50     ` Miquel Raynal
2026-04-17 15:22       ` Aleksander Jan Bajkowski
2026-07-10  9:48     ` Miquel Raynal [this message]
2026-03-27 20:09 ` [PATCH 03/16] dt-bindings: rng: Rename the title of the EIP-76 file Miquel Raynal (Schneider Electric)
2026-04-07 19:47   ` Rob Herring (Arm)
2026-03-27 20:09 ` [PATCH 04/16] dt-bindings: crypto: eip28: Describe EIP-28 PKA Miquel Raynal (Schneider Electric)
2026-04-07 19:49   ` Rob Herring
2026-03-27 20:09 ` [PATCH 05/16] dt-bindings: bus: eip150: Describe the EIP-150 container node Miquel Raynal (Schneider Electric)
2026-04-07 19:44   ` Rob Herring
2026-07-10 12:59     ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 06/16] clk: tests: Add clk_parse_clkspec() Kunit testing Miquel Raynal (Schneider Electric)
2026-03-30 14:48   ` Brian Masney
2026-04-01  8:59     ` Miquel Raynal
2026-04-01 13:55       ` Brian Masney
2026-07-10  9:13         ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 07/16] clk: tests: Add Kunit testing for of_clk_get_parent_name() Miquel Raynal (Schneider Electric)
2026-04-12  1:29   ` Stephen Boyd
2026-07-10 12:09     ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 08/16] clk: Improve a couple of comments Miquel Raynal (Schneider Electric)
2026-03-30 14:50   ` Brian Masney
2026-03-27 20:09 ` [PATCH 09/16] clk: Use the generic OF phandle parsing in only one place Miquel Raynal (Schneider Electric)
2026-03-30 15:01   ` Brian Masney
2026-04-01  8:49     ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 10/16] clk: Add support for clock nexus dt bindings Miquel Raynal (Schneider Electric)
2026-03-30 15:09   ` Brian Masney
2026-03-30 15:16   ` Brian Masney
2026-04-01  8:47     ` Miquel Raynal
2026-04-01 14:04       ` Brian Masney
2026-04-12  1:12       ` Stephen Boyd
2026-07-10 11:44         ` Miquel Raynal
2026-05-13 15:05   ` Frank Li
2026-03-27 20:09 ` [PATCH 11/16] clk: tests: Add Kunit testing for nexus nodes Miquel Raynal (Schneider Electric)
2026-04-12  1:40   ` Stephen Boyd
2026-07-10 10:35     ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 12/16] irqchip/eip201-aic: Add support for Safexcel EIP-201 AIC Miquel Raynal (Schneider Electric)
2026-03-28 13:10   ` Thomas Gleixner
2026-04-01  9:10     ` Miquel Raynal
2026-04-08  8:05   ` Geert Uytterhoeven
2026-07-08 12:59     ` Miquel Raynal
2026-03-27 20:09 ` [PATCH 13/16] hwrng: omap: Enable on Renesas RZ/N1D Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 14/16] crypto: Group Inside-Secure IPs together and align the titles Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 15/16] crypto: eip28: Add support for SafeXcel EIP-28 Public Key Accelerator Miquel Raynal (Schneider Electric)
2026-03-27 20:09 ` [PATCH 16/16] ARM: dts: renesas: r9a06g032: Describe the EIP-150 block Miquel Raynal (Schneider Electric)
2026-04-07 19:33   ` Rob Herring
2026-07-08 12:55     ` Miquel Raynal
2026-03-30 13:33 ` [PATCH 00/16] Add support for Inside-Secure EIP-150 crypto block Geert Uytterhoeven
2026-04-01  9:02   ` Miquel Raynal

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=87y0fjgop5.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=ansuelsmth@gmail.com \
    --cc=atenart@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=herbert@gondor.apana.org.au \
    --cc=j-choudhary@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=olek2@wp.pl \
    --cc=olivia@selenic.com \
    --cc=pascal.eberhard@se.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wsa+renesas@sang-engineering.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