linux-kernel - Re: [PATCH v3 4/7] media: platform: amd: isp4 subdev and firmware loading handling added

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: <3df6474f-ffb7-495f-b976-a380cdb40542@web.de>
Date: Tue, 2 Sep 2025 09:48:07 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Bin Du <Bin.Du@....com>, Svetoslav Stoilov <Svetoslav.Stoilov@....com>,
 linux-media@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>, Anson Tsao <anson.tsao@....com>,
 Benjamin Chan <benjamin.chan@....com>,
 Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
 Dominic Antony <Dominic.Antony@....com>,
 Gjorgji Rosikopulos <gjorgji.rosikopulos@....com>,
 Hans Verkuil <hverkuil@...all.nl>, King Li <king.li@....com>,
 Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>,
 Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
 Mario Limonciello <mario.limonciello@....com>,
 Mauro Carvalho Chehab <mchehab@...nel.org>, Phil Jawich
 <Phil.Jawich@....com>, Pratap Nirujogi <Pratap.Nirujogi@....com>,
 Richard Gong <richard.gong@....com>,
 Sakari Ailus <sakari.ailus@...ux.intel.com>,
 Sultan Alsawaf <sultan@...neltoast.com>
Subject: Re: [PATCH v3 4/7] media: platform: amd: isp4 subdev and firmware
 loading handling added

…
> states, stream configuration and mipi phy configuration. This change also
…

See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17-rc4#n94


…
> +++ b/drivers/media/platform/amd/isp4/isp4_subdev.c
> @@ -0,0 +1,1096 @@
…
> +static s32 isp4sd_fw_resp_thread_wrapper(void *context)
> +{
…
> +		mutex_lock(&thread_ctx->mutex);
> +		isp4sd_fw_resp_func(isp_subdev, stream_id);
> +		mutex_unlock(&thread_ctx->mutex);
…

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

Regards,
Markus