From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andy Gross <agross@kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: qcom: sm8250: add pinctrl for SPI using GPIO as a CS
Date: Thu, 4 Feb 2021 18:25:47 -0600 [thread overview]
Message-ID: <YByQizVTnj2uTNt2@builder.lan> (raw)
In-Reply-To: <CAD=FV=XOk14DfAJT9j86WbiRifxUQZFPy1grJWoz0A7Fon1edg@mail.gmail.com>
On Thu 04 Feb 17:31 CST 2021, Doug Anderson wrote:
> On Thu, Feb 4, 2021 at 3:07 PM Bjorn Andersson
> <bjorn.andersson@linaro.org> wrote:
> > On Thu 04 Feb 14:49 CST 2021, Dmitry Baryshkov wrote:
[..]
> > > diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> > > index 3cea28058a91..03015174ec06 100644
> > > --- a/arch/arm64/boot/dts/qcom/sm8250.dtsi
> > > +++ b/arch/arm64/boot/dts/qcom/sm8250.dtsi
> > > @@ -3046,6 +3046,25 @@ config {
> > > };
> > > };
> > >
> > > + qup_spi0_cs_gpio: qup-spi0-cs-gpio {
> >
> > There might be others who need the same states, but I would prefer if we
> > move this to the device's dts.
>
> This is opposite to what Stephen requested, though it was in a review
> on our gerrit and not on lists [1]. :-P
>
> It definitely feels like a 6 of one half dozen of the other. Unless
> you're dead set on moving them to the board dts my bias would be
> towards keeping consistent with what was done on sc7180. If you
> really want this moved to the board file we should do it for sc7180
> too.
>
What I dislike is the fact that we have a huge amount of these unused in
the platform.dtsi, but let's align with what I agreed to on
sc7180...Sorry for the short memory.
>
> > > + mux {
> >
> > Rather than splitting the properties in {mux, cs, config} I think it
> > makes more sense to split them in {spi, cs} or something like that.
>
> In general pinconf doesn't belong in the SoC dts file. If there's no
> reason to change it seems like this should match what sc7180 did.
>
Right, but I still would prefer the pinctrl state to be split by
function/pins, rather than pinmux vs pinconf. That way it's natural to
add pinconf properties to the various functional parts (i.e. bias or
drive-strength for the spi pins vs cs).
Do you have any concerns with this?
Regards,
Bjorn
>
> [1] https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/2406557/1/arch/arm64/boot/dts/qcom/sc7180-trogdor.dtsi
next prev parent reply other threads:[~2021-02-05 0:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 20:49 [PATCH 1/2] arm64: dts: qcom: sm8250: add pinctrl for SPI using GPIO as a CS Dmitry Baryshkov
2021-02-04 20:49 ` [PATCH 2/2] arm64: dts: qcom: qrb5165-rb5: switch into using GPIO for SPI0 CS Dmitry Baryshkov
2021-02-04 23:07 ` [PATCH 1/2] arm64: dts: qcom: sm8250: add pinctrl for SPI using GPIO as a CS Bjorn Andersson
2021-02-04 23:31 ` Doug Anderson
2021-02-05 0:08 ` Dmitry Baryshkov
2021-02-05 0:25 ` Bjorn Andersson [this message]
2021-02-05 15:00 ` Doug Anderson
2021-02-05 16:48 ` Bjorn Andersson
2021-02-08 15:58 ` Doug Anderson
2021-02-08 18:04 ` Bjorn Andersson
2021-02-09 10:21 ` Dmitry Baryshkov
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=YByQizVTnj2uTNt2@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.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).