Hi Dan, On Thu, Apr 7, 2022 at 9:27 PM Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote: > > On Thu, Apr 07, 2022 at 09:17:38PM +0800, Kate Hsuan wrote: > > Hi Dan, > > > > On Thu, Apr 7, 2022 at 7:52 PM Dan Carpenter <dan.carpenter@xxxxxxxxxx> wrote: > > > > > > On Thu, Apr 07, 2022 at 06:57:24PM +0800, Kate Hsuan wrote: > > > > A not calibrated x_start setting would result in an incorrect AWB location > > > > configuration on a sensor when only the rightmost stripe is used. x_start > > > > should be calibrated by subtracting the stripe offset to set the coordinate > > > > to the correct position on the second stripe. > > > > > > > > > > > > I wish the commit description said more about what the bug looks like to > > > the user. This is the front facing camera, right? Is part of the video > > > blank or what's the deal? > > > > This is IPU3 image processor. I tried to fix the configuration issues > > on stripe 1 coordinate settings. > > > > So in terms of users, if you configure it in a certain way then it > crashes? What happens in terms of what the ordinary user sees? > It will not crash. Currently, application, such as libcamara only uses stripe 0 to estimate 3A (AE AWB AF). The grid coordinate can be used to determine the area on a sensor where we use this area to determine the 3A status. If we start to move the grid and it crosses the stripe 1 offset. The grid will be at the rightmost edge of the sensor. The user may only feel the location of AF, AWB, AE of the image is not the user's expectation. I'll update them in the v3 patch. > regards, > dan carpenter > -- BR, Kate