linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <shuah.kh@samsung.com>
To: m.chehab@samsung.com
Cc: Shuah Khan <shuah.kh@samsung.com>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	shuahkhan@gmail.com
Subject: [RFC] [PATCH 0/6] media: em28xx - power management support em28xx
Date: Fri, 21 Feb 2014 17:50:12 -0700	[thread overview]
Message-ID: <cover.1393027856.git.shuah.kh@samsung.com> (raw)

Add power management support to em28xx usb driver. This driver works in
conjunction with extensions for each of the functions on the USB device
for video/audio/dvb/remote functionality that is present on media USB
devices it supports. During suspend and resume each of these extensions
will have to do their part in suspending the components they control.

Adding suspend and resume hooks to the existing struct em28xx_ops will
enable the extensions the ability to implement suspend and resume hooks
to be called from em28xx driver. The overall approach is as follows:

-- add suspend and resume hooks to em28xx_ops
-- add suspend and resume routines to em28xx-core to invoke suspend
   and resume hooks for all registered extensions.
-- change em28xx dvb, audio, input, and video extensions to implement
   em28xx_ops: suspend and resume hooks. These hooks do what is necessary
   to suspend and resume the devices they control.

Shuah Khan (6):
  media: em28xx - add suspend/resume to em28xx_ops
  media: em28xx-audio - implement em28xx_ops: suspend/resume hooks
  media: em28xx-dvb - implement em28xx_ops: suspend/resume hooks
  media: em28xx-input - implement em28xx_ops: suspend/resume hooks
  media: em28xx-video - implement em28xx_ops: suspend/resume hooks
  media: em28xx - implement em28xx_usb_driver suspend, resume,
    reset_resume hooks

 drivers/media/usb/em28xx/em28xx-audio.c | 30 +++++++++++++++++
 drivers/media/usb/em28xx/em28xx-cards.c | 26 +++++++++++++++
 drivers/media/usb/em28xx/em28xx-core.c  | 28 ++++++++++++++++
 drivers/media/usb/em28xx/em28xx-dvb.c   | 57 +++++++++++++++++++++++++++++++++
 drivers/media/usb/em28xx/em28xx-input.c | 35 ++++++++++++++++++++
 drivers/media/usb/em28xx/em28xx-video.c | 28 ++++++++++++++++
 drivers/media/usb/em28xx/em28xx.h       |  4 +++
 7 files changed, 208 insertions(+)

-- 
1.8.3.2


             reply	other threads:[~2014-02-22  0:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22  0:50 Shuah Khan [this message]
2014-02-22  0:50 ` [RFC] [PATCH 1/6] media: em28xx - add suspend/resume to em28xx_ops Shuah Khan
2014-02-22  0:50 ` [RFC] [PATCH 2/6] media: em28xx-audio - implement em28xx_ops: suspend/resume hooks Shuah Khan
2014-02-22  0:50 ` [RFC] [PATCH 3/6] media: em28xx-dvb " Shuah Khan
2014-02-22  0:50 ` [RFC] [PATCH 4/6] media: em28xx-input " Shuah Khan
2014-03-01 13:48   ` Mauro Carvalho Chehab
2014-03-03  9:45     ` Mauro Carvalho Chehab
2014-02-22  0:50 ` [RFC] [PATCH 5/6] media: em28xx-video " Shuah Khan
2014-02-22  0:50 ` [RFC] [PATCH 6/6] media: em28xx - implement em28xx_usb_driver suspend, resume, reset_resume hooks Shuah Khan

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=cover.1393027856.git.shuah.kh@samsung.com \
    --to=shuah.kh@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=shuahkhan@gmail.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).