[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230903124620.6yrnpbpj37on6wih@zenone.zhora.eu>
Date: Sun, 3 Sep 2023 14:46:20 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Sean Nyekjaer <sean@...nix.com>
Cc: Pierre-Yves MORDRET <pierre-yves.mordret@...s.st.com>,
Alain Volmat <alain.volmat@...s.st.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
linux-i2c@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] i2c: stm32f7: Add atomic_xfer method to driver
Hi Pierre-Yves, Alain,
mind taking a look here?
[...]
> @@ -357,6 +357,7 @@ struct stm32f7_i2c_dev {
> u32 dnf_dt;
> u32 dnf;
> struct stm32f7_i2c_alert *alert;
> + bool atomic;
this smells a bit racy here, this works only if the xfer's are
always sequential.
What happens when we receive at the same time two xfer's, one
atomic and one non atomic?
Andi
Powered by blists - more mailing lists