From: Andi Shyti <andi.shyti@kernel.org>
To: Sean Nyekjaer <sean@geanix.com>
Cc: Pierre-Yves MORDRET <pierre-yves.mordret@foss.st.com>,
Alain Volmat <alain.volmat@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-i2c@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] i2c: stm32f7: Add atomic_xfer method to driver
Date: Wed, 26 Jul 2023 23:21:32 +0200 [thread overview]
Message-ID: <20230726212132.vylu6qulpyu5fndh@intel.intel> (raw)
In-Reply-To: <20230718105435.2641207-1-sean@geanix.com>
Hi Sean,
[...]
> @@ -905,38 +906,43 @@ static void stm32f7_i2c_xfer_msg(struct stm32f7_i2c_dev *i2c_dev,
> cr2 |= STM32F7_I2C_CR2_NBYTES(f7_msg->count);
> }
>
> - /* Enable NACK, STOP, error and transfer complete interrupts */
> - cr1 |= STM32F7_I2C_CR1_ERRIE | STM32F7_I2C_CR1_TCIE |
> - STM32F7_I2C_CR1_STOPIE | STM32F7_I2C_CR1_NACKIE;
> -
> - /* Clear DMA req and TX/RX interrupt */
> - cr1 &= ~(STM32F7_I2C_CR1_RXIE | STM32F7_I2C_CR1_TXIE |
> - STM32F7_I2C_CR1_RXDMAEN | STM32F7_I2C_CR1_TXDMAEN);
> -
> - /* Configure DMA or enable RX/TX interrupt */
> - i2c_dev->use_dma = false;
> - if (i2c_dev->dma && f7_msg->count >= STM32F7_I2C_DMA_LEN_MIN) {
> - ret = stm32_i2c_prep_dma_xfer(i2c_dev->dev, i2c_dev->dma,
> - msg->flags & I2C_M_RD,
> - f7_msg->count, f7_msg->buf,
> - stm32f7_i2c_dma_callback,
> - i2c_dev);
> - if (!ret)
> - i2c_dev->use_dma = true;
> - else
> - dev_warn(i2c_dev->dev, "can't use DMA\n");
> - }
> + if (!i2c_dev->atomic) {
> + /* Enable NACK, STOP, error and transfer complete interrupts */
> + cr1 |= STM32F7_I2C_CR1_ERRIE | STM32F7_I2C_CR1_TCIE |
> + STM32F7_I2C_CR1_STOPIE | STM32F7_I2C_CR1_NACKIE;
> +
> + /* Clear DMA req and TX/RX interrupt */
> + cr1 &= ~(STM32F7_I2C_CR1_RXIE | STM32F7_I2C_CR1_TXIE |
> + STM32F7_I2C_CR1_RXDMAEN | STM32F7_I2C_CR1_TXDMAEN);
> +
> + /* Configure DMA or enable RX/TX interrupt */
> + i2c_dev->use_dma = false;
> + if (i2c_dev->dma && f7_msg->count >= STM32F7_I2C_DMA_LEN_MIN) {
> + ret = stm32_i2c_prep_dma_xfer(i2c_dev->dev, i2c_dev->dma,
> + msg->flags & I2C_M_RD,
> + f7_msg->count, f7_msg->buf,
> + stm32f7_i2c_dma_callback,
> + i2c_dev);
> + if (!ret)
> + i2c_dev->use_dma = true;
> + else
> + dev_warn(i2c_dev->dev, "can't use DMA\n");
> + }
>
> - if (!i2c_dev->use_dma) {
> - if (msg->flags & I2C_M_RD)
> - cr1 |= STM32F7_I2C_CR1_RXIE;
> - else
> - cr1 |= STM32F7_I2C_CR1_TXIE;
> + if (!i2c_dev->use_dma) {
> + if (msg->flags & I2C_M_RD)
> + cr1 |= STM32F7_I2C_CR1_RXIE;
> + else
> + cr1 |= STM32F7_I2C_CR1_TXIE;
> + } else {
> + if (msg->flags & I2C_M_RD)
> + cr1 |= STM32F7_I2C_CR1_RXDMAEN;
> + else
> + cr1 |= STM32F7_I2C_CR1_TXDMAEN;
> + }
> } else {
> - if (msg->flags & I2C_M_RD)
> - cr1 |= STM32F7_I2C_CR1_RXDMAEN;
> - else
> - cr1 |= STM32F7_I2C_CR1_TXDMAEN;
> + /* Disable all interrupts */
> + cr1 &= ~STM32F7_I2C_ALL_IRQ_MASK;
if you do
if (i2c_dev->atomic) {
/* Disable all interrupts */
cr1 &= ~STM32F7_I2C_ALL_IRQ_MASK;
return;
}
you save all the above from a leveel of indentation.
> }
>
> /* Configure Start/Repeated Start */
> @@ -1670,7 +1676,22 @@ static irqreturn_t stm32f7_i2c_isr_error(int irq, void *data)
> return IRQ_HANDLED;
> }
>
> -static int stm32f7_i2c_xfer(struct i2c_adapter *i2c_adap,
> +static int stm32f7_i2c_wait_polling(struct stm32f7_i2c_dev *i2c_dev)
> +{
> + ktime_t timeout = ktime_add_ms(ktime_get(), i2c_dev->adap.timeout);
> +
> + while (ktime_compare(ktime_get(), timeout) < 0) {
> + udelay(5);
> + stm32f7_i2c_isr_event(0, i2c_dev);
> +
> + if (try_wait_for_completion(&i2c_dev->complete))
> + return 1;
I'm wondering if it makes really sense to have a complete() and
wait_for_completion() scheme here.
> + }
> +
> + return 0;
> +}
> +
> +static int stm32f7_i2c_xfer_core(struct i2c_adapter *i2c_adap,
> struct i2c_msg msgs[], int num)
> {
> struct stm32f7_i2c_dev *i2c_dev = i2c_get_adapdata(i2c_adap);
> @@ -1694,8 +1715,13 @@ static int stm32f7_i2c_xfer(struct i2c_adapter *i2c_adap,
>
> stm32f7_i2c_xfer_msg(i2c_dev, msgs);
>
> - time_left = wait_for_completion_timeout(&i2c_dev->complete,
> - i2c_dev->adap.timeout);
> + if (!i2c_dev->atomic) {
> + time_left = wait_for_completion_timeout(&i2c_dev->complete,
> + i2c_dev->adap.timeout);
> + } else {
> + time_left = stm32f7_i2c_wait_polling(i2c_dev);
> + }
please, drop the brackets here... and time_left here serves only
not to get the -ETIMEDOUT... looks a bit ugly to me, but can't
think of a better way.
> +
> ret = f7_msg->result;
> if (ret) {
> if (i2c_dev->use_dma)
> @@ -1727,6 +1753,24 @@ static int stm32f7_i2c_xfer(struct i2c_adapter *i2c_adap,
> return (ret < 0) ? ret : num;
> }
>
> +static int stm32f7_i2c_xfer(struct i2c_adapter *i2c_adap,
> + struct i2c_msg msgs[], int num)
> +{
> + struct stm32f7_i2c_dev *i2c_dev = i2c_get_adapdata(i2c_adap);
> +
> + i2c_dev->atomic = 0;
false
> + return stm32f7_i2c_xfer_core(i2c_adap, msgs, num);
> +}
> +
> +static int stm32f7_i2c_xfer_atomic(struct i2c_adapter *i2c_adap,
> + struct i2c_msg msgs[], int num)
> +{
> + struct stm32f7_i2c_dev *i2c_dev = i2c_get_adapdata(i2c_adap);
> +
> + i2c_dev->atomic = 1;
true
Andi
> + return stm32f7_i2c_xfer_core(i2c_adap, msgs, num);
> +}
> +
next prev parent reply other threads:[~2023-07-26 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 10:54 [PATCH v2] i2c: stm32f7: Add atomic_xfer method to driver Sean Nyekjaer
2023-07-26 21:21 ` Andi Shyti [this message]
2023-08-16 6:59 ` Sean Nyekjaer
2023-08-02 10:07 ` Alain Volmat
2023-08-16 7:02 ` Sean Nyekjaer
2023-08-16 7:22 ` Sean Nyekjaer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230726212132.vylu6qulpyu5fndh@intel.intel \
--to=andi.shyti@kernel.org \
--cc=alain.volmat@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pierre-yves.mordret@foss.st.com \
--cc=sean@geanix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox