From: Charles Drolet <linux@cdrolet.dev>
To: devnull+b.danias.tutamail.com@kernel.org
Cc: b.danias@tutamail.com, bod@kernel.org, hansg@kernel.org,
kieran.bingham@ideasonboard.com,
laurent.pinchart@ideasonboard.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
rfoss@kernel.org, sakari.ailus@linux.intel.com,
serin.yeh@intel.com, stable@vger.kernel.org,
Charles Drolet <linux@cdrolet.dev>
Subject: Re: [PATCH 2/3] media: i2c: ov8856: Enable runtime PM before registering the sub-device
Date: Sun, 8 Nov 2026 18:45:57 -0500 [thread overview]
Message-ID: <20261108234557.12874-1-linux@cdrolet.dev> (raw)
In-Reply-To: <20261104-ov8856-pm-fixes-v1-2-1958b730ce66@tutamail.com>
This issue occurred on my Dell Latitude 7320 Detachable about one in four
times I rebooted. After applying this patch, it didn't recur during 10
reboots. I also ran a very similar patch for a couple of weeks without
seeing the issue.
Tested on Ubuntu 26.04.1 with Linux 7.4-rc1 and a patch for TPS68470
board data. BIOS: 1.48
Tested-by: Charles Drolet <linux@cdrolet.dev>
next prev parent reply other threads:[~2026-11-08 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 9:42 [PATCH 0/3] media: i2c: ov8856: Power management fixes Babis Danias
2026-11-04 9:42 ` Babis Danias via B4 Relay
2026-11-04 9:42 ` [PATCH 1/3] media: i2c: ov8856: Don't power off a suspended sensor in remove() Babis Danias
2026-11-04 9:42 ` Babis Danias via B4 Relay
2026-11-09 13:01 ` Sakari Ailus
2026-11-04 9:42 ` [PATCH 2/3] media: i2c: ov8856: Enable runtime PM before registering the sub-device Babis Danias
2026-11-04 9:42 ` Babis Danias via B4 Relay
2026-11-08 23:45 ` Charles Drolet [this message]
2026-11-09 13:04 ` Sakari Ailus
2026-11-09 13:02 ` Sakari Ailus
2026-11-04 9:42 ` [PATCH 3/3] media: i2c: ov8856: Power off the sensor during system suspend Babis Danias
2026-11-04 9:42 ` Babis Danias via B4 Relay
2026-11-06 1:53 ` Charles Drolet
2026-11-09 0:24 ` Laurent Pinchart
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=20261108234557.12874-1-linux@cdrolet.dev \
--to=linux@cdrolet.dev \
--cc=b.danias@tutamail.com \
--cc=bod@kernel.org \
--cc=devnull+b.danias.tutamail.com@kernel.org \
--cc=hansg@kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=serin.yeh@intel.com \
--cc=stable@vger.kernel.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 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.