linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	Marc Zyngier <marc.zyngier@arm.com>,
	linux-renesas-soc@vger.kernel.org,
	uclinux-h8-devel@lists.sourceforge.jp,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip: Enable compile-testing for Renesas drivers
Date: Mon, 10 Jun 2019 15:52:13 +0900	[thread overview]
Message-ID: <87o936ortu.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20190607095036.9466-1-geert+renesas@glider.be>

On Fri, 07 Jun 2019 18:50:36 +0900,
Geert Uytterhoeven wrote:
> 
> Enable compile-testing for all Renesas interrupt controller drivers,
> except for RENESAS_H8300H_INTC.  The latter relies on a function
> (ctrl_bclr()) that is not available on other architectures.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

for RENESAS_H8S_INTC
Acked-by: Yoshinori Sato <ysato@users.sourceforge.jp>

> ---
>  drivers/irqchip/Kconfig | 20 ++++++++++++++++----
>  1 file changed, 16 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
> index 2d3b5a27cc988ab6..fe509b88f99a8f10 100644
> --- a/drivers/irqchip/Kconfig
> +++ b/drivers/irqchip/Kconfig
> @@ -217,17 +217,26 @@ config RDA_INTC
>  	select IRQ_DOMAIN
>  
>  config RENESAS_INTC_IRQPIN
> -	bool
> +	bool "Renesas INTC External IRQ Pin Support" if COMPILE_TEST
>  	select IRQ_DOMAIN
> +	help
> +	  Enable support for the Renesas Interrupt Controller for external
> +	  interrupt pins, as found on SH/R-Mobile and R-Car Gen1 SoCs.
>  
>  config RENESAS_IRQC
> -	bool
> +	bool "Renesas R-Mobile APE6 and R-Car IRQC support" if COMPILE_TEST
>  	select GENERIC_IRQ_CHIP
>  	select IRQ_DOMAIN
> +	help
> +	  Enable support for the Renesas Interrupt Controller for external
> +	  devices, as found on R-Mobile APE6, R-Car Gen2, and R-Car Gen3 SoCs.
>  
>  config RENESAS_RZA1_IRQC
> -	bool
> +	bool "Renesas RZ/A1 IRQC support" if COMPILE_TEST
>  	select IRQ_DOMAIN_HIERARCHY
> +	help
> +	  Enable support for the Renesas RZ/A1 Interrupt Controller, to use up
> +	  to 8 external interrupts with configurable sense select.
>  
>  config ST_IRQCHIP
>  	bool
> @@ -303,8 +312,11 @@ config RENESAS_H8300H_INTC
>  	select IRQ_DOMAIN
>  
>  config RENESAS_H8S_INTC
> -        bool
> +	bool "Renesas H8S Interrupt Controller Support" if COMPILE_TEST
>  	select IRQ_DOMAIN
> +	help
> +	  Enable support for the Renesas H8/300 Interrupt Controller, as found
> +	  on Renesas H8S SoCs.
>  
>  config IMX_GPCV2
>  	bool
> -- 
> 2.17.1
> 

  reply	other threads:[~2019-06-10  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07  9:50 [PATCH] irqchip: Enable compile-testing for Renesas drivers Geert Uytterhoeven
2019-06-10  6:52 ` Yoshinori Sato [this message]
2019-06-10 13:50 ` Chris Brandt
2019-06-13  9:58 ` Simon Horman

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=87o936ortu.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=geert+renesas@glider.be \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=tglx@linutronix.de \
    --cc=uclinux-h8-devel@lists.sourceforge.jp \
    /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;
as well as URLs for NNTP newsgroup(s).