All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Vignesh R <vigneshr@ti.com>
Cc: Jyri Sarha <jsarha@ti.com>, Dave Gerlach <d-gerlach@ti.com>,
	linux-omap@vger.kernel.org, linux-pwm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pwm: pwm-tipwmss: Remove all pm_runtime gets and puts from the driver
Date: Mon, 5 Sep 2016 08:51:09 +0200	[thread overview]
Message-ID: <20160905065109.GE3532@ulmo.ba.sec> (raw)
In-Reply-To: <20160808100915.30149-1-vigneshr@ti.com>

[-- Attachment #1: Type: text/plain, Size: 769 bytes --]

On Mon, Aug 08, 2016 at 03:39:15PM +0530, Vignesh R wrote:
> From: Jyri Sarha <jsarha@ti.com>
> 
> Remove all pm_runtime gets and puts, and dummy pm_ops, from the
> pwm-tipwmss driver as there is no direct hardware access. The runtime PM
> needs to be enabled, so that the runtime PM framework takes care of
> enabling/disabling of PWMSS clock when submodules of PWMSS (ECAP or
> EHRPWM) call pm_runtime APIs. With this change PWMSS clock goes to
> idle when none of the submodules are in use.
> 
> Signed-off-by: Jyri Sarha <jsarha@ti.com>
> Signed-off-by: Vignesh R <vigneshr@ti.com>
> ---
>  drivers/pwm/pwm-tipwmss.c | 19 -------------------
>  1 file changed, 19 deletions(-)

Applied, with a slightly modified commit message.

Thanks,
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2016-09-05  6:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08 10:09 [PATCH] pwm: pwm-tipwmss: Remove all pm_runtime gets and puts from the driver Vignesh R
2016-08-08 10:09 ` Vignesh R
2016-08-30  4:48 ` Vignesh R
2016-08-30  4:48   ` Vignesh R
2016-09-05  6:51 ` Thierry Reding [this message]
2016-09-05 13:43   ` R, Vignesh

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=20160905065109.GE3532@ulmo.ba.sec \
    --to=thierry.reding@gmail.com \
    --cc=d-gerlach@ti.com \
    --cc=jsarha@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=vigneshr@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.