Message ID | 20221128173744.833018-2-luca@z3ntu.xyz |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp5838969wrr; Mon, 28 Nov 2022 09:43:56 -0800 (PST) X-Google-Smtp-Source: AA0mqf55DHSB6G2loYryePEMJhFZb9R9qMGdQeavYevLULDQFD6Y5MTT7x6LYlPNbcI0bNSlwazB X-Received: by 2002:a17:906:f858:b0:78d:b654:8af9 with SMTP id ks24-20020a170906f85800b0078db6548af9mr37990742ejb.660.1669657435902; Mon, 28 Nov 2022 09:43:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669657435; cv=none; d=google.com; s=arc-20160816; b=Shoap0Im72ILWSYJjyq8ty4ZXsonfnv/m1dEmAd5kf22E07v7BVCJFj861kTmL3gfM MxBXmw8WRLaoi+EFH1glOiNZ0yfWfPSFJBOz63hwtlbnWEZo1zsKMQ7BzLycYPM3xP1G ZohQYSAkWy4JScM6jTujI5BQISXG/bUcv/5fuH7e3JXpQQi3DGDxaNDshBYv/y79j6vb cfLEidxfF6Qw89pShIPXuCvNsdRZGGyQOKNL3wsZ/8vxABnIAOden/rXFLSLwJF+jPXe a6oUka0u0MfyQwRsvsLICFAgqPFcErj1oBxp9ZTYd8YoiUZKX0CzvsFUESqM4h3P72gW vfPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=Wy4h0xqkV7JNz/NLDf4z170Ertsto4Ihsg5LbYA0pqc=; b=Rp3BVMF1458KF+zYUPSreqaPCydMDfsHqDSPmku4i9/RNZ7yqVMD/WMWw6q07Tq3TG 7F2JNXUQC1EhvicDg9ttpIDMPH2HW4RM4apiE9ttoLDhsNqz9SnMbBRzxduTib754UiJ u4uugytrWkFYIzarGEbswX+1x14lUHrM5c2zLy/d5omw6pwjBPLuUi7LJQcekSYDKPQ/ PctqM08+7Hw3eOTvnPB1PMZRcS42x0vimAMyiicEKTGXQ2mu3fWPIv3dGQSCxU0qADNw IxlRrIiggFcpwXNm1FvxDZgHpPo3Jz05q5+bZRcribVHGiOwfhpcoNJOjpHr3ORyR33U B4Fg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@z3ntu.xyz header.s=z3ntu header.b=TVVsX0g9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=z3ntu.xyz Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k26-20020a50ce5a000000b00459195ae973si9756344edj.414.2022.11.28.09.43.31; Mon, 28 Nov 2022 09:43:55 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=fail header.i=@z3ntu.xyz header.s=z3ntu header.b=TVVsX0g9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=z3ntu.xyz Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233018AbiK1RnH (ORCPT <rfc822;gah0developer@gmail.com> + 99 others); Mon, 28 Nov 2022 12:43:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52130 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233336AbiK1Rmm (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 28 Nov 2022 12:42:42 -0500 Received: from mail.z3ntu.xyz (mail.z3ntu.xyz [128.199.32.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E0DBB2AC5D; Mon, 28 Nov 2022 09:40:06 -0800 (PST) Received: from g550jk.arnhem.chello.nl (unknown [62.108.10.64]) by mail.z3ntu.xyz (Postfix) with ESMTPSA id 41157D1E0D; Mon, 28 Nov 2022 17:40:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=z3ntu.xyz; s=z3ntu; t=1669657205; bh=TWqeYHtpfShiGBY9gIUol/DHR5TcnuSKzaWiN7BTc38=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=TVVsX0g9zlGL4sd9s2Be0rq1T8qZFmmyqUXDVdPDfEvWv8Ammmm8R2MgXPYQ5iw8X ZwV1FjEqkJB5QwqPEtP8deTjIRzzGsh/EXjAj++lQ8ZYHGqZjrVRRwhCl3X8AB8Oqo RAW7BNygBVO7QKa0cjb6B3bbobY0WBle2VF9tzV4= From: Luca Weiss <luca@z3ntu.xyz> To: linux-arm-msm@vger.kernel.org Cc: ~postmarketos/upstreaming@lists.sr.ht, phone-devel@vger.kernel.org, Luca Weiss <luca@z3ntu.xyz>, Andy Gross <agross@kernel.org>, Bjorn Andersson <andersson@kernel.org>, Konrad Dybcio <konrad.dybcio@somainline.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [RESEND PATCH 2/2] arm64: dts: qcom: sdm632-fairphone-fp3: Add NFC Date: Mon, 28 Nov 2022 18:37:44 +0100 Message-Id: <20221128173744.833018-2-luca@z3ntu.xyz> X-Mailer: git-send-email 2.38.1 In-Reply-To: <20221128173744.833018-1-luca@z3ntu.xyz> References: <20221128173744.833018-1-luca@z3ntu.xyz> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROM_SUSPICIOUS_NTLD, PDS_OTHER_BAD_TLD,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1750762715281862775?= X-GMAIL-MSGID: =?utf-8?q?1750762715281862775?= |
Series |
[RESEND,1/2] dt-bindings: nfc: nxp,nci: Document NQ310 compatible
|
|
Commit Message
Luca Weiss
Nov. 28, 2022, 5:37 p.m. UTC
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(+)
Comments
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. 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>;
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>;
On 29.11.2022 19:31, Luca Weiss wrote: > 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/ Ok, this looks good then. Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org> > > 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. Check out this reply from Rob Herring here https://lore.kernel.org/lkml/CAL_JsqLubWBr2W3xZPsuPLOGav7CFgBdH=aCfT22F_m0_cx3cQ@mail.gmail.com/ Konrad > > 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>; > > > >
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"; + 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>;