Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 8/11/2025 11:10 PM, Vinod Koul wrote: On 25-07-25, 16:20, Jyothi Kumar Seerapu wrote: On 7/23/2025 12:45 PM, Vinod Koul wrote: On 22-07-25, 15:46, Dmitry Baryshkov wrote: On Tue, Jul 22, 2025 at 05:50:08PM +0530, Jyothi Kumar Seerapu wrote: On 7/19/2025 3:27 PM, Dmitry Baryshkov wrote

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 25-07-25, 16:20, Jyothi Kumar Seerapu wrote: > > > On 7/23/2025 12:45 PM, Vinod Koul wrote: > > On 22-07-25, 15:46, Dmitry Baryshkov wrote: > > > On Tue, Jul 22, 2025 at 05:50:08PM +0530, Jyothi Kumar Seerapu wrote: > > > > On 7/19/2025 3:27 PM, Dmitry Baryshkov wrote: > > > > > On Mon, Jul 07

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 7/23/2025 12:45 PM, Vinod Koul wrote: On 22-07-25, 15:46, Dmitry Baryshkov wrote: On Tue, Jul 22, 2025 at 05:50:08PM +0530, Jyothi Kumar Seerapu wrote: On 7/19/2025 3:27 PM, Dmitry Baryshkov wrote: On Mon, Jul 07, 2025 at 09:58:30PM +0530, Jyothi Kumar Seerapu wrote: On 7/4/2025 1:11 AM

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 22-07-25, 15:46, Dmitry Baryshkov wrote: > On Tue, Jul 22, 2025 at 05:50:08PM +0530, Jyothi Kumar Seerapu wrote: > > On 7/19/2025 3:27 PM, Dmitry Baryshkov wrote: > > > On Mon, Jul 07, 2025 at 09:58:30PM +0530, Jyothi Kumar Seerapu wrote: > > > > On 7/4/2025 1:11 AM, Dmitry Baryshkov wrote: > >

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On Tue, Jul 22, 2025 at 05:50:08PM +0530, Jyothi Kumar Seerapu wrote: > > > On 7/19/2025 3:27 PM, Dmitry Baryshkov wrote: > > On Mon, Jul 07, 2025 at 09:58:30PM +0530, Jyothi Kumar Seerapu wrote: > > > > > > > > > On 7/4/2025 1:11 AM, Dmitry Baryshkov wrote: > > > > On Thu, 3 Jul 2025 at 15:51,

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 7/19/2025 3:27 PM, Dmitry Baryshkov wrote: On Mon, Jul 07, 2025 at 09:58:30PM +0530, Jyothi Kumar Seerapu wrote: On 7/4/2025 1:11 AM, Dmitry Baryshkov wrote: On Thu, 3 Jul 2025 at 15:51, Jyothi Kumar Seerapu wrote: On 6/19/2025 9:46 PM, Jyothi Kumar Seerapu wrote: On 6/18/2025 1

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On Mon, Jul 07, 2025 at 09:58:30PM +0530, Jyothi Kumar Seerapu wrote: > > > On 7/4/2025 1:11 AM, Dmitry Baryshkov wrote: > > On Thu, 3 Jul 2025 at 15:51, Jyothi Kumar Seerapu > > wrote: > > > > > > > > > > > > On 6/19/2025 9:46 PM, Jyothi Kumar Seerapu wrote: > > > > > > > > > > > > On 6/18

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 7/4/2025 1:11 AM, Dmitry Baryshkov wrote: On Thu, 3 Jul 2025 at 15:51, Jyothi Kumar Seerapu wrote: On 6/19/2025 9:46 PM, Jyothi Kumar Seerapu wrote: On 6/18/2025 1:02 AM, Dmitry Baryshkov wrote: On Tue, 17 Jun 2025 at 17:11, Jyothi Kumar Seerapu wrote: On 5/30/2025 10:12 PM, D

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On Thu, 3 Jul 2025 at 15:51, Jyothi Kumar Seerapu wrote: > > > > On 6/19/2025 9:46 PM, Jyothi Kumar Seerapu wrote: > > > > > > On 6/18/2025 1:02 AM, Dmitry Baryshkov wrote: > >> On Tue, 17 Jun 2025 at 17:11, Jyothi Kumar Seerapu > >> wrote: > >>> > >>> > >>> > >>> On 5/30/2025 10:12 PM, Dmitry Ba

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 6/19/2025 9:46 PM, Jyothi Kumar Seerapu wrote: On 6/18/2025 1:02 AM, Dmitry Baryshkov wrote: On Tue, 17 Jun 2025 at 17:11, Jyothi Kumar Seerapu wrote: On 5/30/2025 10:12 PM, Dmitry Baryshkov wrote: On Fri, May 30, 2025 at 07:36:05PM +0530, Jyothi Kumar Seerapu wrote: On 5/21/202

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 6/18/2025 1:02 AM, Dmitry Baryshkov wrote: On Tue, 17 Jun 2025 at 17:11, Jyothi Kumar Seerapu wrote: On 5/30/2025 10:12 PM, Dmitry Baryshkov wrote: On Fri, May 30, 2025 at 07:36:05PM +0530, Jyothi Kumar Seerapu wrote: On 5/21/2025 6:15 PM, Dmitry Baryshkov wrote: On Wed, May 21, 2

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On Tue, 17 Jun 2025 at 17:11, Jyothi Kumar Seerapu wrote: > > > > On 5/30/2025 10:12 PM, Dmitry Baryshkov wrote: > > On Fri, May 30, 2025 at 07:36:05PM +0530, Jyothi Kumar Seerapu wrote: > >> > >> > >> On 5/21/2025 6:15 PM, Dmitry Baryshkov wrote: > >>> On Wed, May 21, 2025 at 03:58:48PM +0530, Jy

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 5/30/2025 10:12 PM, Dmitry Baryshkov wrote: On Fri, May 30, 2025 at 07:36:05PM +0530, Jyothi Kumar Seerapu wrote: On 5/21/2025 6:15 PM, Dmitry Baryshkov wrote: On Wed, May 21, 2025 at 03:58:48PM +0530, Jyothi Kumar Seerapu wrote: On 5/9/2025 9:31 PM, Dmitry Baryshkov wrote: On 09/05

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On Fri, May 30, 2025 at 07:36:05PM +0530, Jyothi Kumar Seerapu wrote: > > > On 5/21/2025 6:15 PM, Dmitry Baryshkov wrote: > > On Wed, May 21, 2025 at 03:58:48PM +0530, Jyothi Kumar Seerapu wrote: > > > > > > > > > On 5/9/2025 9:31 PM, Dmitry Baryshkov wrote: > > > > On 09/05/2025 09:18, Jyothi

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 5/21/2025 6:15 PM, Dmitry Baryshkov wrote: On Wed, May 21, 2025 at 03:58:48PM +0530, Jyothi Kumar Seerapu wrote: On 5/9/2025 9:31 PM, Dmitry Baryshkov wrote: On 09/05/2025 09:18, Jyothi Kumar Seerapu wrote: Hi Dimitry, Thanks for providing the review comments. On 5/6/2025 5:16 PM, Dmi

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On Wed, May 21, 2025 at 03:58:48PM +0530, Jyothi Kumar Seerapu wrote: > > > On 5/9/2025 9:31 PM, Dmitry Baryshkov wrote: > > On 09/05/2025 09:18, Jyothi Kumar Seerapu wrote: > > > Hi Dimitry, Thanks for providing the review comments. > > > > > > On 5/6/2025 5:16 PM, Dmitry Baryshkov wrote: > > >

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 5/9/2025 9:31 PM, Dmitry Baryshkov wrote: On 09/05/2025 09:18, Jyothi Kumar Seerapu wrote: Hi Dimitry, Thanks for providing the review comments. On 5/6/2025 5:16 PM, Dmitry Baryshkov wrote: On Tue, May 06, 2025 at 04:48:44PM +0530, Jyothi Kumar Seerapu wrote: The I2C driver gets an inte

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 09/05/2025 09:18, Jyothi Kumar Seerapu wrote: Hi Dimitry, Thanks for providing the review comments. On 5/6/2025 5:16 PM, Dmitry Baryshkov wrote: On Tue, May 06, 2025 at 04:48:44PM +0530, Jyothi Kumar Seerapu wrote: The I2C driver gets an interrupt upon transfer completion. When handling mul

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

Hi Dimitry, Thanks for providing the review comments. On 5/6/2025 5:16 PM, Dmitry Baryshkov wrote: On Tue, May 06, 2025 at 04:48:44PM +0530, Jyothi Kumar Seerapu wrote: The I2C driver gets an interrupt upon transfer completion. When handling multiple messages in a single transfer, this results

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 5/7/2025 7:51 AM, ALOK TIWARI wrote: On 06-05-2025 16:48, Jyothi Kumar Seerapu wrote: +/** + * struct geni_i2c_dev - I2C Geni device specific structure + * + * @se: geni serial engine + * @tx_wm: Tx watermark level + * @irq: i2c serial engine interrupt + * @err: specifies error codes in

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On 06-05-2025 16:48, Jyothi Kumar Seerapu wrote: +/** + * struct geni_i2c_dev - I2C Geni device specific structure + * + * @se: geni serial engine + * @tx_wm: Tx watermark level + * @irq: i2c serial engine interrupt + * @err: specifies error codes in i2c transfer failures + * @adap: i2c geni a

Re: [PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

On Tue, May 06, 2025 at 04:48:44PM +0530, Jyothi Kumar Seerapu wrote: > The I2C driver gets an interrupt upon transfer completion. > When handling multiple messages in a single transfer, this > results in N interrupts for N messages, leading to significant > software interrupt latency. > > To miti

[PATCH v6 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support

The I2C driver gets an interrupt upon transfer completion. When handling multiple messages in a single transfer, this results in N interrupts for N messages, leading to significant software interrupt latency. To mitigate this latency, utilize Block Event Interrupt (BEI) mechanism. Enabling BEI ins