Re: [PATCH v8 2/4] dmaengine: qcom: gpi: Add lock/unlock TREs for multi-owner I2C transfers

Konrad Dybcio <[email protected]>
Newsgroups org.kernel.vger.linux-i2c,org.kernel.vger.dmaengine,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
On 7/8/26 7:10 AM, Mukesh Kumar Savaliya wrote:
> Some platforms use a QUP-based I2C controller in a configuration where the
> controller is shared with another system processor (described in DT using
> qcom,qup-multi-owner). In such setups, GPI hardware lock/unlock TREs can be
> used to serialize access to the controller.
> 
> Add support to emit lock and unlock TREs around I2C transfers and increase
> the maximum TRE count to account for the additional elements.
> 
> Also simplify the client interface by replacing multiple boolean fields
> (shared flag and message position tracking) with a single lock_action
> selector (acquire/release/none), as the GPI driver only needs to know
> whether to emit lock/unlock TREs for a given transfer.
> 
> Signed-off-by: Mukesh Kumar Savaliya <[email protected]>
> ---

Acked-by: Konrad Dybcio <[email protected]>

Konrad
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.