mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bryan O'Donoghue <bod@kernel.org>,
	Hans de Goede <hansg@kernel.org>
Cc: Jingjing Xiong <jingjing.xiong@intel.com>,
	Hao Yao <hao.yao@intel.com>, Jim Lai <jim.lai@intel.com>,
	You-Sheng Yang <vicamo.yang@canonical.com>,
	Alan Stern <stern@rowland.harvard.edu>,
	Hans de Goede <hdegoede@redhat.com>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] media: i2c: ov02e10: add OV02E10 image sensor driver
Date: Fri, 18 Apr 2025 18:24:03 +0200	[thread overview]
Message-ID: <1d88dd72-8c5d-459a-b681-6a44d32e93df@ixit.cz> (raw)
In-Reply-To: <20250407-b4-media-comitters-next-25-03-13-ov02e10-v4-2-211e3e6fae90@linaro.org>

Tested-by: David Heidelberg <david@ixit.cz>  # Dell Latitude 9440 2024

Thank you!
David

On 07/04/2025 11:13, Bryan O'Donoghue wrote:
> From: Jingjing Xiong <jingjing.xiong@intel.com>
> 
> Add in the ov02e10 driver from the Intel IPU6 repository.
> 
> Changelog to IPU6 incoming driver:
> 
> - handhake GPIO
>    The IPU6 handshake GPIO signals to the FPGA on IPU6/IPU7 laptops and as
>    such is not a sensor signal.
> 
>    Hans has a proposal for handling those GPIOs below. Dropf from the
>    incoming sensor driver.
> 
>    Link: https://lore.kernel.org/linux-media/4b87a956-a767-48dc-b98b-f80d9a44adc8@redhat.com
> 
> - Regulators
>    Change to regulator_bulk API to capture the full range of rails to the
>    o02e10 sensor.
> 
>    This will work for ACPI systems which only have the avdd rail available
>    as missing rails won't fail the regulator_bulk_* function calls.
> 
>    Convert the existing avdd single rail to regulator_bulk API.
> 
> - Clocks
> 
>    Move the MCLK validation logic to check_hwcfg() and move check_hwcfg()
>    to after devm_kzalloc() so that we can pass a struct ov02e pointer to
>    check_hwcfg() to begin to enumerate that structure.
> 
>    Reworks MCLK clock get logic to facilitate OF
> 
> - Power on/off
> 
>    Implement specification on and off delays on power-up
> 
>    The ov02e10 specification says for power-on:
> 
>    t3 = the time between dvdd stable and XSHUTDOWN deassert
>    t5 = the time between XSHUTDOWN deassert and SCCB ready
> 
>    The power-off path in the spec shows no required delays between XSHUTDOWN
>    and power-rail shut off but, if the reset GPIO is not defined no action is
>    taken to change its logical state.
> 
> - Remove dev_dbg() and extra dev_err()
> 
>    Several instances of dev_dbg() and dev_err() were removed.
>    dev_xxx() calls common in development can be stripped away for upstream.
> 
>    We have multiple on-list tests for this code on X86 and Arm so most of
>    the verbose dev_xxx() calls are redundant now.
> 
> - Add OF probe support
> 
>    Simple addition of ovti,0v02e10 compat string and associated resource
>    structure entry.
> 
> - Extend MODULE_AUTHOR list
>    Adds Hans, Alan and myself
> 
> - Conversion to v4l2 subdevice-state
> 
> - Added HFLIP and VFLIP support
> 
> Signed-off-by: Jingjing Xiong <jingjing.xiong@intel.com>
> Co-developed-by: Hao Yao <hao.yao@intel.com>
> Signed-off-by: Hao Yao <hao.yao@intel.com>
> Co-developed-by: Jim Lai <jim.lai@intel.com>
> Signed-off-by: Jim Lai <jim.lai@intel.com>
> Co-developed-by: You-Sheng Yang <vicamo.yang@canonical.com>
> Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>
> Co-developed-by: Alan Stern <stern@rowland.harvard.edu>
> Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> Co-developed-by: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> ---
>   MAINTAINERS                 |   9 +
>   drivers/media/i2c/Kconfig   |  10 +
>   drivers/media/i2c/Makefile  |   1 +
>   drivers/media/i2c/ov02e10.c | 969 ++++++++++++++++++++++++++++++++++++++++++++
>   4 files changed, 989 insertions(+)
> 

      parent reply	other threads:[~2025-04-18 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  9:13 [PATCH v4 0/2] Import IPU6 ov02e10 sensor driver and enable OF usage of it Bryan O'Donoghue
2025-04-07  9:13 ` [PATCH v4 1/2] media: dt-bindings: Add OmniVision OV02E10 Bryan O'Donoghue
2025-04-07  9:13 ` [PATCH v4 2/2] media: i2c: ov02e10: add OV02E10 image sensor driver Bryan O'Donoghue
2025-04-15 12:14   ` Sakari Ailus
2025-04-15 12:16   ` Sakari Ailus
2025-04-18 16:24   ` David Heidelberg [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=1d88dd72-8c5d-459a-b681-6a44d32e93df@ixit.cz \
    --to=david@ixit.cz \
    --cc=bod@kernel.org \
    --cc=broonie@kernel.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hansg@kernel.org \
    --cc=hao.yao@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=jim.lai@intel.com \
    --cc=jingjing.xiong@intel.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=stern@rowland.harvard.edu \
    --cc=vicamo.yang@canonical.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®