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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 5 Oct 2021 15:13:32 +0900
From:   Tomasz Figa <>
To:     Steve Cho <>
Cc:     Ezequiel Garcia <>,
        "" <>,
        Alexandre Courbot <>,
        Hans Verkuil <>,
        Tzung-Bi Shih <>,
        Tiffany Lin <>,
        Andrew-CT Chen <>,
        Mauro Carvalho Chehab <>,
        Rob Herring <>,
        Matthias Brugger <>,
        Laurent Pinchart <>,
        Daniel Vetter <>,
        dri-devel <>,
        Hsin-Yi Wang <>,
        Fritz Koenig <>,
        Irui Wang <>,
        linux-media <>,
        devicetree <>,
        Linux Kernel Mailing List <>,
        linux-arm-kernel <>,
        srv_heupstream <>,
        "moderated list:ARM/Mediatek SoC support" 
Subject: Re: [PATCH v6, 00/15] Using component framework to support multi
 hardware decode

On Tue, Sep 28, 2021 at 2:02 AM Steve Cho <> wrote:
> Hi Ezequiel,
> Thank you for reviewing these series from Yunfei!
> This series is one of the main obstacles for us at the moment for MTK
> so please continue to help & support reviewing this series.
> > > According to google's suggestion, it's better not to use v4l2 async
> > > also.
> >
> > Hum? I haven't seen such objection on the mailing list.
> Maybe coming from Tzung-Bi?
> Yunfei, please let us know.

I do object to using V4L2 async. It's designed for independent
components of media pipelines, handled by multiple different drivers
and also modelled as V4L2 subdevices. We don't have anything like that

How about just open coding something trivial that only fits the needs
of this specific driver? I think it would be as simple as a linked
list and registering the V4L2 devices only after all the nodes probe.

Best regards,

Powered by blists - more mailing lists