On 1/13/2025 3:56 PM, Mukesh Kumar Savaliya wrote:
On 1/7/2025 4:09 PM, Jyothi Kumar Seerapu wrote:
On 1/7/2025 11:33 AM, Mukesh Kumar Savaliya wrote:
On 12/17/2024 10:34 PM, Jyothi Kumar Seerapu wrote:
The I2C driver gets an interrupt upon transfer completion.
When handling multiple
On 1/7/2025 4:09 PM, Jyothi Kumar Seerapu wrote:
On 1/7/2025 11:33 AM, Mukesh Kumar Savaliya wrote:
On 12/17/2024 10:34 PM, 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 inter
On 1/7/2025 11:33 AM, Mukesh Kumar Savaliya wrote:
On 12/17/2024 10:34 PM, 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
softwar
On 12/17/2024 10:34 PM, 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, utiliz
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
