From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Vijaya Krishna Nivarthi <quic_vnivarth@quicinc.com>,
agross@kernel.org, andersson@kernel.org, broonie@kernel.org,
linux-arm-msm@vger.kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: quic_msavaliy@quicinc.com, dianders@chromium.org,
mka@chromium.org, swboyd@chromium.org, quic_vtanuku@quicinc.com
Subject: Re: [PATCH] spi: spi-geni-qcom: Correct CS_TOGGLE bit in SPI_TRANS_CFG
Date: Tue, 25 Apr 2023 14:45:57 +0100 [thread overview]
Message-ID: <9f28dbff-ca3a-8523-5bfc-37b38bc846c3@linaro.org> (raw)
In-Reply-To: <1682412128-1913-1-git-send-email-quic_vnivarth@quicinc.com>
On 4/25/23 09:42, Vijaya Krishna Nivarthi wrote:
> The CS_TOGGLE bit when set is supposed to instruct FW to
> toggle CS line between words. The driver with intent of
> disabling this behaviour has been unsetting BIT(0). This has
> not caused any trouble so far because the original BIT(1)
> is untouched and BIT(0) likely wasn't being used.
>
> Correct this to prevent a potential future bug.
>
> Signed-off-by: Vijaya Krishna Nivarthi <quic_vnivarth@quicinc.com>
> ---
Has this always been the case, or did the switch to BIT(1)
only occur on some recent platforms?
Konrad
> drivers/spi/spi-geni-qcom.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/spi/spi-geni-qcom.c b/drivers/spi/spi-geni-qcom.c
> index ba7be50..8a7d1c2 100644
> --- a/drivers/spi/spi-geni-qcom.c
> +++ b/drivers/spi/spi-geni-qcom.c
> @@ -35,7 +35,7 @@
> #define CS_DEMUX_OUTPUT_SEL GENMASK(3, 0)
>
> #define SE_SPI_TRANS_CFG 0x25c
> -#define CS_TOGGLE BIT(0)
> +#define CS_TOGGLE BIT(1)
>
> #define SE_SPI_WORD_LEN 0x268
> #define WORD_LEN_MSK GENMASK(9, 0)
next prev parent reply other threads:[~2023-04-25 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 8:42 Vijaya Krishna Nivarthi
2023-04-25 13:45 ` Konrad Dybcio [this message]
2023-05-01 8:05 ` Vijaya Krishna Nivarthi
2023-05-01 12:43 ` Konrad Dybcio
2023-05-01 12:44 ` Konrad Dybcio
2023-04-25 15:07 ` Doug Anderson
2023-05-08 13:27 ` Mark Brown
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=9f28dbff-ca3a-8523-5bfc-37b38bc846c3@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mka@chromium.org \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_vnivarth@quicinc.com \
--cc=quic_vtanuku@quicinc.com \
--cc=swboyd@chromium.org \
/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
all inboxes | Powered by JetHome®