Re: atomisp current issues

[Mauro Carvalho Chehab <mchehab+huawei@kernel.org>]

Em Wed, 3 Nov 2021 16:34:39 +0200
Andy Shevchenko <andy.shevchenko@gmail.com> escreveu:

> On Wed, Nov 3, 2021 at 3:54 PM Mauro Carvalho Chehab
> <mchehab+huawei@kernel.org> wrote:
> 
> ...
> 
> > Currently, 10 video? devices are created:
> >
> >         $ for i in $(ls /dev/video*|sort -k2 -to -n); do echo -n $i:; v4l2-ctl -D -d $i|grep Name; done
> >         /dev/video0:    Name             : ATOMISP ISP CAPTURE output
> >         /dev/video1:    Name             : ATOMISP ISP VIEWFINDER output
> >         /dev/video2:    Name             : ATOMISP ISP PREVIEW output
> >         /dev/video3:    Name             : ATOMISP ISP VIDEO output
> >         /dev/video4:    Name             : ATOMISP ISP ACC
> >         /dev/video5:    Name             : ATOMISP ISP MEMORY input
> >         /dev/video6:    Name             : ATOMISP ISP CAPTURE output
> >         /dev/video7:    Name             : ATOMISP ISP VIEWFINDER output
> >         /dev/video8:    Name             : ATOMISP ISP PREVIEW output
> >         /dev/video9:    Name             : ATOMISP ISP VIDEO output
> >         /dev/video10:   Name             : ATOMISP ISP ACC
> >
> > That seems to be written to satisfy some Android-based app, but we don't
> > really need all of those.
> >
> > I'm thinking to comment out the part of the code which creates all of those,
> > keeping just "ATOMISP ISP PREVIEW output", as I don't think we need all
> > of those.  
> 
> Are they using the same microprograms (named routines) in the firmware?

More or less. There's a "run_mode" parameter that actually controls it.

Right now, one of the patches fixed it to work only in preview mode.

So, we're testing only the microprograms that are associated to it.

Regards,
Mauro