From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>,
David Heidelberg <david@ixit.cz>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Luca Weiss <luca.weiss@fairphone.com>,
oe-linux-nfc@lists.linux.dev, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/5] arm64: dts: qcom: milos-fairphone-fp6: Add NFC
Date: Mon, 27 Jul 2026 12:07:22 +0200 [thread overview]
Message-ID: <7ab0655a-52ac-4b15-9223-753c146a9469@oss.qualcomm.com> (raw)
In-Reply-To: <20260726222405.153008-6-jorijnvdgraaf@catcrafts.net>
On 7/27/26 12:24 AM, Jorijn van der Graaf wrote:
> Add the Samsung S3NRN4V NCI NFC controller on i2c1. Its XI clock is
> provided by the RF_CLK2 PMIC buffer and gated through the controller's
> CLK_REQ line on tlmm GPIO6. PVDD is fed from PM7550 LDO20, the rail the
> downstream driver switches for this chip.
>
> The enable line is routed to the chip's power-down input, which is
> asserted high to turn the chip off (the downstream driver treats VEN as
> active-low on this design) -- hence GPIO_ACTIVE_HIGH, unlike the
> exynos5433-tm2 wiring of the same driver. The pin is pulled up so the
> chip stays off while the line is not driven.
>
> Assisted-by: Claude:claude-opus-4-8
> Assisted-by: Claude:claude-fable-5
> Signed-off-by: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>
> ---
> .../boot/dts/qcom/milos-fairphone-fp6.dts | 49 ++++++++++++++++++-
> 1 file changed, 47 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/milos-fairphone-fp6.dts b/arch/arm64/boot/dts/qcom/milos-fairphone-fp6.dts
> index ebdca0e2d2f3..a1b86e4092fe 100644
> --- a/arch/arm64/boot/dts/qcom/milos-fairphone-fp6.dts
> +++ b/arch/arm64/boot/dts/qcom/milos-fairphone-fp6.dts
> @@ -601,9 +601,29 @@ &gcc {
> };
>
> &i2c1 {
> - /* Samsung NFC @ 0x27 */
> -
> status = "okay";
> +
> + /*
> + * Samsung S3NRN4V NFC controller. XI is driven by the RF_CLK2 PMIC
> + * buffer; the chip has no oscillator of its own and gates the clock
> + * via its CLK_REQ line, so the clock must be voted on in response
> + * to it.
> + */
This seems like something that's more fitting of the commit message
and/or dt-bindings (either description: or in a YAML comment)
> + nfc@27 {
> + compatible = "samsung,s3nrn4v";
> + reg = <0x27>;
> +
> + clk-req-gpios = <&tlmm 6 GPIO_ACTIVE_HIGH>;
> + clocks = <&rpmhcc RPMH_RF_CLK2>;
> + en-gpios = <&tlmm 56 GPIO_ACTIVE_HIGH>;
> + interrupt-parent = <&tlmm>;
> + interrupts = <31 IRQ_TYPE_EDGE_RISING>;
interrupts-extended = <&tlmm 31 IRQ..>
> + pinctrl-0 = <&nfc_clk_req_default>, <&nfc_irq_default>,
> + <&nfc_pd_default>;
You can create a group of pins (see below
> + pinctrl-names = "default";
> + pvdd-supply = <&vreg_l20b>;
> + wake-gpios = <&tlmm 7 GPIO_ACTIVE_HIGH>;
Please group the -gpios properties together
> + };
> };
>
> &i2c3 {
> @@ -825,6 +845,31 @@ &tlmm {
> <13 1>, /* NC */
> <63 2>; /* WLAN UART */
>
> + nfc_clk_req_default: nfc-clk-req-default-state {
> + pins = "gpio6";
> + function = "gpio";
> + drive-strength = <2>;
> + bias-disable;
> + };
> +
> + nfc_irq_default: nfc-irq-default-state {
> + pins = "gpio31";
> + function = "gpio";
> + drive-strength = <2>;
> + bias-disable;
> + };
> +
> + /*
> + * Pulled up so the NFC chip stays powered down while the line is
> + * not driven (it is the chip's active-high power-down input).
> + */
> + nfc_pd_default: nfc-pd-default-state {
> + pins = "gpio56";
> + function = "gpio";
> + drive-strength = <2>;
> + bias-pull-up;
> + };
You can group them into something like:
nfc_default_state: nfc-default-state {
nfc-clk-req-default-pins {
gpios = ""
...
};
...
};
Konrad
next prev parent reply other threads:[~2026-07-27 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 22:24 [PATCH v3 0/5] nfc: s3fwrn5: support the S3NRN4V variant Jorijn van der Graaf
2026-07-26 22:24 ` [PATCH v3 1/5] nfc: s3fwrn5: drop of_match_ptr() from the I2C driver Jorijn van der Graaf
2026-07-26 22:24 ` [PATCH v3 2/5] nfc: s3fwrn5: use the "s3fwrn5_i2c" string literal directly Jorijn van der Graaf
2026-07-26 22:24 ` [PATCH v3 3/5] dt-bindings: net: nfc: samsung,s3fwrn5: add S3NRN4V and clk-req-gpios Jorijn van der Graaf
2026-07-26 22:24 ` [PATCH v3 4/5] nfc: s3fwrn5: support the S3NRN4V variant Jorijn van der Graaf
2026-07-26 22:24 ` [PATCH v3 5/5] arm64: dts: qcom: milos-fairphone-fp6: Add NFC Jorijn van der Graaf
2026-07-27 10:07 ` Konrad Dybcio [this message]
2026-08-03 8:02 ` Luca Weiss
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=7ab0655a-52ac-4b15-9223-753c146a9469@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=jorijnvdgraaf@catcrafts.net \
--cc=konradybcio@kernel.org \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=robh@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