From: Luca Weiss <luca@z3ntu.xyz>
To: linux-arm-msm@vger.kernel.org, Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 2/2] arm64: dts: qcom: sdm632-fairphone-fp3: Add NFC
Date: Tue, 29 Nov 2022 19:31:47 +0100 [thread overview]
Message-ID: <3134585.5fSG56mABF@g550jk> (raw)
In-Reply-To: <b20432e8-115c-407f-2480-6dd429ce5c25@linaro.org>
On Dienstag, 29. November 2022 14:29:36 CET Konrad Dybcio wrote:
> On 28.11.2022 18:37, Luca Weiss wrote:
> > Configure the node for the NQ310 chip found on this device, which is
> > compatible with generic nxp-nci-i2c driver.
> >
> > Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
> > ---
> > RESEND to fix Cc
> >
> > arch/arm64/boot/dts/qcom/sdm632-fairphone-fp3.dts | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/sdm632-fairphone-fp3.dts
> > b/arch/arm64/boot/dts/qcom/sdm632-fairphone-fp3.dts index
> > 2920504461d3..fde93cbcd180 100644
> > --- a/arch/arm64/boot/dts/qcom/sdm632-fairphone-fp3.dts
> > +++ b/arch/arm64/boot/dts/qcom/sdm632-fairphone-fp3.dts
> > @@ -63,6 +63,21 @@ touchscreen@48 {
> >
> > };
> >
> > };
> >
> > +&i2c_5 {
> > + status = "okay";
> > +
> > + nfc@28 {
> > + compatible = "nxp,nq310", "nxp,nxp-nci-i2c";
>
> Unless there was some binding change (that was not emailed to me with
> this email, I only got 2/2), only "nxp,nxp-nci-i2c" and
> "nxp,pn547", "nxp,nxp-nci-i2c" are allowed.
Yes, I've added the double compatible to the yaml.
https://lore.kernel.org/lkml/20221128173744.833018-1-luca@z3ntu.xyz/
I'll try to work on my Cc-script setup, currently it adds the output of
get_maintainers.pl for each patch (and adds all for the cover letter), which
is based on some script I found a while ago online.
Is there like a recommended way to put all people in Cc for a series, I'm not
aware of anything at least...
Perhaps I'll look into b4 for sending patches, that seems to have some goodies
there.
Regards
Luca
>
> The node looks good though.
>
> Konrad
>
> > + reg = <0x28>;
> > +
> > + interrupt-parent = <&tlmm>;
> > + interrupts = <17 IRQ_TYPE_LEVEL_HIGH>;
> > +
> > + enable-gpios = <&tlmm 16 GPIO_ACTIVE_HIGH>;
> > + firmware-gpios = <&tlmm 62 GPIO_ACTIVE_HIGH>;
> > + };
> > +};
> > +
> >
> > &pm8953_resin {
> >
> > status = "okay";
> > linux,code = <KEY_VOLUMEDOWN>;
next prev parent reply other threads:[~2022-11-29 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:37 [RESEND PATCH 1/2] dt-bindings: nfc: nxp,nci: Document NQ310 compatible Luca Weiss
2022-11-28 17:37 ` [RESEND PATCH 2/2] arm64: dts: qcom: sdm632-fairphone-fp3: Add NFC Luca Weiss
2022-11-29 13:29 ` Konrad Dybcio
2022-11-29 18:31 ` Luca Weiss [this message]
2022-11-30 14:19 ` Konrad Dybcio
2022-11-28 17:46 ` [RESEND PATCH 1/2] dt-bindings: nfc: nxp,nci: Document NQ310 compatible Krzysztof Kozlowski
2022-12-01 5:50 ` patchwork-bot+netdevbpf
2022-12-28 4:36 ` (subset) " Bjorn Andersson
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=3134585.5fSG56mABF@g550jk \
--to=luca@z3ntu.xyz \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).