mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: johannes.goede@oss.qualcomm.com
To: Leif Skunberg <diamondback@cohunt.app>,
	sakari.ailus@linux.intel.com, bingbu.cao@intel.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: ipu-bridge: Add OV5675 sensor config
Date: Tue, 10 Feb 2026 14:33:30 +0100	[thread overview]
Message-ID: <da017e6d-5048-4ab1-b3c7-3ab07c6bf0b4@oss.qualcomm.com> (raw)
In-Reply-To: <20260210094545.37918-1-diamondback@cohunt.app>

Hi,

On 10-Feb-26 10:45, Leif Skunberg wrote:
> Add the Omnivision OV5675 (ACPI HID OVTI5675) to the
> ipu_supported_sensors[] table with a link frequency of 450 MHz.
> 
> This sensor is found in the Lenovo ThinkPad X1 Fold 16 Gen 1 behind
> an Intel Vision Sensing Controller (IVSC). Without this entry the IPU
> bridge does not create the software-node fwnode graph for the sensor,
> preventing the camera from being enumerated.
> 
> Signed-off-by: Leif Skunberg <diamondback@cohunt.app>

Thanks, patch looks good to me:

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

Regards,

Hans



> ---
>  drivers/media/pci/intel/ipu-bridge.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
> index 4e579352a..170cea847 100644
> --- a/drivers/media/pci/intel/ipu-bridge.c
> +++ b/drivers/media/pci/intel/ipu-bridge.c
> @@ -88,6 +88,8 @@ static const struct ipu_sensor_config ipu_supported_sensors[] = {
>  	IPU_SENSOR_CONFIG("OVTIDB10", 1, 560000000),
>  	/* Omnivision OV2680 */
>  	IPU_SENSOR_CONFIG("OVTI2680", 1, 331200000),
> +	/* Omnivision OV5675 */
> +	IPU_SENSOR_CONFIG("OVTI5675", 1, 450000000),
>  	/* Omnivision OV8856 */
>  	IPU_SENSOR_CONFIG("OVTI8856", 3, 180000000, 360000000, 720000000),
>  	/* Toshiba T4KA3 */


      reply	other threads:[~2026-02-10 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10  8:55 [PATCH 1/2] " Leif Skunberg
2026-02-10  9:36 ` Sakari Ailus
2026-02-10  9:45 ` [PATCH v2] " Leif Skunberg
2026-02-10 13:33   ` 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=da017e6d-5048-4ab1-b3c7-3ab07c6bf0b4@oss.qualcomm.com \
    --to=johannes.goede@oss.qualcomm.com \
    --cc=bingbu.cao@intel.com \
    --cc=diamondback@cohunt.app \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.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

all inboxes | Powered by JetHome®