From: Oliver Zemann <oliver.zemann@gmail.com>
To: Matthias Klein <matthias.klein@optimeas.de>,
Michal Kazior <michal.kazior@tieto.com>,
Jonas Gorski <jonas.gorski@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: compex wle900vx (ath10k) problem on 4.4.24 / armv7
Date: Wed, 26 Oct 2016 22:25:24 +0200 [thread overview]
Message-ID: <7991f55c-ce11-9261-5c8f-3ff8c051b6d1@gmail.com> (raw)
In-Reply-To: <em1c0906d6-d30a-4f2c-bafb-bfec0d18a58d@nb-mak>
>
>> I (naively) went through pci/pm git log and found the following was
>> applied on 4.7-rc2 (i.e. prior to 4.7 release):
>>
>> commit 006d44e49a259b39947366728d65a873a19aadc0
>> Author: Mika Westerberg <mika.westerberg@linux.intel.com>
>> Date: Thu Jun 2 11:17:15 2016 +0300
>>
>> PCI: Add runtime PM support for PCIe ports
>>
>> From reading the commit log it seems to me like it could be it.
>>
>> ath10k tries to wake up the device during probing before it starts
>> talking to it and it does so through MMIO/PCI config space. If it's
>> not mapped properly then driver will not be able to wake it up and
>> will timeout waiting for it.
>>
>> Can you try cherry-picking it into your 4.4.24 and see if it helps?
>>
>>
> Thanks for the help!
>
> Until now I did not compile a kernel for the board.
> I will give it a try and come back with the results ...
>
>
> Best regards,
> Matthias
>
Any news on that? I am in contact with the support of SolidRun
(clearfog). Unfortunately they will stay at 4.4.x - no upgrade to 4.8
nor 4.9 planned. Unfortunately the commit (006d44e) is incompatible to
4.4. because pci_dev does not know bridge_d3
next prev parent reply other threads:[~2016-10-26 20:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 10:18 compex wle900vx (ath10k) problem on 4.4.24 / armv7 Matthias Klein
2016-10-24 11:40 ` Michal Kazior
2016-10-24 12:08 ` Re[2]: " Matthias Klein
2016-10-24 20:14 ` Oliver Zemann
2016-10-25 5:53 ` Oliver Zemann
2016-10-26 20:25 ` Oliver Zemann [this message]
[not found] ` <386d6f28-9a13-51cc-27ae-0028d517cf27@gmail.com>
2016-10-30 9:08 ` Oliver Zemann
[not found] <b61ccf3c-1861-c8f8-ff7d-91c2b6ff4df5@gmail.com>
2016-10-15 14:00 ` Oliver Zemann
2016-10-15 14:44 ` Sebastian Gottschall
2016-10-15 17:04 ` Oliver Zemann
2016-10-21 16:25 ` Oliver Zemann
2016-10-21 16:54 ` Michal Kazior
2016-10-22 11:55 ` Jonas Gorski
2016-10-23 15:53 ` Oliver Zemann
2016-10-23 19:33 ` Jonas Gorski
2016-10-23 19:42 ` Oliver Zemann
2016-10-24 11:14 ` Jonas Gorski
2016-10-24 18:10 ` Oliver Zemann
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=7991f55c-ce11-9261-5c8f-3ff8c051b6d1@gmail.com \
--to=oliver.zemann@gmail.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.klein@optimeas.de \
--cc=michal.kazior@tieto.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