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
| ||
|
Date: Tue, 22 Sep 2020 11:47:47 +0300 From: Sakari Ailus <sakari.ailus@....fi> To: Luca Ceresoli <luca@...aceresoli.net> Cc: Sowjanya Komatineni <skomatineni@...dia.com>, thierry.reding@...il.com, jonathanh@...dia.com, hverkuil@...all.nl, jacopo+renesas@...ndi.org, leonl@...pardimaging.com, robh+dt@...nel.org, lgirdwood@...il.com, broonie@...nel.org, linux-media@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v6 2/3] media: i2c: imx274: Remove stop stream i2c writes during remove Hi Luca, On Tue, Sep 22, 2020 at 10:09:33AM +0200, Luca Ceresoli wrote: > Hi, > > On 21/09/20 23:39, Sowjanya Komatineni wrote: > > Sensor should already be in standby during remove and there is no > > need to configure sensor registers for stream stop. > > I beg your pardon for the newbie question: does the V4L2 framework > guarantee that the stream is stopped (.s_stream(..., 0)) before removing > the driver? It doesn't. That's however one of the lesser concerns, and I don't think it'd help if drivers tried to prepare for that. -- Sakari Ailus
Powered by blists - more mailing lists