From: David Heidelberg <david@ixit.cz>
To: Kristian Brox <isyourbrainfoss@proton.me>, oe-linux-nfc@lists.linux.dev
Cc: krzysztof.kozlowski@linaro.org, luca.weiss@fairphone.com,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: net: nfc: add st,st21nfcd-i2c
Date: Wed, 19 Aug 2026 01:22:31 +0200 [thread overview]
Message-ID: <babb5c20-1b95-481a-b0af-1d581425d37b@ixit.cz> (raw)
In-Reply-To: <20260818205940.1973944-2-isyourbrainfoss@proton.me>
On 18/08/2026 22:59, 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.
>
> Also document the difference and add an I2C example without
> ese-present / uicc-present.
>
> 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 1dcbddbc5..3523a8df0 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-i2c is ST21NFCD with raw NCI (no NDLC PCB).
> enum:
> - st,st21nfcb-i2c
> - st,st21nfcb-spi
> - st,st21nfcc-i2c
> + - st,st21nfcd-i2c
Hello Kristian.
Thank you for your patches!
Before I do full review, for next revision, definitely the compatible should
omit -i2c suffix, thus only `st,st21nfcd`.
If possible, send next revision with b4 (thou you don't have to, it's usually
more fancy and convenient for both parties, takes care about CCing the right
people, checkpatch etc.) [1].
Thanks
David
[1] https://b4.docs.kernel.org/en/latest/contributor/overview.html
[...]
next parent reply other threads:[~2026-08-18 23:22 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 ` David Heidelberg [this message]
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
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=babb5c20-1b95-481a-b0af-1d581425d37b@ixit.cz \
--to=david@ixit.cz \
--cc=isyourbrainfoss@proton.me \
--cc=krzysztof.kozlowski@linaro.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