From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add Broadcom Set Top Box Kconfig entry point
Date: Tue, 12 Jul 2016 10:06:08 +0100 [thread overview]
Message-ID: <5784B300.2000308@arm.com> (raw)
In-Reply-To: <1467229774-20738-1-git-send-email-mmayer@broadcom.com>
On 29/06/16 20:49, Markus Mayer wrote:
> From: Florian Fainelli <f.fainelli@gmail.com>
>
> Add an ARCH_BRCMSTB Kconfig symbol which allows us not to update the
> dependencies for all STB-related drivers. Select BRCMSTB_L2_IRQ and
> GENERIC_IRQ_CHIP which are required for proper functioning.
>
> Signed-off-by: Doug Berger <opendmb@gmail.com>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> ---
>
> arch/arm64/Kconfig.platforms | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/arch/arm64/Kconfig.platforms b/arch/arm64/Kconfig.platforms
> index 7ef1d05..22b5c7f 100644
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -29,6 +29,13 @@ config ARCH_BERLIN
> help
> This enables support for Marvell Berlin SoC Family
>
> +config ARCH_BRCMSTB
> + bool "Broadcom Set-Top-Box SoCs"
> + select BRCMSTB_L2_IRQ
I see that BRCMSTB_L2_IRQ selects GENERIC_IRQ_CHIP already so the below
one is redundant, generally irqchip code should select GENERIC_IRQ_CHIP
> + select GENERIC_IRQ_CHIP
> + help
> + This enables support for Broadcom's ARMv8 Set Top Box SoCs
> +
> config ARCH_EXYNOS
> bool "ARMv8 based Samsung Exynos SoC family"
> select COMMON_CLK_SAMSUNG
>
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-07-12 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 19:49 [PATCH] arm64: Add Broadcom Set Top Box Kconfig entry point Markus Mayer
2016-07-11 23:50 ` Florian Fainelli
2016-07-12 9:06 ` Sudeep Holla [this message]
2016-07-13 21:24 ` Florian Fainelli
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=5784B300.2000308@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).