From: Stephen Boyd <swboyd@chromium.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-cheza: Add cr50 spi node
Date: Mon, 16 Dec 2019 15:32:46 -0800 [thread overview]
Message-ID: <5df8141f.1c69fb81.98eee.37b4@mx.google.com> (raw)
In-Reply-To: <CAD=FV=Urn0ZhQSaVBkdq0hTEqe=bDP0KPz87Rd4B_bCF2CoFUA@mail.gmail.com>
Quoting Doug Anderson (2019-12-16 14:53:22)
> Hi,
>
> On Mon, Dec 16, 2019 at 1:16 PM Stephen Boyd <swboyd@chromium.org> wrote:
> >
> > Add the cr50 device to the spi controller it is attached to. This
> > enables /dev/tpm0 and some login things on Cheza.
> >
> > Cc: Douglas Anderson <dianders@chromium.org>
> > Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> > ---
> > arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi b/arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi
> > index 9a4ff57fc877..f6683460dc82 100644
> > --- a/arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi
> > @@ -651,6 +651,20 @@ &spi0 {
> > status = "okay";
> > };
> >
> > +&spi5 {
> > + status = "okay";
> > +
> > + cr50@0 {
>
> Between v2 and v3 of your upstream bindings you changed this from
> "cr50@0" to "tpm@0" in the example. I'm going to assume you did that
> for some reason and you should be matching the binding example here.
> ...or you should change the binding example to be cr50@.
>
Oh yeha, will fix and resend.
>
> > + compatible = "google,cr50";
> > + reg = <0>;
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&h1_ap_int_odl>;
> > + spi-max-frequency = <800000>;
> > + interrupt-parent = <&tlmm>;
> > + interrupts = <129 IRQ_TYPE_EDGE_RISING>;
>
> Certainly we need an interrupt, but I don't see it in the bindings.
> Any idea why it isn't there?
>
I just forward ported the binding and didn't look back. I'm converting
it to YAML so I'll roll that fix in. Thanks.
prev parent reply other threads:[~2019-12-16 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 21:16 [PATCH] arm64: dts: qcom: sdm845-cheza: Add cr50 spi node Stephen Boyd
2019-12-16 22:53 ` Doug Anderson
2019-12-16 23:32 ` Stephen Boyd [this message]
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=5df8141f.1c69fb81.98eee.37b4@mx.google.com \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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