Re: [PATCH v2 0/4] Enable shared SE support over I2C
From: Vinod Koul
Date: Wed Sep 11 2024 - 13:02:50 EST
On 07-09-24, 00:44, Mukesh Kumar Savaliya wrote:
> This Series adds support to share QUP (Qualcomm Unified peripheral)
> based I2C SE (Serial Engine) controller between two subsystems.
> Each subsystem should have its own dedicated GPII (General Purpose -
> Interface Instance) acting as pipe between SE and GSI (Generic SW -
> Interface) DMA HW engine.
>
> Subsystem must acquire Lock over the SE so that it gets uninterrupted
> control till it unlocks the SE. It also makes sure the commonly shared
> TLMM GPIOs are not touched which can impact other subsystem or cause
> any interruption. Generally, GPIOs are being unconfigured during
> suspend time.
>
> GSI DMA engine is capable to perform requested transfer operations
> from any of the I2C client in a seamless way and its transparent to
> the subsystems. Make sure to enable “qcom,shared-se” flag only while
> enabling this feature. I2C client should add in its respective parent
> node.
>
> Example :
> Two clients from different SS can share an I2C SE for same slave device
> OR their owned slave devices.
> Assume I2C Slave EEPROM device connected with I2C controller.
> Each client from ADSP SS and APPS Linux SS can perform i2c transactions.
> This gets serialized by lock TRE + DMA Transfers + Unlock TRE at HW level.
Where is the rest of the series, I see only this cover letter??
--
~Vinod