public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: johannes.goede@oss.qualcomm.com
To: Serin Yeh <serin.yeh@intel.com>, linux-media@vger.kernel.org
Cc: sakari.ailus@linux.intel.com, jimmy.su@intel.com, sarang.sapre@intel.com
Subject: Re: [PATCH v1] media: ipu-bridge: Add support additional link frequency
Date: Tue, 28 Apr 2026 11:29:15 +0200	[thread overview]
Message-ID: <87a8063a-bf41-49dd-bfd0-505f4284709a@oss.qualcomm.com> (raw)
In-Reply-To: <20260424021913.48020-1-serin.yeh@intel.com>

Hi,

On 24-Apr-26 04:19, Serin Yeh wrote:
> Support additional frequency 900 MHz for the OV05C10 sensor
> 
> Signed-off-by: Serin Yeh <serin.yeh@intel.com>

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, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/media/pci/intel/ipu-bridge.c b/drivers/media/pci/intel/ipu-bridge.c
> index 32cc95a766b7..f4828a691737 100644
> --- a/drivers/media/pci/intel/ipu-bridge.c
> +++ b/drivers/media/pci/intel/ipu-bridge.c
> @@ -81,7 +81,7 @@ static const struct ipu_sensor_config ipu_supported_sensors[] = {
>  	/* Omnivision OV02E10 */
>  	IPU_SENSOR_CONFIG("OVTI02E1", 1, 360000000),
>  	/* Omnivision ov05c10 */
> -	IPU_SENSOR_CONFIG("OVTI05C1", 1, 480000000),
> +	IPU_SENSOR_CONFIG("OVTI05C1", 2, 480000000, 900000000),
>  	/* Omnivision OV08A10 */
>  	IPU_SENSOR_CONFIG("OVTI08A1", 1, 500000000),
>  	/* Omnivision OV08x40 */


      reply	other threads:[~2026-04-28  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24  2:19 [PATCH v1] media: ipu-bridge: Add support additional link frequency Serin Yeh
2026-04-28  9:29 ` 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=87a8063a-bf41-49dd-bfd0-505f4284709a@oss.qualcomm.com \
    --to=johannes.goede@oss.qualcomm.com \
    --cc=jimmy.su@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sarang.sapre@intel.com \
    --cc=serin.yeh@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