From: Kukjin Kim <kgene.kim@samsung.com>
To: Thomas Abraham <thomas.abraham@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linus.walleij@linaro.org, kgene.kim@samsung.com,
patches@linaro.org
Subject: Re: [PATCH 3/5] ARM: Exynos4: Add pinctrl devices and pin maps
Date: Sun, 11 Mar 2012 14:17:21 -0700 [thread overview]
Message-ID: <4F5D1661.4090007@samsung.com> (raw)
In-Reply-To: <1331469965-28846-4-git-send-email-thomas.abraham@linaro.org>
Thomas Abraham wrote:
> Add the three pinctrl platform devices and the pin maps for Exynos4.
>
> Signed-off-by: Thomas Abraham<thomas.abraham@linaro.org>
> ---
> arch/arm/mach-exynos/Kconfig | 1 +
> arch/arm/mach-exynos/Makefile | 1 +
> arch/arm/mach-exynos/common.h | 6 ++
> arch/arm/mach-exynos/dev-pinctrl.c | 115 +++++++++++++++++++++++++++++
> arch/arm/plat-samsung/include/plat/devs.h | 3 +
> 5 files changed, 126 insertions(+), 0 deletions(-)
> create mode 100644 arch/arm/mach-exynos/dev-pinctrl.c
[...]
> +#include<linux/kernel.h>
> +#include<linux/dma-mapping.h>
> +#include<linux/platform_device.h>
> +#include<linux/interrupt.h>
> +#include<linux/pinctrl/machine.h>
#include <linux/ioport.h> for DEFINE_RES_xxx at below.
> +
> +#include<plat/devs.h>
> +#include<plat/pinctrl.h>
> +
> +#include<mach/map.h>
> +
> +static struct resource exynos4_pinctrl_resource0[] = {
> + [0] = {
> + .start = EXYNOS4_PA_GPIO1,
> + .end = EXYNOS4_PA_GPIO1 + SZ_4K - 1,
> + .flags = IORESOURCE_MEM,
> + },
[0] = DEFINE_RES_MEM(EXYNOS4_PA_GPIO1, SZ_4K),
> + [1] = {
> + .start = IRQ_GPIO_XA,
> + .end = IRQ_GPIO_XA,
> + .flags = IORESOURCE_IRQ,
> + },
[1] = DEFINE_RES_IRQ(IRQ_GPIO_XA),
But I'm thinking, we need to move to use EXYNOS4_IRQ_GPIO_XA here for
both EXYNOS4 and EXYNOS5 and as a note, I'm working on updating IRQ
naming you can see it in this week :)
> +};
> +
> +struct platform_device exynos4_pinctrl0 = {
> + .name = "exynos4-pinctrl",
> + .id = 0,
> + .resource = exynos4_pinctrl_resource0,
> + .num_resources = ARRAY_SIZE(exynos4_pinctrl_resource0),
> +};
> +
> +static struct resource exynos4_pinctrl_resource1[] = {
> + [0] = {
> + .start = EXYNOS4_PA_GPIO2,
> + .end = EXYNOS4_PA_GPIO2 + SZ_4K - 1,
> + .flags = IORESOURCE_MEM,
> + },
same as above.
> + [1] = {
> + .start = IRQ_GPIO_XB,
> + .end = IRQ_GPIO_XB,
> + .flags = IORESOURCE_IRQ,
> + },
same.
> +};
> +
> +struct platform_device exynos4_pinctrl1 = {
> + .name = "exynos4-pinctrl",
> + .id = 1,
> + .resource = exynos4_pinctrl_resource1,
> + .num_resources = ARRAY_SIZE(exynos4_pinctrl_resource1),
> +};
> +
> +static struct resource exynos4_pinctrl_resource2[] = {
> + [0] = {
> + .start = EXYNOS4_PA_GPIO3,
> + .end = EXYNOS4_PA_GPIO3 + SZ_4K - 1,
> + .flags = IORESOURCE_MEM,
> + },
same.
> +};
> +
> +struct platform_device exynos4_pinctrl2 = {
> + .name = "exynos4-pinctrl",
> + .id = 2,
> + .resource = exynos4_pinctrl_resource2,
> + .num_resources = ARRAY_SIZE(exynos4_pinctrl_resource2),
> +};
> +
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: Exynos4: Add pinctrl devices and pin maps
Date: Sun, 11 Mar 2012 14:17:21 -0700 [thread overview]
Message-ID: <4F5D1661.4090007@samsung.com> (raw)
In-Reply-To: <1331469965-28846-4-git-send-email-thomas.abraham@linaro.org>
Thomas Abraham wrote:
> Add the three pinctrl platform devices and the pin maps for Exynos4.
>
> Signed-off-by: Thomas Abraham<thomas.abraham@linaro.org>
> ---
> arch/arm/mach-exynos/Kconfig | 1 +
> arch/arm/mach-exynos/Makefile | 1 +
> arch/arm/mach-exynos/common.h | 6 ++
> arch/arm/mach-exynos/dev-pinctrl.c | 115 +++++++++++++++++++++++++++++
> arch/arm/plat-samsung/include/plat/devs.h | 3 +
> 5 files changed, 126 insertions(+), 0 deletions(-)
> create mode 100644 arch/arm/mach-exynos/dev-pinctrl.c
[...]
> +#include<linux/kernel.h>
> +#include<linux/dma-mapping.h>
> +#include<linux/platform_device.h>
> +#include<linux/interrupt.h>
> +#include<linux/pinctrl/machine.h>
#include <linux/ioport.h> for DEFINE_RES_xxx at below.
> +
> +#include<plat/devs.h>
> +#include<plat/pinctrl.h>
> +
> +#include<mach/map.h>
> +
> +static struct resource exynos4_pinctrl_resource0[] = {
> + [0] = {
> + .start = EXYNOS4_PA_GPIO1,
> + .end = EXYNOS4_PA_GPIO1 + SZ_4K - 1,
> + .flags = IORESOURCE_MEM,
> + },
[0] = DEFINE_RES_MEM(EXYNOS4_PA_GPIO1, SZ_4K),
> + [1] = {
> + .start = IRQ_GPIO_XA,
> + .end = IRQ_GPIO_XA,
> + .flags = IORESOURCE_IRQ,
> + },
[1] = DEFINE_RES_IRQ(IRQ_GPIO_XA),
But I'm thinking, we need to move to use EXYNOS4_IRQ_GPIO_XA here for
both EXYNOS4 and EXYNOS5 and as a note, I'm working on updating IRQ
naming you can see it in this week :)
> +};
> +
> +struct platform_device exynos4_pinctrl0 = {
> + .name = "exynos4-pinctrl",
> + .id = 0,
> + .resource = exynos4_pinctrl_resource0,
> + .num_resources = ARRAY_SIZE(exynos4_pinctrl_resource0),
> +};
> +
> +static struct resource exynos4_pinctrl_resource1[] = {
> + [0] = {
> + .start = EXYNOS4_PA_GPIO2,
> + .end = EXYNOS4_PA_GPIO2 + SZ_4K - 1,
> + .flags = IORESOURCE_MEM,
> + },
same as above.
> + [1] = {
> + .start = IRQ_GPIO_XB,
> + .end = IRQ_GPIO_XB,
> + .flags = IORESOURCE_IRQ,
> + },
same.
> +};
> +
> +struct platform_device exynos4_pinctrl1 = {
> + .name = "exynos4-pinctrl",
> + .id = 1,
> + .resource = exynos4_pinctrl_resource1,
> + .num_resources = ARRAY_SIZE(exynos4_pinctrl_resource1),
> +};
> +
> +static struct resource exynos4_pinctrl_resource2[] = {
> + [0] = {
> + .start = EXYNOS4_PA_GPIO3,
> + .end = EXYNOS4_PA_GPIO3 + SZ_4K - 1,
> + .flags = IORESOURCE_MEM,
> + },
same.
> +};
> +
> +struct platform_device exynos4_pinctrl2 = {
> + .name = "exynos4-pinctrl",
> + .id = 2,
> + .resource = exynos4_pinctrl_resource2,
> + .num_resources = ARRAY_SIZE(exynos4_pinctrl_resource2),
> +};
> +
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:[~2012-03-11 21:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 12:46 [PATCH 0/5] pinctrl: add new Samsung pinctrl driver and add Exynos4 support Thomas Abraham
2012-03-11 12:46 ` Thomas Abraham
2012-03-11 12:46 ` [PATCH 1/5] pinctrl: add samsung pinctrl and gpiolib driver Thomas Abraham
2012-03-11 12:46 ` Thomas Abraham
2012-03-19 21:45 ` Stephen Warren
2012-03-19 21:45 ` Stephen Warren
2012-03-11 12:46 ` [PATCH 2/5] pinctrl: add exynos4 specific pins, groups, functions and gpio chip data Thomas Abraham
2012-03-11 12:46 ` Thomas Abraham
2012-03-11 12:46 ` [PATCH 3/5] ARM: Exynos4: Add pinctrl devices and pin maps Thomas Abraham
2012-03-11 12:46 ` Thomas Abraham
2012-03-11 21:17 ` Kukjin Kim [this message]
2012-03-11 21:17 ` Kukjin Kim
2012-03-12 4:22 ` Thomas Abraham
2012-03-12 4:22 ` Thomas Abraham
2012-03-11 12:46 ` [PATCH 4/5] ARM: Exynos: Enable pinctrl driver support for Origen board Thomas Abraham
2012-03-11 12:46 ` Thomas Abraham
2012-03-11 12:46 ` [PATCH 5/5] mmc: sdhci-s3c: setup pins using pinctrl interface Thomas Abraham
2012-03-11 12:46 ` Thomas Abraham
2012-03-11 21:25 ` Kukjin Kim
2012-03-11 21:25 ` Kukjin Kim
2012-03-12 4:28 ` Thomas Abraham
2012-03-12 4:28 ` Thomas Abraham
2012-03-12 2:38 ` Kyungmin Park
2012-03-12 2:38 ` Kyungmin Park
2012-03-12 4:37 ` Thomas Abraham
2012-03-12 4:37 ` Thomas Abraham
2012-03-12 14:21 ` Mark Brown
2012-03-12 14:21 ` Mark Brown
2012-03-12 14:31 ` Thomas Abraham
2012-03-12 14:31 ` Thomas Abraham
2012-03-12 16:12 ` Mark Brown
2012-03-12 16:12 ` Mark Brown
2012-03-19 21:55 ` Stephen Warren
2012-03-19 21:55 ` Stephen Warren
2012-03-13 10:13 ` [PATCH 0/5] pinctrl: add new Samsung pinctrl driver and add Exynos4 support Linus Walleij
2012-03-13 10:13 ` Linus Walleij
2012-03-13 10:18 ` Thomas Abraham
2012-03-13 10:18 ` Thomas Abraham
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=4F5D1661.4090007@samsung.com \
--to=kgene.kim@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=thomas.abraham@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.