dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Arto Merilainen <amerilainen@nvidia.com>
To: tbergstrom@nvidia.com, treding@nvidia.com
Cc: linux-tegra@vger.kernel.org, mkulkarni@nvidia.com,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	amerilainen@nvidia.com
Subject: [PATCHv3 0/4] gpu: host1x: Add runtime pm support
Date: Tue, 24 Sep 2013 15:05:21 +0300	[thread overview]
Message-ID: <1380024325-18280-1-git-send-email-amerilainen@nvidia.com> (raw)

This series adds runtime pm support for host1x, gr2d and dc. It retains the
current behaviour if CONFIG_PM_RUNTIME is not enabled.

The gr2d clock is enabled when a new job is submitted and disabled when
the work is done. Due to parent->child relations between host1x->gr2d, this
scheme enables and disables host1x clock.

For dc, the clocks are enabled in .probe and disabled in .remove via runtime
pm instead of direct clock APIs.

Mayuresh is unfortunately not available to continue with the series and hence
I will continue working on the patches.

Changes in v3:
- Rebased patches on top of 3.12-rc2
- Removed unnecessary #ifdefs
- Added descriptions to commit messages
- If runtime pm is disabled, the code calls suspend/resume functions
for enabling/disabling the clocks instead of repeating the functions

Mayuresh Kulkarni (4):
  gpu: host1x: shuffle job APIs
  drm/tegra: Add runtime pm support for gr2d
  drm/tegra: Add runtime pm support for dc
  gpu: host1x: Add runtime pm support for host1x

 drivers/gpu/host1x/cdma.c     |  2 ++
 drivers/gpu/host1x/channel.c  |  8 ------
 drivers/gpu/host1x/channel.h  |  1 -
 drivers/gpu/host1x/dev.c      | 57 +++++++++++++++++++++++++++++++++++++++---
 drivers/gpu/host1x/drm/dc.c   | 58 +++++++++++++++++++++++++++++++++++++++----
 drivers/gpu/host1x/drm/gr2d.c | 57 ++++++++++++++++++++++++++++++++++++++----
 drivers/gpu/host1x/job.c      | 13 ++++++++++
 drivers/gpu/host1x/job.h      |  3 +++
 8 files changed, 176 insertions(+), 23 deletions(-)

-- 
1.8.1.5

             reply	other threads:[~2013-09-24 12:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 12:05 Arto Merilainen [this message]
     [not found] ` <1380024325-18280-1-git-send-email-amerilainen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-09-24 12:05   ` [PATCHv3 1/4] gpu: host1x: shuffle job APIs Arto Merilainen
2013-09-24 12:05 ` [PATCHv3 2/4] drm/tegra: Add runtime pm support for gr2d Arto Merilainen
     [not found]   ` <1380024325-18280-3-git-send-email-amerilainen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-01 18:14     ` Stephen Warren
     [not found]       ` <524B10F0.7000301-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-10-02  5:40         ` Arto Merilainen
2013-09-24 12:05 ` [PATCHv3 3/4] drm/tegra: Add runtime pm support for dc Arto Merilainen
2013-09-24 12:05 ` [PATCHv3 4/4] gpu: host1x: Add runtime pm support for host1x Arto Merilainen
     [not found]   ` <1380024325-18280-5-git-send-email-amerilainen-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-10-01 18:17     ` Stephen Warren
     [not found]       ` <524B11AA.30400-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-10-02  5:40         ` Arto Merilainen

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=1380024325-18280-1-git-send-email-amerilainen@nvidia.com \
    --to=amerilainen@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkulkarni@nvidia.com \
    --cc=tbergstrom@nvidia.com \
    --cc=treding@nvidia.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).