public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bingbu Cao <bingbu.cao@intel.com>
To: linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	rafael@kernel.org
Cc: shawnx.tu@intel.com, chiranjeevi.rapolu@intel.com,
	tfiga@chromium.org, senozhatsky@chromium.org,
	linux-kernel@vger.kernel.org, bingbu.cao@linux.intel.com
Subject: [PATCH v2 0/6] Support device probe in non-zero ACPI D state
Date: Wed, 15 Dec 2021 19:08:57 +0800	[thread overview]
Message-ID: <1639566543-8561-1-git-send-email-bingbu.cao@intel.com> (raw)

In many use cases where the chip is part of a camera module, and the camera
module is wired together with a privacy LED, powering on the device during
probe will cause the LED blink, it is undesireable as the privacy LED concern.

Sakari's change - 
https://lore.kernel.org/lkml/20211018121729.6357-1-sakari.ailus@linux.intel.com/
which add the support device probe in non-zero ACPI D state.

This following patch add support probe in non-zero ACPI D state for more camera
sensors: ov2740, ov5670, ov5675, ov8856, imx208 and hi556.

--

This patch series is based on linux-next branch of Rafael J. Wysocki's
linux-pm git repository:
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git

--

Bingbu Cao (5):
  media: ov8856: support device probe in non-zero ACPI D state
  media: ov2740: support device probe in non-zero ACPI D state
  media: imx208: Support device probe in non-zero ACPI D state
  media: ov5675: Support device probe in non-zero ACPI D state
  media: hi556: Support device probe in non-zero ACPI D state

Sakari Ailus (1):
  media: ov5670: Support device probe in non-zero ACPI D state

 drivers/media/i2c/hi556.c  |  70 +++++++++++++-------
 drivers/media/i2c/imx208.c |  82 +++++++++++++++--------
 drivers/media/i2c/ov2740.c |  69 ++++++++++++-------
 drivers/media/i2c/ov5670.c |  78 +++++++++++++---------
 drivers/media/i2c/ov5675.c |  71 +++++++++++++-------
 drivers/media/i2c/ov8856.c | 162 +++++++++++++++++++++++++--------------------
 6 files changed, 324 insertions(+), 208 deletions(-)

-- 
2.7.4


             reply	other threads:[~2021-12-15 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 11:08 Bingbu Cao [this message]
2021-12-15 11:08 ` [PATCH v2 1/6] media: ov8856: support device probe in non-zero ACPI D state Bingbu Cao
2021-12-15 11:08 ` [PATCH v2 2/6] media: ov5670: Support " Bingbu Cao
2021-12-15 11:09 ` [PATCH v2 3/6] media: ov2740: support " Bingbu Cao
2021-12-15 11:09 ` [PATCH v2 4/6] media: imx208: Support " Bingbu Cao
2021-12-15 11:09 ` [PATCH v2 5/6] media: ov5675: " Bingbu Cao
2021-12-15 11:09 ` [PATCH v2 6/6] media: hi556: " Bingbu Cao

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=1639566543-8561-1-git-send-email-bingbu.cao@intel.com \
    --to=bingbu.cao@intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=chiranjeevi.rapolu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=senozhatsky@chromium.org \
    --cc=shawnx.tu@intel.com \
    --cc=tfiga@chromium.org \
    /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