From: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>
To: sedat.dilek@gmail.com
Cc: Samuel Ortiz <sameo@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-wireless@vger.kernel.org, linux-nfc@lists.01.org
Subject: Re: [linux-nfc] ThinkPad T470 and NXP PN5xx (PN547 or PN548)
Date: Sat, 11 May 2019 16:27:59 +0300 [thread overview]
Message-ID: <06fbacb5-7739-1ca1-3bf4-8049a3ef019b@intel.com> (raw)
In-Reply-To: <CA+icZUWhBeup95PTP_k58xs8Lf2Ofqb0S_gkdBfbuc0-wdpF-w@mail.gmail.com>
Hi Sedat,
On 5/10/19 10:40 PM, Sedat Dilek wrote:
> Can you guide me how to do that?
I try and then decide whether this is help or not.
If I remember correctly, support for PN547 was done by multiple parties for some Broadwell based designs through the upstream, both on the kernel and neard side.
Assuming the integration details of PN547 didn’t deviate much, this might be:
- From relatively simple, i.e. getting the relevant data from ACPI and hinting the kernel/driver with a minimally sufficient changes. Most likely, once you sort the basic details (i2c, gpio, etc), everything would just work.
- To more laborious and would require a working and ideally open source reference. An option here might be Broadwell based Chromebooks with PN547 (just not sure whether plain or OEMs).
Regards,
Oleg
next prev parent reply other threads:[~2019-05-11 13:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 13:46 ThinkPad T470 and NXP PN5xx (PN547 or PN548) Sedat Dilek
2019-05-10 7:43 ` Sedat Dilek
2019-05-10 16:40 ` Andy Shevchenko
2019-05-10 19:51 ` Sedat Dilek
2019-05-10 18:55 ` [linux-nfc] " Oleg Zhurakivskyy
2019-05-10 19:40 ` Sedat Dilek
2019-05-11 13:27 ` Oleg Zhurakivskyy [this message]
2019-05-13 9:27 ` Sedat Dilek
2019-05-13 9:50 ` Andy Shevchenko
[not found] ` <CA+icZUWXSup0BfXNZXxcrAAbu-b9KCiBU++OkC+eFqacMrTwRg@mail.gmail.com>
2019-05-13 10:57 ` Andy Shevchenko
2019-05-13 11:07 ` Sedat Dilek
[not found] ` <CA+icZUVDTx_ZUuOgHVDmg5_a4tgrRkPp880+0KPaRJ1d=zF5VQ@mail.gmail.com>
2019-05-13 11:22 ` Sedat Dilek
2019-05-13 12:40 ` Andy Shevchenko
2019-05-13 13:32 ` Sedat Dilek
2019-05-13 14:11 ` Andy Shevchenko
2019-05-13 14:23 ` Sedat Dilek
2019-05-13 19:46 ` Sedat Dilek
2019-05-13 20:02 ` Sedat Dilek
2019-05-13 10:15 ` Oleg Zhurakivskyy
2019-05-13 10:51 ` Sedat Dilek
2019-05-13 11:28 ` Oleg Zhurakivskyy
2019-05-13 11:31 ` Sedat Dilek
2019-05-13 11:50 ` 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=06fbacb5-7739-1ca1-3bf4-8049a3ef019b@intel.com \
--to=oleg.zhurakivskyy@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-nfc@lists.01.org \
--cc=linux-wireless@vger.kernel.org \
--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