From: Rajkumar Manoharan <rmanohar@codeaurora.org>
To: Ben Greear <greearb@candelatech.com>
Cc: nbd@openwrt.org, ath10k@lists.infradead.org, "Manoharan,
Rajkumar" <rmanohar@qti.qualcomm.com>,
"Valo, Kalle" <kvalo@qca.qualcomm.com>,
nbd@nbd.name
Subject: Re: Regression in qca99x0 on x86 platform (kernel: 4.7.0-rc1-wt-ath
Date: Wed, 15 Jun 2016 08:25:34 +0530 [thread overview]
Message-ID: <f91f033b77e415fc14f94d5890115e09@codeaurora.org> (raw)
In-Reply-To: <57600A3C.9000104@candelatech.com>
On 2016-06-14 19:14, Ben Greear wrote:
> On 06/13/2016 11:21 PM, Rajkumar Manoharan wrote:
>> On 2016-06-02 23:22, Ben Greear wrote:
>
>>> At the time, I bisected to this commit as well, but I decided to just
>>> live with it
>>> since it seemed it fixed some other bug and we had a work-around. My
>>> understanding
>>> is that without the patch above, some ARM systems failed to work.
>>>
>> Ben,
>>
>> I posted a fix for the freeze issue
>> (https://patchwork.kernel.org/patch/9175029/). Can you please give a
>> try with VT-d disabled?
>>
>> -Rajkumar
>
> Yes, but it might be a bit. I just ported my patches to 4.7, and will
> add yours
> there. We are mainly focussed on getting a stable 4.4+ out the door
> currently though.
>
Thanks..
> Were you able to test on the ARM platform that originally had the
> problem that
> Felix's patch was supposed to fix?
>
I tested this patch on ARM platform. Unfortunately I did not observe
original dma_alloc_coherent failures. Felix replaced dma_alloc_coherent
by kmalloc + dma_map_single. I retained the logic as it is. Thee change
is that host memory chuck size for target is limited by 256 KiB.
-Rajkumar
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-06-15 2:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 17:20 Regression in qca99x0 on x86 platform (kernel: 4.7.0-rc1-wt-ath Manoharan, Rajkumar
2016-06-02 17:27 ` Ben Greear
2016-06-02 17:46 ` Rajkumar Manoharan
2016-06-02 17:52 ` Ben Greear
2016-06-14 6:21 ` Rajkumar Manoharan
2016-06-14 13:44 ` Ben Greear
2016-06-15 2:55 ` Rajkumar Manoharan [this message]
2016-06-03 16:02 ` Valo, Kalle
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=f91f033b77e415fc14f94d5890115e09@codeaurora.org \
--to=rmanohar@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=greearb@candelatech.com \
--cc=kvalo@qca.qualcomm.com \
--cc=nbd@nbd.name \
--cc=nbd@openwrt.org \
--cc=rmanohar@qti.qualcomm.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