Devicetree
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Kristian Brox <isyourbrainfoss@proton.me>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Luca Weiss <luca.weiss@fairphone.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	oe-linux-nfc@lists.linux.dev, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, David Heidelberg <david@ixit.cz>
Subject: Re: [PATCH v3 2/3] nfc: st-nci: add raw NCI path for ST21NFCD
Date: Sun, 23 Aug 2026 10:32:09 +0200	[thread overview]
Message-ID: <4816df55-c486-408b-8aae-80cef532d327@ixit.cz> (raw)
In-Reply-To: <20260820-fp5-st21nfcd-v3-v3-2-5ee0a7f44d04@proton.me>

On 20/08/2026 22:56, Kristian Brox wrote:
> ST21NFCD does not use NDLC. When the compatible is st,st21nfcd,
> talk raw NCI:
> 
> - do not add or strip an NDLC PCB
> - do not run the T1/T2 ACK timers
> - I2C reads are a 3-byte NCI header plus payload
> - skip proprietary SET_NFC_MODE and HCI SE discovery
> 
> Optionally enable clocks (SYS_CLK) and vdd-io (VPS_IO) when the
> DT describes them. Existing st21nfcb / st21nfcc boards keep the
> NDLC path and do not need those properties.
> 
> Tested on Fairphone 5: adapter powers up and reads an NTAG 215.
> 
> Signed-off-by: Kristian Brox <isyourbrainfoss@proton.me>
> ---
>   drivers/nfc/st-nci/core.c |  5 +++
>   drivers/nfc/st-nci/i2c.c  | 87 ++++++++++++++++++++++++++++++++++++++++-------
>   drivers/nfc/st-nci/ndlc.c | 23 +++++++++----
>   drivers/nfc/st-nci/ndlc.h |  2 ++
>   drivers/nfc/st-nci/se.c   |  3 ++
>   5 files changed, 102 insertions(+), 18 deletions(-)
> 

Hello Kristian,

getting better, but still few nitpicls

1. Always To / Cc maintainer :)
2. read the Sashiko review, there is one issue pointed out

see below,

[...]
> @@ -257,23 +318,25 @@ static void st_nci_i2c_remove(struct i2c_client *client)
>   }
>   
>   static const struct i2c_device_id st_nci_i2c_id_table[] = {
> -	{ .name = ST_NCI_DRIVER_NAME },
> -	{ }
> +	{ ST_NCI_DRIVER_NAME },
> +	{}

I believe you reverting recent changes, same below.

>   };
>   MODULE_DEVICE_TABLE(i2c, st_nci_i2c_id_table);
>   
> -static const struct acpi_device_id st_nci_i2c_acpi_match[] = {
> -	{ .id = "SMO2101" },
> -	{ .id = "SMO2102" },
> -	{ }
> +static const struct acpi_device_id st_nci_i2c_acpi_match[] __maybe_unused = {
> +	{"SMO2101"},
> +	{"SMO2102"},
> +	{}
>   };
>   MODULE_DEVICE_TABLE(acpi, st_nci_i2c_acpi_match);
>   
> -static const struct of_device_id of_st_nci_i2c_match[] = {
> -	{ .compatible = "st,st21nfcb-i2c" },
> -	{ .compatible = "st,st21nfcb_i2c" },
> -	{ .compatible = "st,st21nfcc-i2c" },
> -	{ }
> +static const struct of_device_id of_st_nci_i2c_match[] __maybe_unused = {
> +	{ .compatible = "st,st21nfcb-i2c", },
> +	{ .compatible = "st,st21nfcb_i2c", },
> +	{ .compatible = "st,st21nfcc-i2c", },

The `,` above was removed recently, keep it that way ;-)

> +	{ .compatible = "st,st21nfcd",
> +	  .data = (void *)ST_NCI_I2C_PROTO_RAW_NCI },
> +	{}
>   };
>   MODULE_DEVICE_TABLE(of, of_st_nci_i2c_match);
>   
[...]

  parent reply	other threads:[~2026-08-23  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 20:56 [PATCH v3 0/3] nfc: st-nci: Fairphone 5 NFC bring-up (ST21NFCD) Kristian Brox
2026-08-20 20:56 ` [PATCH v3 1/3] dt-bindings: net: nfc: add st,st21nfcd Kristian Brox
2026-08-20 20:56 ` [PATCH v3 2/3] nfc: st-nci: add raw NCI path for ST21NFCD Kristian Brox
2026-08-21 20:56   ` sashiko-bot
2026-08-23  8:32   ` David Heidelberg [this message]
2026-08-20 20:56 ` [PATCH v3 3/3] arm64: dts: qcom: qcm6490-fairphone-fp5: add ST21NFCD NFC Kristian Brox
2026-08-21  6:09 ` [PATCH v3 0/3] nfc: st-nci: Fairphone 5 NFC bring-up (ST21NFCD) Krzysztof Kozlowski
2026-08-21  9:28 ` Luca Weiss
2026-08-23 19:42   ` Kristian Brox

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=4816df55-c486-408b-8aae-80cef532d327@ixit.cz \
    --to=david@ixit.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=isyourbrainfoss@proton.me \
    --cc=krzk@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 \
    /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