linux-kernel - Re: [PATCH v3 2/4] media: ox05b1s: Add omnivision OX05B1S raw sensor driver

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 for Android: free password hash cracker in your pocket

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

Message-ID: <6c32c1e8-0950-4bba-ac32-3284d144b142@web.de>
Date: Mon, 3 Feb 2025 14:45:09 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Mirela Rabulea <mirela.rabulea@....com>, linux-media@...r.kernel.org,
 devicetree@...r.kernel.org, Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
 Hans Verkuil <hverkuil-cisco@...all.nl>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
 Laurentiu Palcu <laurentiu.palcu@....com>,
 Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>,
 Robert Chiras <robert.chiras@....com>,
 Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
 Alain Volmat <alain.volmat@...s.st.com>,
 Alexander Stein <alexander.stein@...tq-group.com>,
 Alice Yuan <alice.yuan@....com>, Conor Dooley <conor+dt@...nel.org>,
 Dave Stevenson <dave.stevenson@...pberrypi.com>,
 Fabio Estevam <festevam@...x.de>, Hans de Goede <hdegoede@...hat.com>,
 Julien Vuillaumier <julien.vuillaumier@....com>,
 Kieran Bingham <kieran.bingham@...asonboard.com>, LnxRevLi@....com,
 Mikhail Rudenko <mike.rudenko@...il.com>,
 Umang Jain <umang.jain@...asonboard.com>, Zhi Mao <zhi.mao@...iatek.com>
Subject: Re: [PATCH v3 2/4] media: ox05b1s: Add omnivision OX05B1S raw sensor
 driver

…
> +++ b/drivers/media/i2c/ox05b1s/ox05b1s_mipi.c
> @@ -0,0 +1,939 @@
…
> +static int ox05b1s_get_frame_desc(struct v4l2_subdev *sd, unsigned int pad,
> +				  struct v4l2_mbus_frame_desc *fd)
> +{
…
> +	/* get sensor current code*/
> +	mutex_lock(&sensor->lock);
> +	fd->entry[0].pixelcode = sensor->mode->code;
> +	mutex_unlock(&sensor->lock);
…

Under which circumstances would you become interested to apply a statement
like “guard(mutex)(&sensor->lock);”?
https://elixir.bootlin.com/linux/v6.13.1/source/include/linux/mutex.h#L201

Regards,
Markus