From: Doug Anderson <dianders@chromium.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v4 2/4] arm64: dts: qcom: sm8250: further split of spi pinctrl config
Date: Wed, 10 Feb 2021 06:41:22 -0800 [thread overview]
Message-ID: <CAD=FV=XFck7+d_d58wG8OJ4yBJrcJi-JKR3abfc_3V6ToP_nVg@mail.gmail.com> (raw)
In-Reply-To: <20210210133458.1201066-3-dmitry.baryshkov@linaro.org>
Hi,
On Wed, Feb 10, 2021 at 5:36 AM Dmitry Baryshkov
<dmitry.baryshkov@linaro.org> wrote:
>
> Split "default" device tree nodes into common "data-clk" nodes and "cs"
> nodes which might differ from board to board depending on how the slave
> chips are wired.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 9 +-
> arch/arm64/boot/dts/qcom/sm8250.dtsi | 220 ++++++++++++++---------
> 2 files changed, 148 insertions(+), 81 deletions(-)
Reviewed-by: Douglas Anderson <dianders@chromium.org>
next prev parent reply other threads:[~2021-02-10 14:42 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 [this message]
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 ` [PATCH v4 0/4] arm64: dts: qcom: qrb5165-rb5: use GPIO as " Dmitry Baryshkov
2021-03-18 14:50 ` 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='CAD=FV=XFck7+d_d58wG8OJ4yBJrcJi-JKR3abfc_3V6ToP_nVg@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.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).