public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bingbu Cao <bingbu.cao@linux.intel.com>
To: Tomasz Figa <tfiga@chromium.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: "Cao, Bingbu" <bingbu.cao@intel.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"Tu, ShawnX" <shawnx.tu@intel.com>,
	"senozhatsky@chromium.org" <senozhatsky@chromium.org>,
	"Yeh, Andy" <andy.yeh@intel.com>
Subject: Re: [PATCH] media: ov5675: use group write to update digital gain
Date: Thu, 27 Jan 2022 11:14:56 +0800	[thread overview]
Message-ID: <c52bf111-41c3-4591-cc0e-1c64d7ec6e41@linux.intel.com> (raw)
In-Reply-To: <CAAFQd5CqEcLOvKsOchB29KzazAUh+hK2HWbqq+67fOhS4ydqEA@mail.gmail.com>

Sakari,

I agree with Tomasz, the group write will not cause timing issues, instead it will help
on that. So we did not need to group hold exposure and digital gain along with analog
gain. Driver can not make the policy that the exposure, a-gain and d-gain are applied
together.


On 1/11/22 12:27 PM, Tomasz Figa wrote:
> Hi Sakari,
> 
> On Mon, Jan 10, 2022 at 8:32 PM Sakari Ailus
> <sakari.ailus@linux.intel.com> wrote:
>>
>> On Wed, Dec 29, 2021 at 10:00:43AM +0000, Cao, Bingbu wrote:
>>> Hi Sakari,
>>>
>>> Thanks for your review.
>>>
>>> ________________________
>>> BRs,
>>> Bingbu Cao
>>>
>>>> -----Original Message-----
>>>> From: Sakari Ailus <sakari.ailus@linux.intel.com>
>>>> Sent: Wednesday, December 29, 2021 5:42 PM
>>>> To: Cao, Bingbu <bingbu.cao@intel.com>
>>>> Cc: linux-media@vger.kernel.org; Tu, ShawnX <shawnx.tu@intel.com>;
>>>> senozhatsky@chromium.org; tfiga@chromium.org; bingbu.cao@linux.intel.com;
>>>> Yeh, Andy <andy.yeh@intel.com>
>>>> Subject: Re: [PATCH] media: ov5675: use group write to update digital
>>>> gain
>>>>
>>>> Hi Bingbu,
>>>>
>>>> On Wed, Dec 29, 2021 at 04:57:39PM +0800, Bingbu Cao wrote:
>>>>> MWB gain register are used to set gain for each mwb channel mannually.
>>>>> However, it will involve some artifacts at low light environment as
>>>>> gain cannot be applied to each channel synchronously. Update the
>>>>> driver to use group write for digital gain to make the sure RGB
>>>>> digital gain be applied together at frame boundary.
>>>>
>>>> How about the analogue gain and exposure time?
>>>>
>>>> Shouldn't they be applied similarly as well? Adding two more writes
>>>> increases the probability of missing a frame there.
>>>
>>> We did not meet issue related to analog gain as the it was applied by only
>>> 1 reg write, it looks like same issue we found on ov8856, changing to set
>>> digital gain by only 1 global gain write will fix the problem.
>>
>> That device is different in its support for global digital gain. This patch
>> sets the gain for each component separately.
> 
> That's not what the patch does. The existing code programs the 3
> per-component registers separately. This patch made it happen under
> one write group. It doesn't increase the likelihood of the frame
> having wrong parameters - given the same timeline, before this patch,
> the frame would just have an even worse, partial gain setting, while
> with this patch it can either have the old or new gain.
> 
> Best regards,
> Tomasz
> 
>>
>> Adding more writes on a given frame increases the probability of slipping
>> to the following frame. Doing the exposure and gain updates in the same
>> group write would alleviate that a little.
>>
>>>
>>>>
>>>> This is of course a trick since the control framework doesn't really
>>>> support this, but I think this support should be added.
>>>>
>>>> --
>>>> Regards,
>>>>
>>>> Sakari Ailus
>>
>> --
>> Sakari Ailus

-- 
Best regards,
Bingbu Cao

  reply	other threads:[~2022-01-27  3:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  8:57 [PATCH] media: ov5675: use group write to update digital gain Bingbu Cao
2021-12-29  9:41 ` Sakari Ailus
2021-12-29 10:00   ` Cao, Bingbu
2022-01-10 11:32     ` Sakari Ailus
2022-01-11  3:22       ` Bingbu Cao
2022-01-11  4:27       ` Tomasz Figa
2022-01-27  3:14         ` Bingbu Cao [this message]
2022-01-28  9:42           ` 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=c52bf111-41c3-4591-cc0e-1c64d7ec6e41@linux.intel.com \
    --to=bingbu.cao@linux.intel.com \
    --cc=andy.yeh@intel.com \
    --cc=bingbu.cao@intel.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=senozhatsky@chromium.org \
    --cc=shawnx.tu@intel.com \
    --cc=tfiga@chromium.org \
    /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