From: David Heidelberg <david@ixit.cz>
To: Kristian Brox <isyourbrainfoss@proton.me>, oe-linux-nfc@lists.linux.dev
Cc: krzk+dt@kernel.org, devicetree@vger.kernel.org,
dmitry.baryshkov@oss.qualcomm.com, luca.weiss@fairphone.com,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: net: nfc: add st,st21nfcd
Date: Wed, 19 Aug 2026 23:47:14 +0200 [thread overview]
Message-ID: <40161970-ae7b-497d-a0ee-98721b0ce6d3@ixit.cz> (raw)
In-Reply-To: <20260819210906.2500789-2-isyourbrainfoss@proton.me>
On 19/08/2026 23:09, Kristian Brox wrote:
> The ST21NFCD (e.g. Fairphone 5) speaks raw NCI on I2C. Existing
> st,st21nfcb-* and st,st21nfcc-i2c compatibles stay NDLC. Add a
> separate compatible so those boards are not switched to the wrong
> framing.
No, this is not reason why do you introduce new compatible. You do it because
it's different HW. The fact it shares the driver is irrelevant in the dt-binding
>
> Also document the optional SYS_CLK (clocks) and VPS_IO (vdd-io-supply)
> used on Fairphone 5, and add an I2C example.
>
> Signed-off-by: Kristian Brox <isyourbrainfoss@proton.me>
> ---
> diff --git a/Documentation/devicetree/bindings/net/nfc/st,st-nci.yaml b/Documentation/devicetree/bindings/net/nfc/st,st-nci.yaml
> index 1dcbddb..4bdbb36 100644
> --- a/Documentation/devicetree/bindings/net/nfc/st,st-nci.yaml
> +++ b/Documentation/devicetree/bindings/net/nfc/st,st-nci.yaml
> @@ -11,10 +11,14 @@ maintainers:
>
> properties:
> compatible:
> + description: |
> + st,st21nfcb-* and st,st21nfcc-i2c use NDLC on the wire.
> + st,st21nfcd is ST21NFCD with raw NCI (no NDLC PCB).
I think you can omit this description completely here, but if someone had better
idea where to put it, I'm open to it.
> enum:
> - st,st21nfcb-i2c
> - st,st21nfcb-spi
> - st,st21nfcc-i2c
> + - st,st21nfcd
>
> reset-gpios:
> description: Output GPIO pin used for resetting the controller
> @@ -36,6 +40,15 @@ properties:
> Specifies that the uicc swp signal can be physically connected to the
> controller
>
> + clocks:
> + maxItems: 1
> + description:
> + External reference clock connected to SYS_CLK.
> +
> + vdd-io-supply:
> + description:
> + Digital I/O supply (VPS_IO).
> +
> required:
> - compatible
> - interrupts
> @@ -49,6 +62,7 @@ if:
> enum:
> - st,st21nfcb-i2c
> - st,st21nfcc-i2c
> + - st,st21nfcd
> then:
> properties:
> spi-max-frequency: false
> @@ -81,6 +95,27 @@ examples:
> };
> };
>
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + nfc@8 {
> + compatible = "st,st21nfcd";
> + reg = <0x08>;
> +
> + interrupt-parent = <&gpio5>;
> + interrupts = <2 IRQ_TYPE_LEVEL_HIGH>;
use interrupts extended (interrupt-parent + interrupts in one line).
As a last point (for the series), never send a new series with Reply-to (as a
followup to existing one). It looks messy, we have tools to track series :)
see: https://patchwork.kernel.org/project/oe-linux-nfc/list/
David
> + reset-gpios = <&gpio5 29 GPIO_ACTIVE_HIGH>;
> +
> + clocks = <&clk>;
> + vdd-io-supply = <&vdd_io>;
> + };
> + };
> +
> - |
> #include <dt-bindings/gpio/gpio.h>
> #include <dt-bindings/interrupt-controller/irq.h>
>
next prev parent reply other threads:[~2026-08-19 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260818205940.1973944-1-isyourbrainfoss@proton.me>
[not found] ` <20260818205940.1973944-2-isyourbrainfoss@proton.me>
2026-08-18 23:22 ` [PATCH 1/3] dt-bindings: net: nfc: add st,st21nfcd-i2c David Heidelberg
2026-08-19 21:09 ` [PATCH v2 0/3] nfc: st-nci: Fairphone 5 NFC bring-up (ST21NFCD) Kristian Brox
2026-08-19 21:09 ` [PATCH v2 1/3] dt-bindings: net: nfc: add st,st21nfcd Kristian Brox
2026-08-19 21:47 ` David Heidelberg [this message]
2026-08-20 6:05 ` Krzysztof Kozlowski
2026-08-19 21:09 ` [PATCH v2 2/3] nfc: st-nci: add raw NCI path for ST21NFCD Kristian Brox
2026-08-19 21:09 ` [PATCH v2 3/3] arm64: dts: qcom: qcm6490-fairphone-fp5: add ST21NFCD NFC Kristian Brox
2026-08-19 21:54 ` David Heidelberg
2026-08-24 8:57 ` Konrad Dybcio
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=40161970-ae7b-497d-a0ee-98721b0ce6d3@ixit.cz \
--to=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=isyourbrainfoss@proton.me \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
/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