From: Mukesh Savaliya <mukesh.savaliya@oss.qualcomm.com>
To: "Jyothi Kumar Seerapu" <jyothi.seerapu@oss.qualcomm.com>,
"Vinod Koul" <vkoul@kernel.org>,
"Viken Dadhaniya" <quic_vdadhani@quicinc.com>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, quic_vtanuku@quicinc.com
Subject: Re: [PATCH v8 2/2] i2c: i2c-qcom-geni: Add Block event interrupt support
Date: Wed, 1 Oct 2025 15:56:31 +0530 [thread overview]
Message-ID: <671c517f-c04c-4f07-aa65-a93e1e1dbce3@oss.qualcomm.com> (raw)
In-Reply-To: <20250925120035.2844283-3-jyothi.seerapu@oss.qualcomm.com>
On 9/25/2025 5:30 PM, Jyothi Kumar Seerapu wrote:
> From: Jyothi Kumar Seerapu <quic_jseerapu@quicinc.com>
>
> 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.
>
> Large I2C transfer can be divided into chunks of messages internally.
> Interrupts are not expected for the messages for which BEI bit set,
> only the last message triggers an interrupt, indicating the completion of
> N messages. This BEI mechanism enhances overall transfer efficiency.
>
> BEI optimizations are currently implemented for I2C write transfers only,
> as there is no use case for multiple I2C read messages in a single transfer
> at this time.
>
> Signed-off-by: Jyothi Kumar Seerapu <quic_jseerapu@quicinc.com>
> ---
>
Reviewed-by: Mukesh Savaliya <mukesh.savaliya@oss.qualcomm.com>
next prev parent reply other threads:[~2025-10-01 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 12:00 [PATCH v8 0/2] i2c: i2c-qcom-geni: Add Block event interrupt support Jyothi Kumar Seerapu
2025-09-25 12:00 ` [PATCH v8 1/2] dmaengine: qcom: gpi: Add GPI " Jyothi Kumar Seerapu
2025-09-26 22:35 ` Dmitry Baryshkov
2025-10-03 18:48 ` Andi Shyti
2025-09-25 12:00 ` [PATCH v8 2/2] i2c: i2c-qcom-geni: Add " Jyothi Kumar Seerapu
2025-09-26 22:36 ` Dmitry Baryshkov
2025-10-01 9:35 ` Mukesh Savaliya
2025-10-01 10:26 ` Mukesh Savaliya [this message]
2025-10-03 18:50 ` Andi Shyti
2025-10-16 12:17 ` Vinod Koul
2025-10-16 15:02 ` [PATCH v8 0/2] " Vinod Koul
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=671c517f-c04c-4f07-aa65-a93e1e1dbce3@oss.qualcomm.com \
--to=mukesh.savaliya@oss.qualcomm.com \
--cc=andi.shyti@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jyothi.seerapu@oss.qualcomm.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=quic_vdadhani@quicinc.com \
--cc=quic_vtanuku@quicinc.com \
--cc=sumit.semwal@linaro.org \
--cc=vkoul@kernel.org \
/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