From: Lukas Larson <lukaslarson@gmail.com>
To: mchehab@kernel.org
Cc: hverkuil+cisco@kernel.org, johannes.goede@oss.qualcomm.com,
sakari.ailus@linux.intel.com, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lukas Larson <lukaslarson@gmail.com>
Subject: [PATCH] media: ipu-bridge: Add upside-down sensor quirk for Dell 16 Premium DA16250
Date: Tue, 31 Mar 2026 21:01:43 +0200 [thread overview]
Message-ID: <20260331190145.11592-1-lukaslarson@gmail.com> (raw)
On the Dell 16 Premium DA16250 laptop, the camera sensor (OVTI02C1) is
mounted upside-down, resulting in a flipped image in userspace
applications.
Add this model to the upside_down_sensor_dmi_ids list to provide the
necessary 180-degree rotation quirk so the image is oriented correctly.
Signed-off-by: Lukas Larson <lukaslarson@gmail.com>
---
drivers/media/pci/intel/ipu-bridge.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
index 32cc95a766b7..ec2056c268de 100644
--- a/drivers/media/pci/intel/ipu-bridge.c
+++ b/drivers/media/pci/intel/ipu-bridge.c
@@ -104,6 +104,13 @@ static const struct ipu_sensor_config ipu_supported_sensors[] = {
* without reporting a rotation of 180° in neither the SSDB nor the _PLD.
*/
static const struct dmi_system_id upside_down_sensor_dmi_ids[] = {
+ {
+ .matches = {
+ DMI_EXACT_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
+ DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "Dell 16 Premium DA16250"),
+ },
+ .driver_data = "OVTI02C1",
+ },
{
.matches = {
DMI_EXACT_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
--
2.53.0
next reply other threads:[~2026-03-31 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 19:01 Lukas Larson [this message]
2026-04-02 16:39 ` [PATCH] media: ipu-bridge: Add upside-down sensor quirk for Dell 16 Premium DA16250 Sakari Ailus
[not found] ` <CAMCiyfoVxS_iQWVEiak+mv1i9uF2WtqMqyfCgeQyO_q5XS4LgA@mail.gmail.com>
2026-04-07 12:33 ` Sakari Ailus
2026-04-08 6:02 ` Lukas Larson
2026-04-08 11:11 ` Sakari Ailus
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=20260331190145.11592-1-lukaslarson@gmail.com \
--to=lukaslarson@gmail.com \
--cc=hverkuil+cisco@kernel.org \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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