From: Xianwei Zhao <xianwei.zhao@amlogic.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Junyi Zhao <junyi.zhao@amlogic.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Xianwei Zhao <xianwei.zhaol@amlogic.com>,
Junyi Zhao <junyi.zhaol@amlogic.com>,
linux-i2c@vger.kernel.org, linux-amlogic@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] i2c: amlogic: Add Amlogic A9 I2C controller driver
Date: Tue, 27 Oct 2026 10:59:37 +0800 [thread overview]
Message-ID: <e5319105-0a88-44f5-94fd-6c78a0ab2ac1@amlogic.com> (raw)
In-Reply-To: <at8nuDtiHEDq4AZ2@zenone.zhora.eu>
Hi Andi,
Thanks for your review.
On 2026/10/26 23:22, Andi Shyti wrote:
> Hi Junyi,
>
> Sashiko's comments look legit to me, can you please take a look
> at those?
>
I'm currently looking at this part. Some of them don't have relatively
good solutions yet, so I haven't replied.
> Besides...
>
>> +static irqreturn_t aml_i2c_irq(int irqno, void *dev_id)
>> +{
>> + struct aml_i2c *i2c = dev_id;
>> + u8 *buf = NULL;
>> + int ret;
>> + u32 rd_len, i;
>> + u32 rd_val;
>> +
>> + spin_lock(&i2c->lock);
>> + ret = controller_is_error(i2c);
>> + if (ret) {
>> + i2c->error = ret;
>> + goto complete_irq_out;
>> + }
>> +
>> + switch (i2c->state) {
>> + case A9_STATE_READ:
>> + buf = i2c->msg->buf;
>> + rd_len = min(i2c->msg->len - i2c->pos, A9_I2C_FIFO_DEPTH);
>> + for (i = 0; i < rd_len; i++) {
>> + rd_val = readl(i2c->regs + REG_CFG_RX);
>> + buf[i2c->pos++] = rd_val & TX_RX_DATA;
>> + }
>> + /* Rx must clear thresh after read fifo */
>> + clear_irq_status(i2c, A9_RX_THRESH_READ);
>> + break;
>> + case A9_STATE_WRITE:
>> + aml_i2c_prepare_xfer(i2c, A9_FIFO_FILL_HALF);
>> + if ((i2c->pos + A9_I2C_HALF_FIFO) >= i2c->msg->len)
>> + aml_i2c_set_mask(i2c, REG_CFG_IRQ_ENABLE, A9_TX_THRESH_WRITE, 0);
>> + i2c->pos += i2c->count;
>> + /* Tx must clear thresh after write fifo */
>> + clear_irq_status(i2c, A9_TX_THRESH_WRITE);
>> + break;
>> + case A9_STATE_IDLE:
>> + dev_warn(i2c->dev, "i2c irq triggered abnormally, irq_state:0x%x,irq_en:0x%x\n",
>> + readl(i2c->regs + REG_CFG_IRQ_STATE),
>> + readl(i2c->regs + REG_CFG_IRQ_ENABLE));
>> + break;
>> + default:
>> + break;
>> + }
>> +
>> + if (!controller_is_done(i2c)) {
>> + goto irq_trans_out;
>> + } else {
>> + if (i2c->state == A9_STATE_READ && (i2c->msg->len - i2c->pos))
>> + goto irq_trans_out;
>> + }
> No need for brackets here:
>
> if (...)
> goto ...;
> else if (...)
> goto ...;
>
Will do.
> But perhaps the two can be even merged.
I will try to merged them.
> (i2c->msg->len - i2c->pos) is equal to (i2c->pos < i2c->msg->len)
>
Will do.
>> +
>> +complete_irq_out:
>> + reset_fifo_pos(i2c);
>> + complete(&i2c->done);
>> + i2c->state = A9_STATE_IDLE;
>> + aml_i2c_set_mask(i2c, REG_CFG_IRQ_ENABLE, A9_RX_THRESH_READ | A9_TX_THRESH_WRITE, 0);
>> + clear_irq_status(i2c, IRQ_ALL_MASK);
>> +irq_trans_out:
>> + spin_unlock(&i2c->lock);
> ...
>
>> + i2c->state = (msg->flags & I2C_M_RD) ? A9_STATE_READ : A9_STATE_WRITE;
>> + spin_lock_irqsave(&i2c->lock, flags);
>> + aml_i2c_prepare_xfer(i2c, A9_FIFO_FILL_FULL);
>> + i2c->pos += i2c->count;
>> + spin_unlock_irqrestore(&i2c->lock, flags);
>> + reinit_completion(&i2c->done);
>> +
>> + if (last)
>> + aml_i2c_set_mask(i2c, REG_CFG_BUS, BUS_NO_STOP, 0);
>> + else
>> + aml_i2c_set_mask(i2c, REG_CFG_BUS, BUS_NO_STOP, BUS_NO_STOP);
>> + /* Start the transfer */
>> + aml_i2c_do_start(i2c, msg);
> I think this should also be under spinlock in order to avoid that
> the interrupt handler accesses a partially initialized state.
>
I will lock it.
>> +
>> + time_left = msecs_to_jiffies(I2C_TIMEOUT_MS);
>> + time_left = wait_for_completion_timeout(&i2c->done, time_left);
>> +
>> + /*
>> + * Protect access to i2c struct and registers from interrupt
>> + * handlers triggered by a transfer terminated after the
>> + * timeout period
>> + */
>> +
>> + spin_lock_irqsave(&i2c->lock, flags);
>> + if (!time_left) {
>> + i2c->state = A9_STATE_IDLE;
>> + clear_irq_status(i2c, IRQ_ALL_MASK);
>> + reset_fifo_pos(i2c);
>> + ret = -ETIMEDOUT;
> the next instruction overwrites this error. Perhaps you could
> use a goto to spin_unlock and return.
>
> Andi
>
Will do.
>> + }
>> +
>> + if (i2c->error)
>> + ret = i2c->error;
>> + spin_unlock_irqrestore(&i2c->lock, flags);
>> +
>> + return ret;
>> +}
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-10-27 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 9:26 [PATCH v2 0/2] i2c: Add driver support Amlogic A9 I2C Xianwei Zhao via B4 Relay
2026-10-22 9:26 ` [PATCH v2 1/2] dt-bindings: i2c: add Amlogic A9 I2C controller Xianwei Zhao via B4 Relay
2026-10-22 9:26 ` [PATCH v2 2/2] i2c: amlogic: Add Amlogic A9 I2C controller driver Xianwei Zhao via B4 Relay
2026-10-22 9:46 ` sashiko-bot
2026-10-28 11:21 ` Xianwei Zhao
2026-10-26 15:22 ` Andi Shyti
2026-10-27 2:59 ` Xianwei Zhao [this message]
2026-10-26 17:28 ` Markus Elfring
2026-10-27 3:18 ` Xianwei Zhao
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=e5319105-0a88-44f5-94fd-6c78a0ab2ac1@amlogic.com \
--to=xianwei.zhao@amlogic.com \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=junyi.zhao@amlogic.com \
--cc=junyi.zhaol@amlogic.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=xianwei.zhaol@amlogic.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
all inboxes | Powered by JetHome®