Re: [PATCH v2 7/9] i3c: mipi-i3c-hci: Program AST2700 IBI termination threshold

From: Frank Li

Date: Wed Nov 11 2026 - 12:33:29 EST


On Wed, Nov 11, 2026 at 11:16:35AM +0800, Billy Tsai wrote:
> For an IBI with payload, it's normally the device that decides when to
> stop sending payload bytes. A misbehaving device that never terminates
> can leave the controller stuck waiting on the transfer. AST2700 has an
> in-house IBI payload length threshold that, once enabled, forces
> termination once the received payload reaches it.
>
> When payload IBIs are requested, grow the AST2700 termination
> threshold to at least the requested payload length and enable
> termination on that value. The register is controller-wide while IBI
> requests for different devices can run in parallel, so the
> read-modify-write is serialized under the controller lock. Gate this
> behind HCI_QUIRK_IBI_PAYLOAD_THLD; controllers without the quirk keep
> the existing behavior.

what's happen if device A have payload 4 bytes and device B have payload
8 bytes, you set payload thld to 8. if device A raise IBI, what's happen
if device have not sent out earily termniate?

Frank