public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>,
	bingbu.cao@intel.com, dave.stevenson@raspberrypi.com,
	linux-media@vger.kernel.org, sakari.ailus@linux.intel.com,
	tomi.valkeinen@ideasonboard.com
Subject: Re: [PATCH v2] media: i2c: add ov01a10 image sensor driver
Date: Sun, 23 Apr 2023 10:59:27 +0800	[thread overview]
Message-ID: <2ff1a677-256a-b77b-c0b2-d2aa075738af@linux.intel.com> (raw)
In-Reply-To: <168199174036.2445904.14561161009082027354@Monstersaurus>

Kieran,

Thanks for your review.

On 4/20/23 7:55 PM, Kieran Bingham wrote:
> Hi Bingbu,
> 
> Running this through my sensor driver check script still highlights some
> missing features:
> 
> Selection Controls and fwnode properties (will become mandatory):
>  - V4L2_SEL_TGT_CROP_DEFAULT       : --------
>  - V4L2_SEL_TGT_CROP               : --------
>  - V4L2_SEL_TGT_CROP_BOUNDS        : --------
>  - .get_selection                  : --------
>  - v4l2_ctrl_new_fwnode_properties : found
> 
> Could you consider adding these controls please?

Yes, I will add them in v3.

> 
> Please see https://git.libcamera.org/libcamera/libcamera.git/tree/Documentation/sensor_driver_requirements.rst#n77:
> 
> The sensor driver should implement support for the V4L2 Selection API,
> specifically it should implement support for the
> `VIDIOC_SUBDEV_G_SELECTION` ioctl with support for the following selection
> targets:
> 
> .. VIDIOC_SUBDEV_G_SELECTION:
> 
> * `V4L2_SEL_TGT_CROP_BOUNDS` to report the readable pixel array area size
> * `V4L2_SEL_TGT_CROP_DEFAULT` to report the active pixel array area size
> * `V4L2_SEL_TGT_CROP` to report the analogue selection rectangle
> 
> - https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/vidioc-subdev-g-selection.html
> - https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/v4l2-selection-targets.html
> 
> --
> Regards
> 
> Kieran
> 
> 
> Quoting bingbu.cao@intel.com (2023-04-20 05:22:13)
>> From: Bingbu Cao <bingbu.cao@intel.com>
>>
>> Add v4l2 device driver for OmniVision ov01a10 image sensor, ov01a10
>> image sensor can deliver 1280x800 resolution BGGR10 images at 60 fps.
>>
>> Signed-off-by: Bingbu Cao <bingbu.cao@intel.com>
>> Signed-off-by: Yating Wang <yating.wang@intel.com>
>> ---
>> Changes from v1:
>>  - Create ORIENTATION and ROTATION controls if fwnode properties exists
>>  - Move sensor PLL related settings into mipi_data_rate_720mbps[]
>>  - Use v4l2 subdev active state API and remove private mutex
>>  - Add support for vertical and horizontal flip v4l2 control
>>  - Update the copyright header comment format
>>  - Remove some unused macros
>>  - Add entry in MAINTAINERS
>>
>> ---

..snip..

-- 
Best regards,
Bingbu Cao

      reply	other threads:[~2023-04-23  2:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-20  4:22 [PATCH v2] media: i2c: add ov01a10 image sensor driver bingbu.cao
2023-04-20  6:19 ` kernel test robot
2023-04-20 11:55 ` Kieran Bingham
2023-04-23  2:59   ` Bingbu Cao [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=2ff1a677-256a-b77b-c0b2-d2aa075738af@linux.intel.com \
    --to=bingbu.cao@linux.intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --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