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: Mon, 1 May 2023 14:43:11 +0200 [thread overview]
Message-ID: <d23d3757-da6f-69d7-bca9-581c489f81e6@linaro.org> (raw)
In-Reply-To: <1b1b095e-8fcb-37d5-7542-48a6b55f35a1@quicinc.com>
On 1.05.2023 10:05, Vijaya Krishna Nivarthi wrote:
> On 4/25/2023 7:15 PM, Konrad Dybcio wrote:
>>
>> 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?
>
>
> Thank you very much for the review..
>
> This has always been the case.
>
> With intent of disabling CS_TOGGLE, currently, the driver is unsetting BIT(0), though it should have been BIT(1).
>
> Yet no problem was encountered because
>
> a) BIT(0) seems to be an unused bit
>
> b) BIT(1) is probably already unset because its untouched
>
> Further more, as Doug pointed we are mostly using GPIO for CS.
>
>
> Testing with the change has not caused any regressions.
Okay, with no deeper knowledge of the topic best I can give you is:
Acked-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
>
>
> Thank you,
>
> Vijay/
>
>
>
>>
>> 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-05-01 12:43 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
2023-05-01 8:05 ` Vijaya Krishna Nivarthi
2023-05-01 12:43 ` Konrad Dybcio [this message]
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=d23d3757-da6f-69d7-bca9-581c489f81e6@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®