From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: sedat.dilek@gmail.com
Cc: Samuel Ortiz <sameo@linux.intel.com>,
linux-wireless@vger.kernel.org, linux-nfc@lists.01.org,
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 10:17:12 +0200 [thread overview]
Message-ID: <27f2ce02-8deb-384f-af10-7737b703770a@linaro.org> (raw)
In-Reply-To: <CA+icZUXDLQKyTH-_pPi7A2=Bu5ratwab930Fcecrdr4NtMnFcw@mail.gmail.com>
On 14/05/2019 09:49, Sedat Dilek wrote:
> On Tue, May 14, 2019 at 8:43 AM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
> [...]
>
>> The nxp-nci kernel module is loaded and neard is installed.
>
> You have to...
>
> # modprobe -v nxp-nci_i2c
>
> # lsmod | egrep 'nfc|nci|nxp|i2c' | sort
> i2c_algo_bit 16384 1 i915
> i2c_dev 24576 0
> i2c_i801 32768 0
> nci 77824 2 nxp_nci,nxp_nci_i2c
> nfc 131072 16 nci,nxp_nci
> nxp_nci 16384 1 nxp_nci_i2c
> nxp_nci_i2c 16384 0
> rfkill 28672 10 nfc,bluetooth,thinkpad_acpi,cfg80211
I have the same modules except 'rfkill'
> # modinfo nxp_nci_i2c
> filename:
> /lib/modules/5.1.1-1-amd64-iniza/kernel/drivers/nfc/nxp-nci/nxp-nci_i2c.ko
> author: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>
> author: Clément Perrochaud <clement.perrochaud@nxp.com>
> description: I2C driver for NXP NCI NFC controllers
> license: GPL
> alias: i2c:nxp-nci_i2c
> alias: acpi*:NXP7471:*
> alias: acpi*:NXP1001:*
> alias: of:N*T*Cnxp,nxp-nci-i2cC*
> alias: of:N*T*Cnxp,nxp-nci-i2c
> depends: nci,nxp-nci
> retpoline: Y
> intree: Y
> name: nxp_nci_i2c
> vermagic: 5.1.1-1-amd64-iniza SMP mod_unload modversions
Same result for the modinfo.
-----
So the first time I run:
[mark]
nfctool -d nfc0 -p
Start polling on nfc0 as initiator
With an error in syslog/dmesg:
nci: nci_ntf_packet: unknown ntf opcode 0x0
The second time:
nfctool -p -d nfc0
Protocol error
With an error in syslog/dmesg:
nci: nci_start_poll: failed to set local general bytes
Then I do:
nfctool -0 -d nfc0
it returns to point [mark]
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2019-05-14 8:17 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
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 [this message]
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=27f2ce02-8deb-384f-af10-7737b703770a@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=charles.gorand@effinnov.com \
--cc=clement.perrochaud@effinnov.com \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--cc=oleg.zhurakivskyy@intel.com \
--cc=sameo@linux.intel.com \
--cc=sedat.dilek@gmail.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).