From: Vinod Koul <vkoul@kernel.org>
To: Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>,
Bartosz Golaszewski <brgl@kernel.org>,
bjorn.andersson@oss.qualcomm.com
Cc: viken.dadhaniya@oss.qualcomm.com, andi.shyti@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Frank.Li@kernel.org, andersson@kernel.org,
konradybcio@kernel.org, dmitry.baryshkov@oss.qualcomm.com,
linmq006@gmail.com, quic_jseerapu@quicinc.com,
zhengxingda@iscas.ac.cn, kees@kernel.org, agross@kernel.org,
linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org, krzysztof.kozlowski@oss.qualcomm.com,
bartosz.golaszewski@oss.qualcomm.com,
bjorn.andersson@oss.qualcomm.com, konrad.dybcio@oss.qualcomm.com
Subject: Re: [PATCH v8 2/4] dmaengine: qcom: gpi: Add lock/unlock TREs for multi-owner I2C transfers
Date: Wed, 15 Jul 2026 21:03:40 +0530 [thread overview]
Message-ID: <aleoVNavBOrF9r7O@vaman> (raw)
In-Reply-To: <20260708051023.2872304-3-mukesh.savaliya@oss.qualcomm.com>
On 08-07-26, 10:40, Mukesh Kumar Savaliya wrote:
> +/**
> + * enum gpi_lock_action - request lock/unlock TRE sequencing
> + * @GPI_LOCK_NONE: No lock/unlock TRE requested for this transfer
> + * @GPI_LOCK_ACQUIRE: Emit a lock TRE before the transfer
> + * @GPI_LOCK_RELEASE: Emit an unlock TRE after the transfer
> + *
> + * Used by protocol drivers for multi-owner controller setups (e.g. when
> + * DeviceTree indicates the controller is shared via qcom,qup-multi-owner).
> + */
> +enum gpi_lock_action {
> + GPI_LOCK_NONE = 0,
> + GPI_LOCK_ACQUIRE,
> + GPI_LOCK_RELEASE,
Can qualcomm people please align on LOCK/UNLOCK interface? This is
second interface I am seeing now. Can you folks align internally on how
clients should communicating lock/unlock across different qualcomm
dmaengine drivers
--
~Vinod
next prev parent reply other threads:[~2026-07-15 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 5:10 [PATCH v8 0/4] Enable multi-owner I2C support for QCOM GENI controllers Mukesh Kumar Savaliya
2026-07-08 5:10 ` [PATCH v8 1/4] dt-bindings: i2c: qcom,i2c-geni: Document multi-owner controller support Mukesh Kumar Savaliya
2026-07-08 5:19 ` sashiko-bot
2026-07-08 5:10 ` [PATCH v8 2/4] dmaengine: qcom: gpi: Add lock/unlock TREs for multi-owner I2C transfers Mukesh Kumar Savaliya
2026-07-08 5:32 ` sashiko-bot
2026-07-15 12:22 ` Konrad Dybcio
2026-07-15 15:33 ` Vinod Koul [this message]
2026-07-08 5:10 ` [PATCH v8 3/4] soc: qcom: geni-se: Keep pinctrl active for multi-owner controllers Mukesh Kumar Savaliya
2026-07-08 5:25 ` sashiko-bot
2026-07-08 5:10 ` [PATCH v8 4/4] i2c: qcom-geni: Support multi-owner controllers in GPI mode Mukesh Kumar Savaliya
2026-07-08 5:23 ` sashiko-bot
2026-07-15 12:24 ` Konrad Dybcio
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=aleoVNavBOrF9r7O@vaman \
--to=vkoul@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kees@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linmq006@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mukesh.savaliya@oss.qualcomm.com \
--cc=quic_jseerapu@quicinc.com \
--cc=robh@kernel.org \
--cc=viken.dadhaniya@oss.qualcomm.com \
--cc=zhengxingda@iscas.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.