All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Maurizio Casciano <mauriziocasciano7@gmail.com>
Cc: mchehab@kernel.org, linux-media@vger.kernel.org,
	sakari.ailus@linux.intel.com, bingbu.cao@amd.com,
	jacopo.mondi@ideasonboard.com, nicholas@rothemail.net,
	andy@kernel.org, hansg@kernel.org, gregkh@linuxfoundation.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 00/16] media: Add Yoga Book camera support
Date: Wed, 2 Sep 2026 16:27:55 +0300	[thread overview]
Message-ID: <apgkWxmlYyWFfHjT@ashevche-desk.local> (raw)
In-Reply-To: <cover.1788286339.git.mauriziocasciano7@gmail.com>

On Tue, Sep 01, 2026 at 09:04:22PM +0200, Maurizio Casciano wrote:
> Hi,
> 
> This series adds the sensor, bridge, AtomISP and lens-actuator support
> needed by the front and rear cameras of the Lenovo Yoga Book YB1-X91.
> 
> It covers the OV8858 19.2 MHz clock and Cherry Trail gain programming,
> OV2740 288 MHz link frequency and manual white balance, firmware IDs and
> IPU bridge data, AtomISP raw capture and CSI-2 timing, and the WV517S lens
> actuator.
> 
> Changes in v6:
> - In patch 2, replace the arithmetic MHz expressions with direct Hz
>   constants, as requested by Andy Shevchenko.
> - Give the supported input clocks distinct names:
>   OV8858_XVCLK_FREQ_24MHZ and OV8858_XVCLK_FREQ_19_2MHZ.
> - No other code changes from v5.
> 
> Validation:
> - Strict checkpatch over all 16 patches: no errors or warnings.
> - W=1 object build of drivers/media/i2c/ov8858.o.
> - Sparse C=2 check of drivers/media/i2c/ov8858.c.

> - Front and rear cameras previously validated on the Yoga Book with real
>   raw Bayer capture.

Can you confirm it still works? Because word 'previously' makes me a bit
worrying. In v7 it might be even more changes, so please make sure it still
works as expected.

-- 
With Best Regards,
Andy Shevchenko



      parent reply	other threads:[~2026-09-02 13:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 19:04 [PATCH v6 00/16] media: Add Yoga Book camera support Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 01/16] media: ov8858: Extract digital gain programming Maurizio Casciano
2026-09-01 22:16   ` Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 02/16] media: ov8858: support 19.2 MHz clock and CHT gain setup Maurizio Casciano
2026-09-02 10:33   ` Sakari Ailus
2026-09-02 13:13     ` Andy Shevchenko
2026-09-01 19:04 ` [PATCH v6 03/16] media: ov2740: Use C99 initializers for ACPI IDs Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 04/16] media: ov2740: Add OVTI2740 ACPI ID Maurizio Casciano
2026-09-01 22:17   ` Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 05/16] media: ov8858: Add INT3477 " Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 06/16] media: intel: ipu-bridge: Add Yoga Book camera sensors Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 07/16] media: atomisp: Add Yoga Book camera configuration Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 08/16] media: ov2740: support 288 MHz link frequency Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 09/16] media: intel: ipu-bridge: allow sensor-specific link frequencies Maurizio Casciano
2026-09-01 22:21   ` Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 10/16] media: atomisp: derive CSI-2 timing from sensor link frequency Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 11/16] media: atomisp: provide Yoga Book OV2740 " Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 12/16] media: ov2740: release group hold after gain write errors Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 13/16] media: ov2740: add manual white balance controls Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 14/16] media: atomisp: Use struct v4l2_area for padding Maurizio Casciano
2026-09-03  4:38   ` Andy Shevchenko
2026-09-01 19:04 ` [PATCH v6 15/16] media: atomisp: allow raw Bayer capture Maurizio Casciano
2026-09-01 19:04 ` [PATCH v6 16/16] media: i2c: Add WV517S lens actuator driver Maurizio Casciano
2026-09-02 13:27 ` Andy Shevchenko [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=apgkWxmlYyWFfHjT@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=bingbu.cao@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mauriziocasciano7@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=nicholas@rothemail.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.