From: Marc Zyngier <marc.zyngier@arm.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irqchip: create a Kconfig menu for irqchip drivers
Date: Wed, 26 Jul 2017 09:04:23 +0100 [thread overview]
Message-ID: <3d59b609-aeec-9177-8849-da1fbd386191@arm.com> (raw)
In-Reply-To: <1501041791-10131-1-git-send-email-yamada.masahiro@socionext.com>
On 26/07/17 05:03, Masahiro Yamada wrote:
> Some irqchip drivers have a Kconfig prompt. When we run menuconfig
> or friends, those drivers are directly listed in the "Device Drivers"
> menu level. This does not look nice. Create a sub-system level menu.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> drivers/irqchip/Kconfig | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
> index f1fd5f44d1d4..7b66313a2952 100644
> --- a/drivers/irqchip/Kconfig
> +++ b/drivers/irqchip/Kconfig
> @@ -1,3 +1,5 @@
> +menu "IRQ chip support"
> +
> config IRQCHIP
> def_bool y
> depends on OF_IRQ
> @@ -306,3 +308,5 @@ config QCOM_IRQ_COMBINER
> help
> Say yes here to add support for the IRQ combiner devices embedded
> in Qualcomm Technologies chips.
> +
> +endmenu
>
I'm very reluctant to introduce this. IMHO, interrupt controllers are
way too low level a thing to let them be selected by the user. They
really should be selected by the platform that needs them
Do you have any example in mind where having a user-selectable interrupt
controller actually makes sense on its own?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2017-07-26 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 4:03 Masahiro Yamada
2017-07-26 8:04 ` Marc Zyngier [this message]
2017-07-26 10:18 ` Masahiro Yamada
2017-07-26 10:37 ` Marc Zyngier
2017-07-26 13:14 ` Masahiro Yamada
2017-07-26 13:50 ` Marc Zyngier
2017-07-26 14:24 ` Thomas Gleixner
2017-07-26 14:48 ` Masahiro Yamada
2017-07-26 14:27 ` Masahiro Yamada
2017-07-26 14:58 ` 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=3d59b609-aeec-9177-8849-da1fbd386191@arm.com \
--to=marc.zyngier@arm.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®