From: Tony Lindgren <tony@atomide.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Felipe Balbi <balbi@ti.com>,
Grygorii Strashko <grygorii.strashko@linaro.org>,
Javier Martinez Canillas <jmartinez@softcrates.net>,
Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH 1/1] gpio: omap: Fix PM runtime issue and remove most BANK_USED macros
Date: Tue, 12 May 2015 07:13:49 -0700 [thread overview]
Message-ID: <20150512141348.GG15563@atomide.com> (raw)
In-Reply-To: <CACRpkdZ1nJ=-NPHrZdCQ6_TCrF7009R9Y7zVyXN1z9RWcv3a6A@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [150512 02:01]:
> On Tue, Apr 21, 2015 at 6:08 PM, Tony Lindgren <tony@atomide.com> wrote:
>
> > Looks like omap_gpio_irq_type can return early at several places
> > leaving a GPIO bank enabled without doing pm_runtime_put if wrong
> > GPIO arguments are passed.
> >
> > Instead of adding more complicated BANK_USED macros, let's fix the
> > issue properly. We can pass is_irq flag to omap_enable_gpio_module
> > and omap_disble_gpio_module. And with that we can remove all the
> > similar code elsewhere to get rid of most BANK_USED macros.
> >
> > Note that the reason for the BANK_USED macro is that we need to manage
> > PM runtime on per GPIO bank basis. In the long run we want to move to
> > using PM runtime counts for each GPIO line to determine if a GPIO
> > bank is used. Once we have a solution for omap_enable_gpio_module
> > and omap_disable_gpio_module, we can remove the remaining BANK_USED
> > macros.
> >
> > Cc: Felipe Balbi <balbi@ti.com>
> > Cc: Grygorii Strashko <grygorii.strashko@linaro.org>
> > Cc: Javier Martinez Canillas <jmartinez@softcrates.net>
> > Cc: Nishanth Menon <nm@ti.com>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> There is so much discussion around this patch that I can't make
> up my mind whether I should apply this or some subsequent inline
> version of it.
>
> Holding this off for now...
Yeah let's see what Grygorii comes up, sounds like he may have
a minimal fix coming up. Then we can do the rest as clean-up
later on.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] gpio: omap: Fix PM runtime issue and remove most BANK_USED macros
Date: Tue, 12 May 2015 07:13:49 -0700 [thread overview]
Message-ID: <20150512141348.GG15563@atomide.com> (raw)
In-Reply-To: <CACRpkdZ1nJ=-NPHrZdCQ6_TCrF7009R9Y7zVyXN1z9RWcv3a6A@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [150512 02:01]:
> On Tue, Apr 21, 2015 at 6:08 PM, Tony Lindgren <tony@atomide.com> wrote:
>
> > Looks like omap_gpio_irq_type can return early at several places
> > leaving a GPIO bank enabled without doing pm_runtime_put if wrong
> > GPIO arguments are passed.
> >
> > Instead of adding more complicated BANK_USED macros, let's fix the
> > issue properly. We can pass is_irq flag to omap_enable_gpio_module
> > and omap_disble_gpio_module. And with that we can remove all the
> > similar code elsewhere to get rid of most BANK_USED macros.
> >
> > Note that the reason for the BANK_USED macro is that we need to manage
> > PM runtime on per GPIO bank basis. In the long run we want to move to
> > using PM runtime counts for each GPIO line to determine if a GPIO
> > bank is used. Once we have a solution for omap_enable_gpio_module
> > and omap_disable_gpio_module, we can remove the remaining BANK_USED
> > macros.
> >
> > Cc: Felipe Balbi <balbi@ti.com>
> > Cc: Grygorii Strashko <grygorii.strashko@linaro.org>
> > Cc: Javier Martinez Canillas <jmartinez@softcrates.net>
> > Cc: Nishanth Menon <nm@ti.com>
> > Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> There is so much discussion around this patch that I can't make
> up my mind whether I should apply this or some subsequent inline
> version of it.
>
> Holding this off for now...
Yeah let's see what Grygorii comes up, sounds like he may have
a minimal fix coming up. Then we can do the rest as clean-up
later on.
Regards,
Tony
next prev parent reply other threads:[~2015-05-12 14:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 16:08 [PATCH 1/1] gpio: omap: Fix PM runtime issue and remove most BANK_USED macros Tony Lindgren
2015-04-21 16:08 ` Tony Lindgren
2015-04-22 14:20 ` Felipe Balbi
2015-04-22 14:20 ` Felipe Balbi
2015-04-23 11:12 ` Grygorii.Strashko@linaro.org
2015-04-23 11:12 ` Grygorii.Strashko@linaro.org
2015-04-23 14:39 ` Tony Lindgren
2015-04-23 14:39 ` Tony Lindgren
2015-04-28 21:57 ` Grygorii.Strashko@linaro.org
2015-04-28 21:57 ` Grygorii.Strashko@linaro.org
2015-04-29 14:26 ` Tony Lindgren
2015-04-29 14:26 ` Tony Lindgren
2015-04-30 19:10 ` Grygorii.Strashko@linaro.org
2015-04-30 19:10 ` Grygorii.Strashko@linaro.org
2015-04-30 21:12 ` Tony Lindgren
2015-04-30 21:12 ` Tony Lindgren
2015-05-02 16:27 ` Grygorii.Strashko@linaro.org
2015-05-02 16:27 ` Grygorii.Strashko@linaro.org
2015-05-04 15:38 ` Tony Lindgren
2015-05-04 15:38 ` Tony Lindgren
2015-05-12 9:00 ` Linus Walleij
2015-05-12 9:00 ` Linus Walleij
2015-05-12 14:13 ` Tony Lindgren [this message]
2015-05-12 14:13 ` Tony Lindgren
2015-05-12 15:31 ` Grygorii.Strashko@linaro.org
2015-05-12 15:31 ` Grygorii.Strashko@linaro.org
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=20150512141348.GG15563@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@linaro.org \
--cc=jmartinez@softcrates.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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.