[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176062693701.525215.15119814964609949547.b4-ty@kernel.org>
Date: Thu, 16 Oct 2025 20:32:17 +0530
From: Vinod Koul <vkoul@...nel.org>
To: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>,
Viken Dadhaniya <quic_vdadhani@...cinc.com>,
Andi Shyti <andi.shyti@...nel.org>, Sumit Semwal <sumit.semwal@...aro.org>,
Christian König <christian.koenig@....com>,
Jyothi Kumar Seerapu <jyothi.seerapu@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org, dmaengine@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linaro-mm-sig@...ts.linaro.org, quic_vtanuku@...cinc.com
Subject: Re: [PATCH v8 0/2] i2c: i2c-qcom-geni: Add Block event interrupt
support
On Thu, 25 Sep 2025 17:30:33 +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 mitigate this latency, utilize Block Event Interrupt (BEI)
> mechanism. Enabling BEI instructs the hardware to prevent interrupt
> generation and BEI is disabled when an interrupt is necessary.
>
> [...]
Applied, thanks!
[1/2] dmaengine: qcom: gpi: Add GPI Block event interrupt support
commit: 4e8331317e73902e8b2663352c8766227e633901
[2/2] i2c: i2c-qcom-geni: Add Block event interrupt support
commit: 398035178503bf662281bbffb4bebce1460a4bc5
Best regards,
--
~Vinod
Powered by blists - more mailing lists