From: Tomasz Figa <tomasz.figa@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: "Tomasz Figa" <t.figa@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Kukjin Kim" <kgene.kim@samsung.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>,
"Heiko Stübner" <heiko@sntech.de>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Thomas Abraham" <thomas.abraham@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Prathyush K" <prathyush.k@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>
Subject: Re: [PATCH 4/6] pinctrl: samsung: Add support for SoC-specific suspend/resume callbacks
Date: Fri, 17 May 2013 22:51:04 +0200 [thread overview]
Message-ID: <31112981.QqbfMZZPSN@flatron> (raw)
In-Reply-To: <CAD=FV=Xy2Poti6Wz594DpN1ZbB3FQJ1Dkt+PND1Z0fqf2pJvaw@mail.gmail.com>
On Friday 17 of May 2013 12:24:29 Doug Anderson wrote:
> Tomasz,
>
> On Fri, May 17, 2013 at 9:24 AM, Tomasz Figa <t.figa@samsung.com> wrote:
> > + if (ctrl->resume)
> > + ctrl->resume(drvdata);
> > +
>
> Having this resume at the beginning of the function seems right for
> restoring eint settings like you do in patch #6.
>
> ...but if you need to try to handle the old s3c64xx and s5p64x0
> concept of "restored" to actually take GPIOs out of powerdown mode
> then you'll also need a callback at the end.
>
> Does it make sense to add a second callback at the end of this function?
Right. I haven't thought of this. It might make sense to add .resumed()
callback as well to handle this.
I guess it could be added as a part of patches for S3C64xx-specific
pinctrl suspend/resume, that I will post some day.
> ...since it's unclear how we'll handle s3c64xx/s5p64x0 (or even if I'm
> misunderstanding and they're already handled somehow), I don't see any
> problems with this patch, so...
>
>
> On exynos5250-snow (pinmux backported to 3.8):
>
> Tested-by: Doug Anderson <dianders@chromium.org>
>
> Reviewed-by: Doug Anderson <dianders@chromium.org>
Thanks.
Best regards,
Tomasz
WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/6] pinctrl: samsung: Add support for SoC-specific suspend/resume callbacks
Date: Fri, 17 May 2013 22:51:04 +0200 [thread overview]
Message-ID: <31112981.QqbfMZZPSN@flatron> (raw)
In-Reply-To: <CAD=FV=Xy2Poti6Wz594DpN1ZbB3FQJ1Dkt+PND1Z0fqf2pJvaw@mail.gmail.com>
On Friday 17 of May 2013 12:24:29 Doug Anderson wrote:
> Tomasz,
>
> On Fri, May 17, 2013 at 9:24 AM, Tomasz Figa <t.figa@samsung.com> wrote:
> > + if (ctrl->resume)
> > + ctrl->resume(drvdata);
> > +
>
> Having this resume at the beginning of the function seems right for
> restoring eint settings like you do in patch #6.
>
> ...but if you need to try to handle the old s3c64xx and s5p64x0
> concept of "restored" to actually take GPIOs out of powerdown mode
> then you'll also need a callback at the end.
>
> Does it make sense to add a second callback at the end of this function?
Right. I haven't thought of this. It might make sense to add .resumed()
callback as well to handle this.
I guess it could be added as a part of patches for S3C64xx-specific
pinctrl suspend/resume, that I will post some day.
> ...since it's unclear how we'll handle s3c64xx/s5p64x0 (or even if I'm
> misunderstanding and they're already handled somehow), I don't see any
> problems with this patch, so...
>
>
> On exynos5250-snow (pinmux backported to 3.8):
>
> Tested-by: Doug Anderson <dianders@chromium.org>
>
> Reviewed-by: Doug Anderson <dianders@chromium.org>
Thanks.
Best regards,
Tomasz
next prev parent reply other threads:[~2013-05-17 20:51 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 16:24 [PATCH 0/6] Fix suspend/resume issues created by pinmux on exynos, part 2 Tomasz Figa
2013-05-17 16:24 ` Tomasz Figa
2013-05-17 16:24 ` [PATCH 1/6] pinctrl: exynos: Add support for set_irq_wake of wake-up EINTs Tomasz Figa
2013-05-17 16:24 ` Tomasz Figa
2013-05-17 19:17 ` Doug Anderson
2013-05-17 19:17 ` Doug Anderson
2013-05-21 11:25 ` Linus Walleij
2013-05-21 11:25 ` Linus Walleij
2013-05-17 16:24 ` [PATCH 2/6] ARM: EXYNOS: Fix EINT wake-up mask configuration when pinctrl is used Tomasz Figa
2013-05-17 16:24 ` Tomasz Figa
2013-05-17 19:22 ` Doug Anderson
2013-05-17 19:22 ` Doug Anderson
2013-05-17 19:49 ` Tomasz Figa
2013-05-17 19:49 ` Tomasz Figa
2013-05-21 11:27 ` Linus Walleij
2013-05-21 11:27 ` Linus Walleij
2013-05-17 16:24 ` [PATCH 3/6] ARM: SAMSUNG: pm: Adjust for pinctrl- and DT-enabled platforms Tomasz Figa
2013-05-17 16:24 ` Tomasz Figa
2013-05-17 19:24 ` Doug Anderson
2013-05-17 19:24 ` Doug Anderson
2013-05-17 20:23 ` Tomasz Figa
2013-05-17 20:23 ` Tomasz Figa
2013-05-17 20:56 ` Doug Anderson
2013-05-17 20:56 ` Doug Anderson
2013-05-17 21:07 ` Tomasz Figa
2013-05-17 21:07 ` Tomasz Figa
2013-05-21 11:29 ` Linus Walleij
2013-05-21 11:29 ` Linus Walleij
2013-05-21 13:15 ` Tomasz Figa
2013-05-21 13:15 ` Tomasz Figa
2013-05-21 17:06 ` Tomasz Figa
2013-05-21 17:06 ` Tomasz Figa
2013-06-10 14:45 ` Tomasz Figa
2013-06-10 14:45 ` Tomasz Figa
2013-06-10 16:13 ` Linus Walleij
2013-06-10 16:13 ` Linus Walleij
2013-06-11 7:45 ` Olof Johansson
2013-06-11 7:45 ` Olof Johansson
2013-06-11 8:21 ` Olof Johansson
2013-06-11 8:21 ` Olof Johansson
2013-06-12 0:15 ` Tomasz Figa
2013-06-12 0:15 ` Tomasz Figa
2013-06-12 0:20 ` Olof Johansson
2013-06-12 0:20 ` Olof Johansson
2013-05-17 16:24 ` [PATCH 4/6] pinctrl: samsung: Add support for SoC-specific suspend/resume callbacks Tomasz Figa
2013-05-17 16:24 ` Tomasz Figa
2013-05-17 19:24 ` Doug Anderson
2013-05-17 19:24 ` Doug Anderson
2013-05-17 20:51 ` Tomasz Figa [this message]
2013-05-17 20:51 ` Tomasz Figa
2013-05-24 9:07 ` Linus Walleij
2013-05-24 9:07 ` Linus Walleij
2013-05-24 9:20 ` Tomasz Figa
2013-05-24 9:20 ` Tomasz Figa
2013-05-17 16:24 ` [PATCH 5/6] pinctrl: samsung: Allow per-bank SoC-specific private data Tomasz Figa
2013-05-17 16:24 ` Tomasz Figa
2013-05-17 19:24 ` Doug Anderson
2013-05-17 19:24 ` Doug Anderson
2013-05-24 9:09 ` Linus Walleij
2013-05-24 9:09 ` Linus Walleij
2013-05-17 16:24 ` [PATCH 6/6] pinctrl: exynos: Handle suspend/resume of GPIO EINT registers Tomasz Figa
2013-05-17 16:24 ` Tomasz Figa
2013-05-17 19:25 ` Doug Anderson
2013-05-17 19:25 ` Doug Anderson
2013-05-17 20:34 ` Tomasz Figa
2013-05-17 20:34 ` Tomasz Figa
2013-05-17 21:18 ` Doug Anderson
2013-05-17 21:18 ` Doug Anderson
2013-05-21 17:05 ` [PATCH v2 " Tomasz Figa
2013-05-21 17:05 ` Tomasz Figa
2013-05-22 4:46 ` Doug Anderson
2013-05-22 4:46 ` Doug Anderson
2013-05-22 13:32 ` Tomasz Figa
2013-05-22 13:32 ` Tomasz Figa
2013-05-22 14:03 ` [PATCH v3 " Tomasz Figa
2013-05-22 14:03 ` Tomasz Figa
2013-05-22 15:57 ` Doug Anderson
2013-05-22 15:57 ` Doug Anderson
2013-05-24 9:12 ` Linus Walleij
2013-05-24 9:12 ` Linus Walleij
2013-05-24 9:23 ` Tomasz Figa
2013-05-24 9:23 ` Tomasz Figa
2013-05-20 9:35 ` [PATCH 0/6] Fix suspend/resume issues created by pinmux on exynos, part 2 Tushar Behera
2013-05-20 9:35 ` Tushar Behera
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=31112981.QqbfMZZPSN@flatron \
--to=tomasz.figa@gmail.com \
--cc=arnd@arndb.de \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=prathyush.k@samsung.com \
--cc=swarren@wwwdotorg.org \
--cc=t.figa@samsung.com \
--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.