All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Oleg Zhurakivskyy <oleg.zhurakivskyy@intel.com>,
	Samuel Ortiz <sameo@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: Mon, 13 May 2019 13:57:45 +0300	[thread overview]
Message-ID: <20190513105745.GR9224@smile.fi.intel.com> (raw)
In-Reply-To: <CA+icZUWXSup0BfXNZXxcrAAbu-b9KCiBU++OkC+eFqacMrTwRg@mail.gmail.com>

On Mon, May 13, 2019 at 12:38:27PM +0200, Sedat Dilek wrote:
> On Mon, May 13, 2019 at 11:51 AM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> >
> > On Mon, May 13, 2019 at 11:27:07AM +0200, Sedat Dilek wrote:
> >
> > > Sorry to say, I still have not get all correlations...
> >
> > Can you provide the output of the following on running Linux system with latest
> > possible kernel you can install (I am expecting v5.1) and command line with
> > 'ignore_loglevel'?
> >
> > 1. `dmesg`
> > 2. `grep -H 15 /sys/bus/acpi/devices/*/status`
> > 3. `acpidump -o t470-tables.dat` # the file t470-tables.dat
> > 4. `lspci -vv -nk`
> >
> > P.S. You may use GitHub gist for this set (please, don't share archives) or any
> > other resource like pastebin.
> >
> 
> Looks like I am unable to use Debian's gist-paste package today or
> need more coffee.
> 
> So, I add this here.
> 
> I added my kernel-config.


Thanks. I just sent a series to (hopefully) support it in the vanilla kernel.
Can you test it?

P.S. I see in dmesg the pn544 tries to bind to the NXP1001. Do you have some
custom patches for that in your kernel? If so, please drop them.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2019-05-13 10:57 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
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 [this message]
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=20190513105745.GR9224@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.