From: Thomas Abraham <thomas.abraham@linaro.org>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: devicetree-discuss@lists.ozlabs.org,
linux-samsung-soc@vger.kernel.org, grant.likely@secretlab.ca,
rob.herring@calxeda.com, arnd@arndb.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] gpio/samsung: Add device tree support for Exynos4
Date: Wed, 2 Nov 2011 18:37:19 +0530 [thread overview]
Message-ID: <CAJuYYwRrku+7u_Ws4_c99xP3tWXG9ewj=sULchwcQK2_sdPnJQ@mail.gmail.com> (raw)
In-Reply-To: <004d01cc9956$46ef8040$d4ce80c0$%kim@samsung.com>
Hi Mr. Kim,
On 2 November 2011 17:25, Kukjin Kim <kgene.kim@samsung.com> wrote:
> Thomas Abraham wrote:
>>
>> As gpio chips get registered, a device tree node which represents the
>> gpio chip is searched and attached to it. A translate function is also
>> provided to convert the gpio specifier into actual platform settings
>> for pin function selection, pull up/down and driver strength settings.
>>
>> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
>> Acked-by: Grant Likely <grant.likely@secretlab.ca>
>> ---
>> Changes since v1:
>> - As suggested by Rob and Grant, the gpio controller node lookup is based
>> on the base address of the gpio controller instead of the unique
>> per-controller compatible property value.
>>
>> This patch is based on the following tree and branch.
>> git://git.linaro.org/git/people/arnd/arm-soc.git branch: for-next
>>
>> .../devicetree/bindings/gpio/gpio-samsung.txt | 40 ++++++++++++
>> drivers/gpio/gpio-samsung.c | 66
>> ++++++++++++++++++++
>> 2 files changed, 106 insertions(+), 0 deletions(-)
>> create mode 100644
[...]
>> diff --git a/drivers/gpio/gpio-samsung.c b/drivers/gpio/gpio-samsung.c
>> index 8662518..0140756 100644
>> --- a/drivers/gpio/gpio-samsung.c
>> +++ b/drivers/gpio/gpio-samsung.c
[...]
> Thomas,
>
> Happens following build error.
>
> drivers/gpio/gpio-samsung.c: In function 'samsung_gpiolib_init':
> drivers/gpio/gpio-samsung.c:2519: error: 'EXYNOS4_PA_GPIO1' undeclared
> (first use in this function)
> drivers/gpio/gpio-samsung.c:2519: error: (Each undeclared identifier is
> reported only once
> drivers/gpio/gpio-samsung.c:2519: error: for each function it appears in.)
> drivers/gpio/gpio-samsung.c:2533: error: 'EXYNOS4_PA_GPIO2' undeclared
> (first use in this function)
> drivers/gpio/gpio-samsung.c:2547: error: 'EXYNOS4_PA_GPIO3' undeclared
> (first use in this function)
Can this be fixed while you apply this patch. If required, I can
submit an updated patch for this.
Thanks,
Thomas.
>
> Thanks.
>
> Best regards,
> Kgene.
> --
> Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
> SW Solution Development Team, Samsung Electronics Co., Ltd.
>
>
prev parent reply other threads:[~2011-11-02 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 0:43 [PATCH v2] gpio/samsung: Add device tree support for Exynos4 Thomas Abraham
2011-11-01 8:22 ` Sylwester Nawrocki
2011-11-02 13:05 ` Thomas Abraham
2011-11-02 13:11 ` Mark Brown
2011-11-02 14:31 ` Sylwester Nawrocki
2011-11-02 11:55 ` Kukjin Kim
2011-11-02 13:07 ` Thomas Abraham [this message]
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='CAJuYYwRrku+7u_Ws4_c99xP3tWXG9ewj=sULchwcQK2_sdPnJQ@mail.gmail.com' \
--to=thomas.abraham@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).