mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: johannes.goede@oss.qualcomm.com
To: Steve Kaznak <skaznak@protonmail.com>, linux-media@vger.kernel.org
Cc: mchehab@kernel.org, sakari.ailus@linux.intel.com,
	hverkuil+cisco@kernel.org, mehdi.djait@linux.intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: ipu-bridge: Add OV01A1B sensor config
Date: Mon, 17 Aug 2026 14:55:23 +0200	[thread overview]
Message-ID: <6d0b08b4-c786-46be-bf03-ed957d52bc72@oss.qualcomm.com> (raw)
In-Reply-To: <20260815022320.728925-1-skaznak@protonmail.com>

Hi,

On 15-Aug-26 4:23 AM, Steve Kaznak wrote:
> Add the Omnivision OV01A1B (ACPI HID OVTI01AB) to the
> ipu_supported_sensors[] table, with the same single 400 MHz link
> frequency as the OV01A10 and OV01A1S entries it shares a comment with.
> 
> The sensor is the IR camera in the Dell XPS 13 Plus 9320, behind an
> Intel Vision Sensing Controller (IVSC). Commit 36eab90d3f4f ("media:
> i2c: ov01a10: Add ov01a1b support") added driver support for it, but
> without a bridge entry no fwnode graph endpoint is created, so the
> driver never binds and the camera is not enumerated.
> 
> Tested on an XPS 13 Plus 9320: the sensor binds and streams 1296x816
> Y10 at 30 fps.
> 
> Signed-off-by: Steve Kaznak <skaznak@protonmail.com>
> Reviewed-by: Mehdi Djait <mehdi.djait@linux.intel.com>

Thanks, patch looks good to me:

Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com>

Regards,

Hans

> ---
> Changes in v2:
> - Move OVTI01AB before OVTI01AS so the table stays sorted by ACPI HID,
>   and reorder the shared comment to match (Mehdi Djait)
> - Add Reviewed-by from v1
> 
> v1: https://lore.kernel.org/linux-media/20260805021154.51404-1-skaznak@protonmail.com/
> 
>  drivers/media/pci/intel/ipu-bridge.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
> index 88581a4c081d..3dde07443002 100644
> --- a/drivers/media/pci/intel/ipu-bridge.c
> +++ b/drivers/media/pci/intel/ipu-bridge.c
> @@ -73,8 +73,9 @@ static const struct ipu_sensor_config ipu_supported_sensors[] = {
>  	IPU_SENSOR_CONFIG("INT3537", 1, 437000000),
>  	/* Lontium lt6911uxe */
>  	IPU_SENSOR_CONFIG("INTC10C5", 0),
> -	/* Omnivision OV01A10 / OV01A1S */
> +	/* Omnivision OV01A10 / OV01A1B / OV01A1S */
>  	IPU_SENSOR_CONFIG("OVTI01A0", 1, 400000000),
> +	IPU_SENSOR_CONFIG("OVTI01AB", 1, 400000000),
>  	IPU_SENSOR_CONFIG("OVTI01AS", 1, 400000000),
>  	/* Omnivision OV02C10 */
>  	IPU_SENSOR_CONFIG("OVTI02C1", 1, 400000000),



      reply	other threads:[~2026-08-17 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15  2:23 Steve Kaznak
2026-08-17 12:55 ` johannes.goede [this message]

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=6d0b08b4-c786-46be-bf03-ed957d52bc72@oss.qualcomm.com \
    --to=johannes.goede@oss.qualcomm.com \
    --cc=hverkuil+cisco@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mehdi.djait@linux.intel.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=skaznak@protonmail.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

all inboxes | Powered by JetHome®