From: Vinod Koul <vkoul@kernel.org>
To: Aniket Randive <quic_arandive@quicinc.com>
Cc: agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, broonie@kernel.org,
linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_msavaliy@quicinc.com,
quic_vtanuku@quicinc.com, quic_ramkri@quicinc.com
Subject: Re: [RESEND V1] soc: qcom: geni: Add SPI Slave protocol type
Date: Wed, 9 Nov 2022 16:39:25 +0530 [thread overview]
Message-ID: <Y2uKZZqF/Pps8hvU@matsya> (raw)
In-Reply-To: <1667987326-13970-1-git-send-email-quic_arandive@quicinc.com>
Hi Aniket,
On 09-11-22, 15:18, Aniket Randive wrote:
> Add "GENI_SE_SPI_SLAVE" entry in enum which represents the
> protocols supported by GENI Serial Engines. This is needed
Ok
> to support the SPI slave feature on QUP based target.
Where is that support. Typically we dont merge things without users, so
please add this patch along with slave support in driver
>
> Signed-off-by: Aniket Randive <quic_arandive@quicinc.com>
> ---
> include/linux/qcom-geni-se.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/qcom-geni-se.h b/include/linux/qcom-geni-se.h
> index f567278..9fb2175 100644
> --- a/include/linux/qcom-geni-se.h
> +++ b/include/linux/qcom-geni-se.h
> @@ -35,6 +35,7 @@ enum geni_se_protocol_type {
> GENI_SE_UART,
> GENI_SE_I2C,
> GENI_SE_I3C,
> + GENI_SE_SPI_SLAVE,
> };
>
> struct geni_wrapper;
> --
> 2.7.4
--
~Vinod
prev parent reply other threads:[~2022-11-09 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 9:48 [RESEND V1] soc: qcom: geni: Add SPI Slave protocol type Aniket Randive
2022-11-09 11:09 ` Vinod Koul [this message]
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=Y2uKZZqF/Pps8hvU@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_arandive@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_ramkri@quicinc.com \
--cc=quic_vtanuku@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).