From: Todd Poynor <toddpoynor@google.com>
To: Tarun Kanti DebBarma <tarun.kanti@ti.com>
Cc: khilman@ti.com, tony@atomide.com, santosh.shilimkar@ti.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Charulatha V <charu@ti.com>
Subject: Re: [PATCH v4 REPOST 18/20] gpio/omap: use pm-runtime framework
Date: Sat, 16 Jul 2011 12:07:34 -0700 [thread overview]
Message-ID: <20110716190734.GB990@google.com> (raw)
In-Reply-To: <1310804152-9243-19-git-send-email-tarun.kanti@ti.com>
On Sat, Jul 16, 2011 at 01:45:50PM +0530, Tarun Kanti DebBarma wrote:
> Call runtime pm APIs pm_runtime_get_sync() and pm_runtime_put_sync()
> for enabling/disabling clocks appropriately. Remove syscore_ops and
> instead use dev_pm_ops now.
>
...
> @@ -481,6 +483,22 @@ static int omap_gpio_request(struct gpio_chip *chip, unsigned offset)
>
> spin_lock_irqsave(&bank->lock, flags);
>
> + /*
> + * If this is the first gpio_request for the bank,
> + * enable the bank module.
> + */
> + if (!bank->mod_usage) {
> + if (IS_ERR_VALUE(pm_runtime_get_sync(bank->dev) < 0)) {
> + dev_err(bank->dev, "%s: GPIO bank %d "
> + "pm_runtime_get_sync failed\n",
> + __func__, bank->id);
> + return -EINVAL;
Must spin_unlock_irqrestore() first.
> + }
> +
> + /* Initialize the gpio bank registers to init time value */
> + omap_gpio_mod_init(bank);
omap_gpio_mod_init calls mpuio_init calls platform_driver_register
which can't be called in an IRQs off and spinlocked atomic context,
for example, device_private_init calls kzalloc with GFP_KERNEL.
Concurrency protection for this will need to happen prior to the
spinlock (assuming it really does need to be an IRQ saving spinlock
and not a mutex). Possibly a new mutex is needed to protect the
check for first usage and init'ing the bank (and blocking a racing
second caller until the init is done).
The omap_gpio_mod_init may be unbalanced with the code performed below
on last free of a GPIO for the bank? If all GPIOs are freed and then
a new GPIO used, does omap_gpio_mod_init do the right thing? Need a
separate flag to indicate whether one-time init has ever been
performed, vs. needing runtime PM enable/disable?
> + }
> +
> /* Set trigger to none. You need to enable the desired trigger with
> * request_irq() or set_irq_type().
> */
> @@ -517,7 +535,6 @@ static void omap_gpio_free(struct gpio_chip *chip, unsigned offset)
> unsigned long flags;
>
> spin_lock_irqsave(&bank->lock, flags);
> -
> if (bank->regs->wkup_status)
> /* Disable wake-up during idle for dynamic tick */
> _gpio_rmw(base, bank->regs->wkup_status, 1 << offset, 0);
> @@ -535,6 +552,18 @@ static void omap_gpio_free(struct gpio_chip *chip, unsigned offset)
> }
>
> _reset_gpio(bank, bank->chip.base + offset);
> +
> + /*
> + * If this is the last gpio to be freed in the bank,
> + * disable the bank module.
> + */
> + if (!bank->mod_usage) {
> + if (IS_ERR_VALUE(pm_runtime_put_sync(bank->dev) < 0)) {
> + dev_err(bank->dev, "%s: GPIO bank %d "
> + "pm_runtime_put_sync failed\n",
> + __func__, bank->id);
> + }
> + }
> spin_unlock_irqrestore(&bank->lock, flags);
Todd
WARNING: multiple messages have this Message-ID (diff)
From: toddpoynor@google.com (Todd Poynor)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 REPOST 18/20] gpio/omap: use pm-runtime framework
Date: Sat, 16 Jul 2011 12:07:34 -0700 [thread overview]
Message-ID: <20110716190734.GB990@google.com> (raw)
In-Reply-To: <1310804152-9243-19-git-send-email-tarun.kanti@ti.com>
On Sat, Jul 16, 2011 at 01:45:50PM +0530, Tarun Kanti DebBarma wrote:
> Call runtime pm APIs pm_runtime_get_sync() and pm_runtime_put_sync()
> for enabling/disabling clocks appropriately. Remove syscore_ops and
> instead use dev_pm_ops now.
>
...
> @@ -481,6 +483,22 @@ static int omap_gpio_request(struct gpio_chip *chip, unsigned offset)
>
> spin_lock_irqsave(&bank->lock, flags);
>
> + /*
> + * If this is the first gpio_request for the bank,
> + * enable the bank module.
> + */
> + if (!bank->mod_usage) {
> + if (IS_ERR_VALUE(pm_runtime_get_sync(bank->dev) < 0)) {
> + dev_err(bank->dev, "%s: GPIO bank %d "
> + "pm_runtime_get_sync failed\n",
> + __func__, bank->id);
> + return -EINVAL;
Must spin_unlock_irqrestore() first.
> + }
> +
> + /* Initialize the gpio bank registers to init time value */
> + omap_gpio_mod_init(bank);
omap_gpio_mod_init calls mpuio_init calls platform_driver_register
which can't be called in an IRQs off and spinlocked atomic context,
for example, device_private_init calls kzalloc with GFP_KERNEL.
Concurrency protection for this will need to happen prior to the
spinlock (assuming it really does need to be an IRQ saving spinlock
and not a mutex). Possibly a new mutex is needed to protect the
check for first usage and init'ing the bank (and blocking a racing
second caller until the init is done).
The omap_gpio_mod_init may be unbalanced with the code performed below
on last free of a GPIO for the bank? If all GPIOs are freed and then
a new GPIO used, does omap_gpio_mod_init do the right thing? Need a
separate flag to indicate whether one-time init has ever been
performed, vs. needing runtime PM enable/disable?
> + }
> +
> /* Set trigger to none. You need to enable the desired trigger with
> * request_irq() or set_irq_type().
> */
> @@ -517,7 +535,6 @@ static void omap_gpio_free(struct gpio_chip *chip, unsigned offset)
> unsigned long flags;
>
> spin_lock_irqsave(&bank->lock, flags);
> -
> if (bank->regs->wkup_status)
> /* Disable wake-up during idle for dynamic tick */
> _gpio_rmw(base, bank->regs->wkup_status, 1 << offset, 0);
> @@ -535,6 +552,18 @@ static void omap_gpio_free(struct gpio_chip *chip, unsigned offset)
> }
>
> _reset_gpio(bank, bank->chip.base + offset);
> +
> + /*
> + * If this is the last gpio to be freed in the bank,
> + * disable the bank module.
> + */
> + if (!bank->mod_usage) {
> + if (IS_ERR_VALUE(pm_runtime_put_sync(bank->dev) < 0)) {
> + dev_err(bank->dev, "%s: GPIO bank %d "
> + "pm_runtime_put_sync failed\n",
> + __func__, bank->id);
> + }
> + }
> spin_unlock_irqrestore(&bank->lock, flags);
Todd
next prev parent reply other threads:[~2011-07-16 19:07 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 8:15 [PATCH v4 REPOST 00/20] gpio/omap: driver cleanup and fixes Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 01/20] gpio/omap: remove dependency on gpio_bank_count Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 02/20] gpio/omap: use flag to identify wakeup domain Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 03/20] gpio/omap: make gpio_context part of gpio_bank structure Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 04/20] gpio/omap: fix pwrdm_post_transition call sequence Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 05/20] gpio/omap: handle save/restore ctx in GPIO driver Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 06/20] gpio/omap: make non-wakeup GPIO part of pdata Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 07/20] gpio/omap: avoid cpu checks during module ena/disable Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 08/20] gpio/omap: further cleanup using wakeup_status register Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 09/20] gpio/omap: cleanup omap1 related macros Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 10/20] gpio/omap: use level/edge detect reg offsets Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 11/20] gpio/omap: remove hardcoded offsets in ctxt save/restore Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 12/20] gpio/omap: cleanup set_gpio_triggering function Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 13/20] gpio/omap: cleanup omap_gpio_mod_init function Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 18:26 ` Todd Poynor
2011-07-16 18:26 ` Todd Poynor
2011-07-20 7:07 ` DebBarma, Tarun Kanti
2011-07-20 7:07 ` DebBarma, Tarun Kanti
2011-07-16 8:15 ` [PATCH v4 REPOST 14/20] gpio/omap: use pinctrl offset instead of macro Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 15/20] gpio/omap: use readl in irq_handler for all access Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 16/20] gpio/omap: remove bank->method & METHOD_* macros Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 17/20] gpio/omap: fix bankwidth for OMAP7xx MPUIO Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 18/20] gpio/omap: use pm-runtime framework Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 19:07 ` Todd Poynor [this message]
2011-07-16 19:07 ` Todd Poynor
2011-07-20 10:08 ` DebBarma, Tarun Kanti
2011-07-20 10:08 ` DebBarma, Tarun Kanti
2011-07-27 11:44 ` DebBarma, Tarun Kanti
2011-07-27 11:44 ` DebBarma, Tarun Kanti
2011-07-28 7:43 ` Todd Poynor
2011-07-28 7:43 ` Todd Poynor
2011-07-28 9:35 ` DebBarma, Tarun Kanti
2011-07-28 9:35 ` DebBarma, Tarun Kanti
2011-07-28 17:00 ` Todd Poynor
2011-07-28 17:00 ` Todd Poynor
2011-07-29 10:45 ` DebBarma, Tarun Kanti
2011-07-29 10:45 ` DebBarma, Tarun Kanti
2011-07-29 10:55 ` DebBarma, Tarun Kanti
2011-07-29 10:55 ` DebBarma, Tarun Kanti
2011-07-16 8:15 ` [PATCH v4 REPOST 19/20] gpio/omap: optimize suspend and resume functions Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
2011-07-16 8:15 ` [PATCH v4 REPOST 20/20] gpio/omap: cleanup prepare_for_idle and resume_after_idle Tarun Kanti DebBarma
2011-07-16 8:15 ` Tarun Kanti DebBarma
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=20110716190734.GB990@google.com \
--to=toddpoynor@google.com \
--cc=charu@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=tarun.kanti@ti.com \
--cc=tony@atomide.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.