linux-kernel - Re: atomisp current issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20211103165913.221f1ef1@sal.lan>
Date:   Wed, 3 Nov 2021 16:59:13 +0000
From:   Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Linux Media Mailing List <linux-media@...r.kernel.org>,
        Tsuchiya Yuto <kitakar@...il.com>,
        Hans de Goede <hdegoede@...hat.com>,
        Patrik Gfeller <patrik.gfeller@...il.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Sakari Ailus <sakari.ailus@...ux.intel.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Hans Verkuil <hverkuil-cisco@...all.nl>,
        Kaixu Xia <kaixuxia@...cent.com>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Yang Li <abaci-bugfix@...ux.alibaba.com>,
        Tomi Valkeinen <tomi.valkeinen@...asonboard.com>,
        Alex Dewar <alex.dewar90@...il.com>,
        Aline Santana Cordeiro <alinesantanacordeiro@...il.com>,
        Arnd Bergmann <arnd@...db.de>, Alan <alan@...ux.intel.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...nel.org>, linux-staging@...ts.linux.dev,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: atomisp current issues

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

> On Wed, Nov 3, 2021 at 3:54 PM Mauro Carvalho Chehab
> <mchehab+huawei@...nel.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