From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
konrad.dybcio@linaro.org, andersson@kernel.org,
andi.shyti@kernel.org, linux-arm-msm@vger.kernel.org,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Cc: quic_vdadhani@quicinc.com
Subject: Re: [PATCH v1 0/4] Enable shared SE support over I2C
Date: Thu, 29 Aug 2024 11:10:22 +0100 [thread overview]
Message-ID: <c3ee4cd4-a4a6-421c-9114-fba5ecc365da@linaro.org> (raw)
In-Reply-To: <20240829092418.2863659-1-quic_msavaliy@quicinc.com>
On 29/08/2024 10:24, Mukesh Kumar Savaliya wrote:
> This Series adds support to share QUP based I2C SE between subsystems.
> Each subsystem should have its own GPII which interacts between SE and
> GSI DMA HW engine.
>
> Subsystem must acquire Lock over the SE on GPII channel 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 SE 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.
>
> ---
> Mukesh Kumar Savaliya (4):
> dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag
> dma: gpi: Add Lock and Unlock TRE support to access SE exclusively
> soc: qcom: geni-se: Export function geni_se_clks_off()
> i2c: i2c-qcom-geni: Enable i2c controller sharing between two
> subsystems
>
> .../bindings/i2c/qcom,i2c-geni-qcom.yaml | 4 ++
> drivers/dma/qcom/gpi.c | 37 ++++++++++++++++++-
> drivers/i2c/busses/i2c-qcom-geni.c | 29 +++++++++++----
> drivers/soc/qcom/qcom-geni-se.c | 4 +-
> include/linux/dma/qcom-gpi-dma.h | 6 +++
> include/linux/soc/qcom/geni-se.h | 3 ++
> 6 files changed, 74 insertions(+), 9 deletions(-)
>
In the cover letter please give an example of Serial Engine sharing.
next prev parent reply other threads:[~2024-08-29 10:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 9:24 [PATCH v1 0/4] Enable shared SE support over I2C Mukesh Kumar Savaliya
2024-08-29 9:24 ` [PATCH v1 1/4] dt-bindindgs: i2c: qcom,i2c-geni: Document shared flag Mukesh Kumar Savaliya
2024-08-29 9:58 ` Bryan O'Donoghue
2024-08-29 10:01 ` Bryan O'Donoghue
2024-09-04 18:26 ` Mukesh Kumar Savaliya
2024-09-04 18:37 ` Mukesh Kumar Savaliya
2024-08-30 8:11 ` Krzysztof Kozlowski
2024-09-04 18:12 ` Mukesh Kumar Savaliya
2024-09-04 18:20 ` Krzysztof Kozlowski
2024-09-05 5:43 ` Mukesh Kumar Savaliya
2024-09-05 6:21 ` Krzysztof Kozlowski
2024-09-05 11:17 ` Mukesh Kumar Savaliya
2024-08-29 9:24 ` [PATCH v1 2/4] dma: gpi: Add Lock and Unlock TRE support to access SE exclusively Mukesh Kumar Savaliya
2024-08-29 10:05 ` Bryan O'Donoghue
2024-09-04 18:23 ` Mukesh Kumar Savaliya
2024-08-29 9:24 ` [PATCH v1 3/4] soc: qcom: geni-se: Export function geni_se_clks_off() Mukesh Kumar Savaliya
2024-08-29 10:19 ` Bryan O'Donoghue
2024-09-04 18:12 ` Mukesh Kumar Savaliya
2024-08-29 9:24 ` [PATCH v1 4/4] i2c: i2c-qcom-geni: Enable i2c controller sharing between two subsystems Mukesh Kumar Savaliya
2024-08-29 9:56 ` [PATCH v1 0/4] Enable shared SE support over I2C Bryan O'Donoghue
2024-09-04 18:21 ` Mukesh Kumar Savaliya
2024-08-29 10:10 ` Bryan O'Donoghue [this message]
2024-09-04 18:08 ` Mukesh Kumar Savaliya
2024-08-29 17:01 ` Vinod Koul
2024-08-30 7:47 ` neil.armstrong
2024-09-04 18:07 ` Mukesh Kumar Savaliya
2024-09-05 7:09 ` neil.armstrong
2024-09-05 9:28 ` Mukesh Kumar Savaliya
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=c3ee4cd4-a4a6-421c-9114-fba5ecc365da@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_vdadhani@quicinc.com \
/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;
as well as URLs for NNTP newsgroup(s).