Re: [PATCH v2 RESEND 3/3] i2c: i2c-qcom-geni: Add Block event interrupt support

2024-12-02 Thread Jyothi Kumar Seerapu
On 11/21/2024 6:28 PM, Jyothi Kumar Seerapu wrote: On 11/12/2024 10:03 AM, Bjorn Andersson wrote: On Mon, Nov 11, 2024 at 07:32:44PM +0530, Jyothi Kumar Seerapu wrote: The I2C driver gets an interrupt upon transfer completion. For multiple messages in a single transfer, N interrupts will b

Re: [PATCH v2 RESEND 3/3] i2c: i2c-qcom-geni: Add Block event interrupt support

2024-11-21 Thread Jyothi Kumar Seerapu
On 11/12/2024 10:03 AM, Bjorn Andersson wrote: On Mon, Nov 11, 2024 at 07:32:44PM +0530, Jyothi Kumar Seerapu wrote: The I2C driver gets an interrupt upon transfer completion. For multiple messages in a single transfer, N interrupts will be received for N messages, leading to significant soft

Re: [PATCH v2 RESEND 3/3] i2c: i2c-qcom-geni: Add Block event interrupt support

2024-11-11 Thread Bjorn Andersson
On Mon, Nov 11, 2024 at 07:32:44PM +0530, Jyothi Kumar Seerapu wrote: > The I2C driver gets an interrupt upon transfer completion. > For multiple messages in a single transfer, N interrupts will be > received for N messages, leading to significant software interrupt > latency. To mitigate this late

[PATCH v2 RESEND 3/3] i2c: i2c-qcom-geni: Add Block event interrupt support

2024-11-11 Thread Jyothi Kumar Seerapu
The I2C driver gets an interrupt upon transfer completion. For multiple messages in a single transfer, N interrupts will be received for N messages, leading to significant software interrupt latency. To mitigate this latency, utilize Block Event Interrupt (BEI) only when an interrupt is necessary.