From: Jake Steinman <j@metarealtyinc.ca>
To: Ramshouriesh R <rshouriesh@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans de Goede <hansg@kernel.org>,
Hans Verkuil <hverkuil+cisco@kernel.org>,
Bryan O'Donoghue <bod@kernel.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Bingbu Cao <bingbu.cao@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] media: hm1092: Intel IPU (ACPI) support on top of v6
Date: Sat, 10 Oct 2026 00:59:20 -0400 [thread overview]
Message-ID: <cover.1791608336.git.j@metarealtyinc.ca> (raw)
In-Reply-To: <20260801-hm1092-driver-v6-0-5979f223748a@gmail.com>
Hi Ramshouriesh, Sakari,
These two patches make the HM1092 usable on Intel IPU laptops, where the
sensor is described in ACPI as HIMX1092. They apply on top of
"[PATCH v6 0/2] media: Add Himax HM1092 mono NIR sensor driver".
Patch 1 is for the sensor driver. v6 cannot bind on x86: there is no
ACPI match table, the 19.2 MHz clock these machines supply is rejected,
and the only mode is the 24 MHz one. The patch selects the configuration
from the clock rate and adds the 19.2 MHz / 648x368 / 180.48 MHz one.
The 24 MHz path is functionally unchanged. Ramshouriesh, feel free to
fold it into a v7 if you prefer that to a follow-up.
Patch 2 is independent of the sensor. The IPU7 capture nodes have no
pixel format for MEDIA_BUS_FMT_Y10_1X10, so no monochrome sensor can be
captured, whatever its driver.
Tested together on a Dell XPS 16 DA16260 (Panther Lake), kernel
7.3-rc5, with the ipu-bridge entry that is already in media/next:
intel_ipu7_isys.isys intel_ipu7.isys.40: bind hm1092 17-0024 nlanes is 1 port is 2
link_frequency 180480000
pixel_rate 36096000
exposure min=2 max=719 default=360
Y10 648x368, 1344 bytes per line, 10 frames, 4945920 bytes
Y10P 648x368, 832 bytes per line, 10 frames, 3061760 bytes
exposure 100: mean level 59
exposure 700: mean level 198
Two things worth knowing when reviewing patch 1:
- The 19.2 MHz configuration reads X 0..1293 and Y 0..733, which is the
full 1296x736 array including the dummy border. That is what the
vendor sequence programs, so the crop rectangle reports it as is, and
it lies outside the 1280x720 crop bounds v6 defines. I left the
bounds alone. Say if you would rather have them widened.
- The 24 MHz configuration is compile-tested only here. I have no
devicetree hardware with this sensor.
Regards,
Jake
Jake Steinman (2):
media: i2c: hm1092: Add ACPI enumeration and the 19.2 MHz
configuration
media: staging/ipu7: Add 10-bit greyscale capture formats
drivers/media/i2c/hm1092.c | 363 ++++++++++++++++---
drivers/staging/media/ipu7/ipu7-isys-video.c | 4 +
2 files changed, 321 insertions(+), 46 deletions(-)
--
2.56.0
next prev parent reply other threads:[~2026-10-10 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 12:54 [PATCH v6 0/2] media: Add Himax HM1092 mono NIR sensor driver Ramshouriesh R
2026-08-01 12:54 ` [PATCH v6 1/2] media: dt-bindings: Add Himax HM1092 NIR sensor Ramshouriesh R
2026-08-01 12:54 ` [PATCH v6 2/2] media: i2c: hm1092: add Himax HM1092 mono NIR sensor driver Ramshouriesh R
2026-10-10 4:59 ` Jake Steinman [this message]
2026-10-10 4:59 ` [PATCH 1/2] media: i2c: hm1092: Add ACPI enumeration and the 19.2 MHz configuration Jake Steinman
2026-10-10 9:15 ` Eduard Kulyk
2026-10-10 4:59 ` [PATCH 2/2] media: staging/ipu7: Add 10-bit greyscale capture formats Jake Steinman
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.1791608336.git.j@metarealtyinc.ca \
--to=j@metarealtyinc.ca \
--cc=bingbu.cao@intel.com \
--cc=bod@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=hverkuil+cisco@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=rshouriesh@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=vladimir.zapolskiy@linaro.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
all inboxes | Powered by JetHome®