[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aW5RiHlkX0HGkAzT@pluto>
Date: Mon, 19 Jan 2026 15:45:12 +0000
From: Cristian Marussi <cristian.marussi@....com>
To: Jonathan Cameron <jonathan.cameron@...wei.com>
Cc: Cristian Marussi <cristian.marussi@....com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
arm-scmi@...r.kernel.org, linux-fsdevel@...r.kernel.org,
sudeep.holla@....com, james.quinlan@...adcom.com,
f.fainelli@...il.com, vincent.guittot@...aro.org,
etienne.carriere@...com, peng.fan@....nxp.com, michal.simek@....com,
dan.carpenter@...aro.org, d-gole@...com, elif.topuz@....com,
lukasz.luba@....com, philip.radford@....com,
souvik.chakravarty@....com
Subject: Re: [PATCH v2 02/17] firmware: arm_scmi: Reduce the scope of
protocols mutex
On Mon, Jan 19, 2026 at 11:21:54AM +0000, Jonathan Cameron wrote:
> On Wed, 14 Jan 2026 11:46:06 +0000
> Cristian Marussi <cristian.marussi@....com> wrote:
>
> > Currently the mutex dedicated to the protection of the list of registered
> > protocols is held during all the protocol initialization phase.
Hi Jonathan,
> >
> > Such a wide locking region is not needed and causes problem when trying to
> > initialize notifications from within a protocol initialization routine.
> >
> > Reduce the scope of the protocol mutex.
> >
> > Signed-off-by: Cristian Marussi <cristian.marussi@....com>
> I haven't checked carefully that the new scope is appropriate but
> as a change in of itself, the code is correct and clean.
> With that in mind.
I will double check after more testing.
> Reviewed-by: Jonathan Cameron <jonathan.cameron@...wei.com>
>
Thanks for having a look.
Cristian
Powered by blists - more mailing lists