From: "Krasteva, Martina" <martinax.krasteva@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, mchehab@kernel.org,
robh+dt@kernel.org, devicetree@vger.kernel.org,
daniele.alessandrelli@linux.intel.com,
paul.j.murphy@linux.intel.com,
gjorgjix.rosikopulos@linux.intel.com
Subject: Re: [PATCH v2 0/6] Camera Sensor Drivers
Date: Fri, 11 Jun 2021 10:06:00 +0100 [thread overview]
Message-ID: <747a5d78-2575-4d1e-f4c2-ae803a02a654@linux.intel.com> (raw)
In-Reply-To: <20210610212751.GJ3@paasikivi.fi.intel.com>
Hi Sakari,
Thanks for the review
On 6/10/2021 10:27 PM, Sakari Ailus wrote:
> Hi Martina,
>
> On Thu, May 27, 2021 at 03:21:39PM +0100, Martina Krasteva wrote:
>> From: Martina Krasteva <martinax.krasteva@intel.com>
>>
>> Patch series contains Sony IMX335, Sony IMX412 and OmniVision OV9282
>> camera sensor drivers and respective binding documentation.
>>
>> v1->v2:
>> - define maxItems for reset-gpios in dt binding document
>> - make sure the device is powered off on remove
>> - use pm_runtime_resume_and_get() instead of pm_runtime_get_sync()
>>
>> v1: https://patchwork.kernel.org/project/linux-media/list/?series=458115
> Thanks for the update.
>
> The patches seem fine, but I noticed one problem: the analogue gain is only
> updated when exposure is set. This is a bug.
>
> Most drivers do not try to synchronise setting analogue gain and exposure
> to the same frame. Do you need that? Alternatively the control framework
> would probably need to be amended a little --- something that would have
> other benefits, too.
Analog gain and exposure are "clustered". If I understand correctly,
when several controls are in a cluster and one/several of them are
set/get from userspace only the first control ops is called -
V4L2_CID_EXPOSURE in my case.
Analog gain can be set explicitly, exposure control ops will be called
with analog gain new value and current exp. value.
Then I could have checked the is_new flag, so I can write the reg value
just to the updated control, not to both.
In my case the userspace provides gain and exposure settings in sync so
cluster is used to mirror that behavior.
>
> I don't think that blocks merging the drivers though. But this needs to be
> addressed.
Best Regards,
Martina
next prev parent reply other threads:[~2021-06-11 9:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 14:21 [PATCH v2 0/6] Camera Sensor Drivers Martina Krasteva
2021-05-27 14:21 ` [PATCH v2 1/6] dt-bindings: media: Add bindings for imx335 Martina Krasteva
2021-06-04 20:22 ` Rob Herring
2021-05-27 14:21 ` [PATCH v2 2/6] media: i2c: Add imx335 camera sensor driver Martina Krasteva
2021-05-27 14:21 ` [PATCH v2 3/6] dt-bindings: media: Add bindings for imx412 Martina Krasteva
2021-06-04 20:23 ` Rob Herring
2021-05-27 14:21 ` [PATCH v2 4/6] media: i2c: Add imx412 camera sensor driver Martina Krasteva
2021-05-27 14:21 ` [PATCH v2 5/6] dt-bindings: media: Add bindings for ov9282 Martina Krasteva
2021-06-04 20:23 ` Rob Herring
2021-05-27 14:21 ` [PATCH v2 6/6] media: i2c: Add ov9282 camera sensor driver Martina Krasteva
2021-06-10 21:27 ` [PATCH v2 0/6] Camera Sensor Drivers Sakari Ailus
2021-06-11 9:06 ` Krasteva, Martina [this message]
2021-06-11 9:25 ` Sakari Ailus
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=747a5d78-2575-4d1e-f4c2-ae803a02a654@linux.intel.com \
--to=martinax.krasteva@linux.intel.com \
--cc=daniele.alessandrelli@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gjorgjix.rosikopulos@linux.intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=paul.j.murphy@linux.intel.com \
--cc=robh+dt@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox