All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abhilash Kesavan <kesavan.abhilash@gmail.com>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: exynos: Remove eint_gpio_init call-back for exynos7 alive pinctrl block
Date: Mon, 9 Mar 2015 22:22:17 +0530	[thread overview]
Message-ID: <CAM4voandpVQqVtHgZdTViEzNtBj=XWJ7A7yY5oGqgqg4btxzCA@mail.gmail.com> (raw)
In-Reply-To: <CA+Ln22HGH3r6UEYtCPU7Y4a0-b4FKnx8d0VcA3a1-m1VD5Jm=w@mail.gmail.com>

Hi Tomasz,

On Mon, Mar 9, 2015 at 3:54 PM, Tomasz Figa <tomasz.figa@gmail.com> wrote:
> Hi Abhilash, Linus,
>
> 2015-03-02 1:21 GMT+09:00 Abhilash Kesavan <a.kesavan@samsung.com>:
>> The alive pin controller on exynos7 does not support external gpio
>> interrupts. Hence, remove the eint_gpio_init call-back for it. This
>> fixes the following error message seen during exynos7 boot-up:
>> "samsung-pinctrl 10580000.pinctrl: irq number not available"
>
> As long as "external gpio interrupts" refer to non-wake-up-capable
> GPIO interrupts I'm fine with this patch.

Yes, that was the intention. Thanks for the review.

Regards,
Abhilash
>
> Acked-by: Tomasz Figa <tomasz.figa@gmail.com>
>
> Thanks Linus for pinging and sorry for delay.
>
> Best regards,
> Tomasz

WARNING: multiple messages have this Message-ID (diff)
From: kesavan.abhilash@gmail.com (Abhilash Kesavan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: exynos: Remove eint_gpio_init call-back for exynos7 alive pinctrl block
Date: Mon, 9 Mar 2015 22:22:17 +0530	[thread overview]
Message-ID: <CAM4voandpVQqVtHgZdTViEzNtBj=XWJ7A7yY5oGqgqg4btxzCA@mail.gmail.com> (raw)
In-Reply-To: <CA+Ln22HGH3r6UEYtCPU7Y4a0-b4FKnx8d0VcA3a1-m1VD5Jm=w@mail.gmail.com>

Hi Tomasz,

On Mon, Mar 9, 2015 at 3:54 PM, Tomasz Figa <tomasz.figa@gmail.com> wrote:
> Hi Abhilash, Linus,
>
> 2015-03-02 1:21 GMT+09:00 Abhilash Kesavan <a.kesavan@samsung.com>:
>> The alive pin controller on exynos7 does not support external gpio
>> interrupts. Hence, remove the eint_gpio_init call-back for it. This
>> fixes the following error message seen during exynos7 boot-up:
>> "samsung-pinctrl 10580000.pinctrl: irq number not available"
>
> As long as "external gpio interrupts" refer to non-wake-up-capable
> GPIO interrupts I'm fine with this patch.

Yes, that was the intention. Thanks for the review.

Regards,
Abhilash
>
> Acked-by: Tomasz Figa <tomasz.figa@gmail.com>
>
> Thanks Linus for pinging and sorry for delay.
>
> Best regards,
> Tomasz

  reply	other threads:[~2015-03-09 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01 16:21 [PATCH] pinctrl: exynos: Remove eint_gpio_init call-back for exynos7 alive pinctrl block Abhilash Kesavan
2015-03-01 16:21 ` Abhilash Kesavan
2015-03-09 10:08 ` Linus Walleij
2015-03-09 10:08   ` Linus Walleij
2015-03-09 10:24 ` Tomasz Figa
2015-03-09 10:24   ` Tomasz Figa
2015-03-09 16:52   ` Abhilash Kesavan [this message]
2015-03-09 16:52     ` Abhilash Kesavan
2015-03-17 12:23 ` Linus Walleij
2015-03-17 12:23   ` 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='CAM4voandpVQqVtHgZdTViEzNtBj=XWJ7A7yY5oGqgqg4btxzCA@mail.gmail.com' \
    --to=kesavan.abhilash@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=tomasz.figa@gmail.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 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.