Linux Media Controller development
 help / color / mirror / Atom feed
From: "Yan, Dongcheng" <dongcheng.yan@intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
	dave.stevenson@raspberrypi.com, hverkuil@xs4all.nl,
	ricardo.ribalda@gmail.com, bingbu.cao@linux.intel.com,
	tomi.valkeinen@ideasonboard.com, jacopo.mondi@ideasonboard.com,
	dongcheng.yan@linux.intel.com
Subject: Re: [PATCH v5] media: i2c: Add ar0234 camera sensor driver
Date: Thu, 17 Apr 2025 15:16:13 +0800	[thread overview]
Message-ID: <4a432eb3-79ba-4e8e-a7f6-c0bb0db749a9@intel.com> (raw)
In-Reply-To: <aAClUxNhOhcPl9zX@kekkonen.localdomain>

Hi Sakari,

On 4/17/2025 2:53 PM, Sakari Ailus wrote:
> Hi Dongcheng,
> 
> On Fri, Apr 11, 2025 at 12:12:49AM +0800, Dongcheng Yan wrote:
>> The driver is implemented with V4L2 framework,
>> and supports following features:
>>
>>     - manual exposure and analog/digital gain control
>>     - vblank/hblank control
>>     - vflip/hflip control
>>     - runtime PM support
>>     - 1280x960@30fps and 1920x1200@60fps support
>>     - dynamical pll_params set
>>
>> Signed-off-by: Dongcheng Yan <dongcheng.yan@intel.com>
> 
> I reviewed Laurent's ar0144 driver and it turns out that the ar0144 and
> ar0234 sensors are nearly identical in their register interface. Thus they
> could be controlled using the same driver, with relatively small changes.
> Laurent's driver programmatically sets the register values in general and
> does not rely on register lists, which is why I prefer that driver.
> 
> Would you be able to add ar0234 support to the ar0144 driver, please?

Do you mean use the ar0144 driver to support the ar0234? two sensors
share the same driver code? Or do I implement the similar
"programmatically sets the register values" in the ar0234 driver?

Thanks,
Dongcheng

> Sensor configuration independent MSRs are totally fine, I presume there are
> some the ar0234 benefits from.
> 
> My apologies for telling you this now, after 5 versions of this driver, but
> I only learned of this very recently.
> 
> I expect Laurent to send v3 of his driver by early next week.
> 


  reply	other threads:[~2025-04-17  7:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 16:12 [PATCH v5] media: i2c: Add ar0234 camera sensor driver Dongcheng Yan
2025-04-14 15:21 ` Dave Stevenson
2025-04-17  6:53 ` Sakari Ailus
2025-04-17  7:16   ` Yan, Dongcheng [this message]
2025-04-17  7:23     ` Sakari Ailus
2025-04-28  8:05   ` Yan, Dongcheng
2025-04-28 13:27     ` Dave Stevenson
  -- strict thread matches above, loose matches on Subject: below --
2025-04-10 13:29 Dongcheng Yan

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=4a432eb3-79ba-4e8e-a7f6-c0bb0db749a9@intel.com \
    --to=dongcheng.yan@intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=dongcheng.yan@linux.intel.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=ricardo.ribalda@gmail.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tomi.valkeinen@ideasonboard.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