linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Doug Anderson <dianders@chromium.org>
Cc: "open list:DRM DRIVER FOR MSM ADRENO GPU" 
	<linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v4 0/4] arm64: dts: qcom: qrb5165-rb5: use GPIO as SPI0 CS
Date: Sat, 13 Mar 2021 23:19:30 +0300	[thread overview]
Message-ID: <CAA8EJpoOXE3duEdZO63zuczGb4BUXjmzmq3fLxh2LHJWt0G4xg@mail.gmail.com> (raw)
In-Reply-To: <20210210133458.1201066-1-dmitry.baryshkov@linaro.org>

Colleagues,

On Wed, 10 Feb 2021 at 16:36, Dmitry Baryshkov
<dmitry.baryshkov@linaro.org> wrote:
>
> GENI SPI controller shows several issues if it manages the CS on its own
> (see 37dd4b777942 ("arm64: dts: qcom: sc7180: Provide pinconf for SPI to
> use GPIO for CS") for the details). Configure SPI0 CS pin as a GPIO.

Should I improve this patchset in any way or is it fine to go?

> Changes since v3:
>  - Rephrase qrb5165-rb5 commit
>  - Remove leftover  pinctrl-name entries for spi0
>  - Group pinctrl entries at the end of qrb5165-rb5.
>
> Changes since v2:
>  - Move pinctrl-names to the board file.
>  - Reorder CS/CS-gpio/data-clk nodes to follow alphabetical sort.
>
> Changes since v1:
>  - Split sm8250's spi pin config into mux/config parts, split away CS
>    handling from main SPI pinctrl nodes.
>
> ----------------------------------------------------------------
> Dmitry Baryshkov (4):
>       arm64: dts: qcom: sm8250: split spi pinctrl config
>       arm64: dts: qcom: sm8250: further split of spi pinctrl config
>       arm64: dts: qcom: sm8250: add pinctrl for SPI using GPIO as a CS
>       arm64: dts: qcom: qrb5165-rb5: switch into using GPIO for SPI0 CS
>
>  arch/arm64/boot/dts/qcom/qrb5165-rb5.dts |  14 +
>  arch/arm64/boot/dts/qcom/sm8250.dtsi     | 540 +++++++++++++++----------------
>  2 files changed, 274 insertions(+), 280 deletions(-)
>
>


-- 
With best wishes
Dmitry

  parent reply	other threads:[~2021-03-13 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 13:34 [PATCH v4 0/4] arm64: dts: qcom: qrb5165-rb5: use GPIO as SPI0 CS Dmitry Baryshkov
2021-02-10 13:34 ` [PATCH v4 1/4] arm64: dts: qcom: sm8250: split spi pinctrl config Dmitry Baryshkov
2021-02-10 14:41   ` Doug Anderson
2021-02-10 13:34 ` [PATCH v4 2/4] arm64: dts: qcom: sm8250: further split of " Dmitry Baryshkov
2021-02-10 14:41   ` Doug Anderson
2021-02-10 13:34 ` [PATCH v4 3/4] arm64: dts: qcom: sm8250: add pinctrl for SPI using GPIO as a CS Dmitry Baryshkov
2021-02-10 13:34 ` [PATCH v4 4/4] arm64: dts: qcom: qrb5165-rb5: switch into using GPIO for SPI0 CS Dmitry Baryshkov
2021-03-13 20:19 ` Dmitry Baryshkov [this message]
2021-03-18 14:50 ` [PATCH v4 0/4] arm64: dts: qcom: qrb5165-rb5: use GPIO as " patchwork-bot+linux-arm-msm

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=CAA8EJpoOXE3duEdZO63zuczGb4BUXjmzmq3fLxh2LHJWt0G4xg@mail.gmail.com \
    --to=dmitry.baryshkov@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=dianders@chromium.org \
    --cc=linux-arm-msm@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).