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: Sun, 19 May 2019 18:46:52 +0200 [thread overview]
Message-ID: <525160f3-a76c-4b45-2e05-c27aaabbf74d@linaro.org> (raw)
In-Reply-To: <CA+icZUVaBdswfmRfbRtdVJY8ymeDOwDSFEf7G6jneqEmpW84bg@mail.gmail.com>
FYI, when I tried to make the NFC work on my x280, I tried the module at:
https://github.com/jr64/nxp-pn5xx
AFAIR, it finally worked somehow.
May be you can cross check with your series and the change in this
module to find out what could be missing? (I can do that but it will be
certainly easier for you spot something in the code you wrote).
I can experiment your changes in my laptop if needed.
On 14/05/2019 16:59, Sedat Dilek wrote:
> On Tue, May 14, 2019 at 10:17 AM Daniel Lezcano
> <daniel.lezcano@linaro.org> wrote:
> [...]
>
> Just for the records:
>
> root@iniza:~# rfkill --output ID,TYPE
> ID TYPE
> 0 bluetooth
> 1 nfc
> 2 wlan
> 3 bluetooth
>
> root@iniza:~# rfkill list nfc
> 1: nfc0: NFC
> Soft blocked: no
> Hard blocked: no
>
> - Sedat -
>
--
<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-19 17:19 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
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 [this message]
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=525160f3-a76c-4b45-2e05-c27aaabbf74d@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