From: Sedat Dilek <sedat.dilek@gmail.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
linux-wireless@vger.kernel.org, linux-nfc@lists.01.org,
robert.dolca@intel.com, oleg.zhurakivskyy@intel.com,
clement.perrochaud@effinnov.com, charles.gorand@effinnov.com,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: NXP NFC version and ACPI
Date: Tue, 14 May 2019 08:52:15 +0200 [thread overview]
Message-ID: <CA+icZUWLBjTtcFS0Fo8M5gSb90GbEUpetUgwr3fy=NxGAVqCyw@mail.gmail.com> (raw)
In-Reply-To: <5ae87449-83a1-ecce-c72c-b4742c507497@linaro.org>
On Tue, May 14, 2019 at 8:43 AM Daniel Lezcano
<daniel.lezcano@linaro.org> wrote:
>
> On 13/05/2019 22:15, Sedat Dilek wrote:
> > On Wed, Dec 5, 2018 at 8:38 AM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
> >>
> >>
> >> Hi,
> >>
> >> the discussion reference is on github [1].
> >>
> >> I acquired a Lenovo x280 with a NFC chip. It is unclear what chip is it
> >> really, it is called NXP NPC300 which could be a PN7xxx chip range.
> >>
> >> A hacked version of an old deprecated out-of-tree module made the PN5xxx
> >> to work with my laptop but I suspect it brought some subtle instability
> >> on my system.
> >>
> >> Now it would be nice to have this correctly supported upstream.
> >>
> >> I dumped the ACPI DSDT table and got the id NXP1001. This one is not
> >> listed in the match table of the nxp-nci driver.
> >>
> >> - is the driver missing for the so called NXP NPC300 ?
> >> - should the NXP1001 matching string to be added to nxp-nci?
> >> - is my firmware sending me garbage ?
> >>
> >> Thanks in advance for any input
> >>
> >
> > [ CC Andy ]
> >
> > Hi Daniel,
> >
> > I was able to get a NXP NPC300 NFC device run on Lenovo ThinkPad T470.
> >
> > Look at the patchset "[PATCH v2 00/12] NFC: nxp-nci: clean up and
> > support new ID".
> > I have tested on top of Linux v5.1.1.
>
> Hi Sedat,
>
> yes, I have them see. Thanks for letting me know.
>
> > Here I have set...
> >
> > scripts/config -m NFC_NCI -m NFC_NXP_NCI -m NFC_NXP_NCI_I2C -e
> > PINCTRL_SUNRISEPOINT
> >
> > Please give this a try and report.
>
> My laptop is the first one I have with a NFC reader, so I'm not used to
> test this as it was not working yet.
>
> I booted the machine with a 5.1.1, the series applied on top, and the
> config options set as mentioned above.
>
> The nxp-nci kernel module is loaded and neard is installed.
>
> I used the sniffing tool with the command libnfc -d nfc0 -n but when
> passing my NFC devices on the laptop's NFC mark, nothing happens.
>
> Is that correct?
>
Hi Daniel,
I am new to the topic Linux NFC.
I have installed neard (daemon) v0.16 and neard-tools from Debian/buster AMD64.
root@iniza:~# systemctl is-active neard.service
active
root@iniza:~# nfctool --list
nfc0:
Tags: [ ]
Devices: [ ]
Protocols: [ Felica MIFARE Jewel ISO-DEP NFC-DEP ]
Powered: No
RF Mode: None
lto: 150
rw: 15
miux: 2047
root@iniza:~# nfctool --poll -d nfc0
Start polling on nfc0 as initiator
...
Throwing my YubiKey Neo-5 NFC on my ThinkPad T470 NFC sticker shows me...
Targets found for nfc0
Tags: [ tag0 ]
Devices: [ ]
Hope that helps.
Regards,
- Sedat -
next prev parent reply other threads:[~2019-05-14 6:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 7:38 NXP NFC version and ACPI Daniel Lezcano
2018-12-13 20:44 ` Daniel Lezcano
2018-12-13 20:50 ` [linux-nfc] " Anders Rundgren
2018-12-13 20:57 ` Daniel Lezcano
2018-12-13 21:11 ` Anders Rundgren
2019-05-13 20:15 ` Sedat Dilek
2019-05-14 6:42 ` Daniel Lezcano
2019-05-14 6:52 ` Sedat Dilek [this message]
2019-05-14 6:56 ` Sedat Dilek
2019-05-14 6:57 ` Daniel Lezcano
2019-05-14 7:12 ` Sedat Dilek
2019-05-14 7:49 ` Sedat Dilek
2019-05-14 8:17 ` Daniel Lezcano
2019-05-14 8:30 ` Sedat Dilek
2019-05-14 14:59 ` Sedat Dilek
2019-05-14 16:36 ` Daniel Lezcano
2019-05-19 16:46 ` Daniel Lezcano
2019-05-29 9:33 ` Sedat Dilek
2019-08-05 19:40 ` Sedat Dilek
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='CA+icZUWLBjTtcFS0Fo8M5gSb90GbEUpetUgwr3fy=NxGAVqCyw@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=charles.gorand@effinnov.com \
--cc=clement.perrochaud@effinnov.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=oleg.zhurakivskyy@intel.com \
--cc=robert.dolca@intel.com \
--cc=sameo@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).