From: 박상수 <sangsu4u.park@samsung.com>
To: "'Doug Anderson'" <dianders@chromium.org>,
"'Sean Paul'" <seanpaul@chromium.org>
Cc: grant.likely@secretlab.ca, linus.walleij@stericsson.com,
linux-kernel@vger.kernel.org, olofj@chromium.org,
"'Thomas Abraham'" <thomas.abraham@linaro.org>,
"'Kukjin Kim'" <kgene.kim@samsung.com>
Subject: RE: [PATCH] gpio: samsung: Fix off-by-one bug in gpio addresses
Date: Mon, 30 Jul 2012 17:04:47 +0900 [thread overview]
Message-ID: <000001cd6e29$fcb4bc30$f61e3490$@samsung.com> (raw)
In-Reply-To: <CAD=FV=W8oqytNM0xSHbceTEy6gAdr_Lmm7zWqogcwAPJR6jKSg@mail.gmail.com>
> -----Original Message-----
> From: dianders@google.com [mailto:dianders@google.com] On Behalf Of Doug Anderson
> Sent: Saturday, July 21, 2012 6:07 AM
> To: Sean Paul
> Cc: grant.likely@secretlab.ca; linus.walleij@stericsson.com; linux-kernel@vger.kernel.org;
> olofj@chromium.org; Sangsu Park; Thomas Abraham; Kukjin Kim
> Subject: Re: [PATCH] gpio: samsung: Fix off-by-one bug in gpio addresses
>
> Acked-by: Doug Anderson <dianders@chromium.org>
>
> ---
>
> On Fri, Jul 20, 2012 at 1:58 PM, Sean Paul <seanpaul@chromium.org> wrote:
> >
> > Move gpc4 to the end of the automatically processed gpio controllers
> > so we don't taint the automatic offset calculation.
> >
> > This bug caused all controllers coming after gpc4 to map to the
> > incorrect address. The result is <&gpd1 0 0 0 0> would actually map to
> > GPIO 0 in gpd0.
> >
> > Signed-off-by: Sean Paul <seanpaul@chromium.org>
> > ---
> > drivers/gpio/gpio-samsung.c | 14 +++++++-------
> > 1 files changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/gpio/gpio-samsung.c b/drivers/gpio/gpio-samsung.c
> > index b6453d0..e4599b4 100644
> > --- a/drivers/gpio/gpio-samsung.c
> > +++ b/drivers/gpio/gpio-samsung.c
> > @@ -2454,12 +2454,6 @@ static struct samsung_gpio_chip exynos5_gpios_1[] = {
> > },
> > }, {
> > .chip = {
> > - .base = EXYNOS5_GPC4(0),
> > - .ngpio = EXYNOS5_GPIO_C4_NR,
> > - .label = "GPC4",
> > - },
> > - }, {
> > - .chip = {
> > .base = EXYNOS5_GPD0(0),
> > .ngpio = EXYNOS5_GPIO_D0_NR,
> > .label = "GPD0", @@ -2513,6 +2507,12 @@
> > static struct samsung_gpio_chip exynos5_gpios_1[] = {
> > .label = "GPY6",
> > },
> > }, {
> > + .chip = {
> > + .base = EXYNOS5_GPC4(0),
> > + .ngpio = EXYNOS5_GPIO_C4_NR,
> > + .label = "GPC4",
> > + },
> > + }, {
> > .config = &samsung_gpio_cfgs[9],
> > .irq_base = IRQ_EINT(0),
> > .chip = {
> > @@ -2833,7 +2833,7 @@ static __init void exynos5_gpiolib_init(void)
> > }
> >
> > /* need to set base address for gpc4 */
> > - exynos5_gpios_1[11].base = gpio_base1 + 0x2E0;
> > + exynos5_gpios_1[20].base = gpio_base1 + 0x2E0;
> >
> > /* need to set base address for gpx */
> > chip = &exynos5_gpios_1[21];
> > --
> > 1.7.7.3
> >
I think that this modification is right.
Thanks.
next prev parent reply other threads:[~2012-07-30 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 20:58 Sean Paul
2012-07-20 21:06 ` Doug Anderson
2012-07-30 8:04 ` 박상수 [this message]
2012-07-30 8:37 ` Thomas Abraham
2012-07-27 23:09 ` Linus Walleij
2012-07-31 23:27 ` Kukjin Kim
2012-08-05 9:59 ` Linus Walleij
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='000001cd6e29$fcb4bc30$f61e3490$@samsung.com' \
--to=sangsu4u.park@samsung.com \
--cc=dianders@chromium.org \
--cc=grant.likely@secretlab.ca \
--cc=kgene.kim@samsung.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@chromium.org \
--cc=seanpaul@chromium.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 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®