Linux Media Controller development
 help / color / mirror / Atom feed
From: Kate Hsuan <hpa@redhat.com>
To: Miguel Vadillo <miguel.vadillo@intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: "Hans Verkuil" <hverkuil+cisco@kernel.org>,
	"Mihail Antsev" <mihail.antcev@gmail.com>,
	"José María Martín" <jmmartinf@hotmail.com>,
	"Leif Skunberg" <diamondback@cohunt.app>,
	"Samuele Angioli" <samuele.angioli@inspect.it>,
	"Ricardo Ribalda" <ribalda@chromium.org>,
	"Kees Cook" <kees@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Kate Hsuan" <hpa@redhat.com>
Subject: [PATCH v2 0/2] media: i2c: cvs: Add Lattice device quirk for VID:0x2ac1 PID:0x20d1 and resolve image upside down issue
Date: Mon,  7 Sep 2026 18:25:02 +0800	[thread overview]
Message-ID: <20260907102504.60512-1-hpa@redhat.com> (raw)

This patch series adds a Lattice device quirk for VID:0x2ac1 PID:0x20d1 to
allow intel_cvs to configure the device properly and enable the camera.
It also adds a sensor rotation quirk for Dell XPS 14 (Dell 14 Premium) DA14250
to resolve the image upside down issue.

Changes in v2:
- Add a sensor rotation quirk for Dell XPS 14 (Dell 14 Premium) DA14250
  to resolve the image upside down issue.

Kate Hsuan (2):
  media: i2c: cvs: Add Lattice device quirk for VID:0x2ac1 PID:0x20d1
  media: ipu-bridge: Add sensor rotation quirk for Dell XPS 14 (Dell 14
    Premium) DA14250

 drivers/media/i2c/cvs/core.c         | 7 +++++++
 drivers/media/pci/intel/ipu-bridge.c | 7 +++++++
 2 files changed, 14 insertions(+)

-- 
2.55.0


             reply	other threads:[~2026-09-07 10:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 10:25 Kate Hsuan [this message]
2026-09-07 10:25 ` [PATCH v2 1/2] media: i2c: cvs: Add Lattice device quirk for VID:0x2ac1 PID:0x20d1 Kate Hsuan
2026-09-07 10:25 ` [PATCH v2 2/2] media: ipu-bridge: Add sensor rotation quirk for Dell XPS 14 (Dell 14 Premium) DA14250 Kate Hsuan

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=20260907102504.60512-1-hpa@redhat.com \
    --to=hpa@redhat.com \
    --cc=diamondback@cohunt.app \
    --cc=hverkuil+cisco@kernel.org \
    --cc=jmmartinf@hotmail.com \
    --cc=johannes.goede@oss.qualcomm.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=miguel.vadillo@intel.com \
    --cc=mihail.antcev@gmail.com \
    --cc=ribalda@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=samuele.angioli@inspect.it \
    /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