linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Omar Ramirez Luna <omar.ramirez@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	Benoit Cousson <b-cousson@ti.com>, Kevin Hilman <khilman@ti.com>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Russell King <linux@arm.linux.org.uk>,
	Linux PM <linux-pm@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	iommu@lists.linux-foundation.org,
	MyungJoo Ham <myungjoo.ham@gmail.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 4/4] OMAP3/4: iommu: adapt to runtime pm
Date: Fri, 16 Dec 2011 02:53:21 +0200	[thread overview]
Message-ID: <CAMP44s3Jb9DZLUyDVU_HmQbaJKp=2qym7Z6uauNchJh0fPL4hQ@mail.gmail.com> (raw)
In-Reply-To: <1323922709-6986-5-git-send-email-omar.ramirez@ti.com>

On Thu, Dec 15, 2011 at 6:18 AM, Omar Ramirez Luna <omar.ramirez@ti.com> wrote:
> Use runtime PM functionality interfaced with hwmod enable/idle
> functions, to replace direct clock operations, reset and sysconfig
> handling.
>
> Removed clk handling during interrupt, given that in order to receive one,
> the device should be powered on in advance. Now doing pm_runtime_get/put
> on iommu_enable/disable so it doesn't rely on others to keep the clocks on.
>
> Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com>
> ---
>  arch/arm/mach-omap2/iommu2.c             |   17 -----------
>  arch/arm/mach-omap2/omap-iommu.c         |    1 -
>  arch/arm/plat-omap/include/plat/iommu.h  |    2 -
>  arch/arm/plat-omap/include/plat/iommu2.h |    2 -
>  drivers/iommu/omap-iommu.c               |   44 ++++++++++++-----------------
>  5 files changed, 18 insertions(+), 48 deletions(-)

Shouldn't pm_runtime_enable() be called in omap_iommu_init(), and
omap_iommu_probe() call pm_runtime_get_sync()/put() on the sections
where the device should be active?

Cheers.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-12-16  0:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15  4:18 [PATCH v4 0/4] OMAP: iommu: hwmod support and runtime PM Omar Ramirez Luna
2011-12-15  4:18 ` [PATCH v4 1/4] OMAP3: hwmod data: add mmu data for iva and isp Omar Ramirez Luna
2011-12-16  0:39   ` Felipe Contreras
2011-12-16  2:01     ` Ramirez Luna, Omar
2011-12-19 16:11       ` Felipe Contreras
2011-12-23 15:53         ` Ramirez Luna, Omar
2011-12-25 21:08           ` Laurent Pinchart
2012-01-05 19:24             ` Ramirez Luna, Omar
2012-01-07 16:12               ` Laurent Pinchart
2011-12-15  4:18 ` [PATCH v4 2/4] OMAP4: hwmod data: add mmu hwmod for ipu and dsp Omar Ramirez Luna
2011-12-15  4:18 ` [PATCH v4 3/4] OMAP3/4: iommu: migrate to hwmod framework Omar Ramirez Luna
2011-12-16  0:47   ` Felipe Contreras
2011-12-15  4:18 ` [PATCH v4 4/4] OMAP3/4: iommu: adapt to runtime pm Omar Ramirez Luna
2011-12-16  0:33   ` Felipe Contreras
2011-12-16  2:59     ` Ramirez Luna, Omar
2011-12-16  0:53   ` Felipe Contreras [this message]
2011-12-16  3:18     ` Ramirez Luna, Omar
2011-12-19 16:27       ` Felipe Contreras
2011-12-23 16:30         ` Ramirez Luna, Omar
2011-12-23 17:04           ` Felipe Contreras
2011-12-25  0:03             ` Ramirez Luna, Omar
2011-12-27  9:41               ` Felipe Contreras
2012-01-05 18:26                 ` Ramirez Luna, Omar
2011-12-17  1:39   ` Tony Lindgren

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='CAMP44s3Jb9DZLUyDVU_HmQbaJKp=2qym7Z6uauNchJh0fPL4hQ@mail.gmail.com' \
    --to=felipe.contreras@gmail.com \
    --cc=b-cousson@ti.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=khilman@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=myungjoo.ham@gmail.com \
    --cc=ohad@wizery.com \
    --cc=omar.ramirez@ti.com \
    --cc=rjw@sisk.pl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).