From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: EXYNOS4: add a placeholder for board specific interrupts
Date: Tue, 15 Mar 2011 21:55:20 +0900 [thread overview]
Message-ID: <011301cbe310$41381f10$c3a85d30$%kim@samsung.com> (raw)
In-Reply-To: <1300086405-9895-1-git-send-email-m.szyprowski@samsung.com>
Marek Szyprowski wrote:
>
> This patch adds a placeholder for board specific interrupts on S5PC210
> platform.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> ---
> arch/arm/mach-exynos4/include/mach/irqs.h | 6 +++++-
> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-exynos4/include/mach/irqs.h b/arch/arm/mach-
> exynos4/include/mach/irqs.h
> index 5d03730..cc2186d 100644
> --- a/arch/arm/mach-exynos4/include/mach/irqs.h
> +++ b/arch/arm/mach-exynos4/include/mach/irqs.h
> @@ -154,7 +154,11 @@
> #define IRQ_GPIO2_NR_GROUPS 9
> #define IRQ_GPIO_END (S5P_GPIOINT_BASE + S5P_GPIOINT_COUNT)
>
> +/* optional board specific irqs */
> +#define IRQ_BOARD_START IRQ_GPIO_END
> +#define IRQ_NR_BOARD 16
> +
> /* Set the default NR_IRQS */
> -#define NR_IRQS (IRQ_GPIO_END)
> +#define NR_IRQS (IRQ_GPIO_END + IRQ_NR_BOARD)
>
> #endif /* __ASM_ARCH_IRQS_H */
> --
> 1.7.1.569.g6f426
I have no idea that we need specific interrupt on EXYNOS4 now.
As you know, this can affect all machines of EXYNOS4 SoC even though there
is EXYNOS4210 now.
If required, we need something like SAMSUNG_GPIO_EXTRA for compatibility.
Anyway need more discussion on this :)
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2011-03-15 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 7:06 [PATCH v2] ARM: EXYNOS4: add a placeholder for board specific interrupts Marek Szyprowski
2011-03-15 12:55 ` Kukjin Kim [this message]
2011-03-15 13:07 ` Kyungmin Park
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='011301cbe310$41381f10$c3a85d30$%kim@samsung.com' \
--to=kgene.kim@samsung.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).