On 2019-11-06 18:01, Tom Psyborg wrote:
On 30/10/2019, zhic...@codeaurora.org wrote:
On 2019-10-22 18:07, Tom Psyborg wrote:
What about main and 10x firmware branch?
There is no code changes in firmware. It's a configuration change of
host memory access.
Zhi
Please change it for main
On 30/10/2019, zhic...@codeaurora.org wrote:
> On 2019-10-22 18:07, Tom Psyborg wrote:
>
>> What about main and 10x firmware branch?
>
> There is no code changes in firmware. It's a configuration change of
> host memory access.
>
> Zhi
>
Please change it for main and 10x branch too. Dumping
On 30/10/2019, zhic...@codeaurora.org wrote:
> On 2019-10-23 01:16, Peter Oh wrote:
>>
>> How can you say value 0 (I believe it's 64 bytes) DMA burst size
>> causes the symptom and 1 fixes it?
>>
>> Peter
>
> Confirmed from HW team that the configuration controls AXI burst size of
> the RD/WR
On 10/29/19 11:16 PM, zhic...@codeaurora.org wrote:
On 2019-10-23 01:16, Peter Oh wrote:
How can you say value 0 (I believe it's 64 bytes) DMA burst size
causes the symptom and 1 fixes it?
Peter
Confirmed from HW team that the configuration controls AXI burst size
of the RD/WR access to
On 2019-10-23 02:24, Adrian Chadd wrote:
On Tue, 22 Oct 2019 at 10:17, Peter Oh wrote:
On 10/22/19 1:57 AM, Zhi Chen wrote:
> This reverts commit 76d164f582150fd0259ec0fcbc485470bcd8033e.
> PCIe hung issue was observed on multiple platforms. The issue was reproduced
> when DUT was configured
On 2019-10-23 01:16, Peter Oh wrote:
How can you say value 0 (I believe it's 64 bytes) DMA burst size
causes the symptom and 1 fixes it?
Peter
Confirmed from HW team that the configuration controls AXI burst size of
the RD/WR access to the HOST MEM.
0- No split , RAW read/write transfer
On 10/22/19 11:24 AM, Adrian Chadd wrote:
On Tue, 22 Oct 2019 at 10:17, Peter Oh wrote:
On 10/22/19 1:57 AM, Zhi Chen wrote:
This reverts commit 76d164f582150fd0259ec0fcbc485470bcd8033e.
PCIe hung issue was observed on multiple platforms. The issue was reproduced
when DUT was configured as
On 2019-10-22 18:07, Tom Psyborg wrote:
What about main and 10x firmware branch?
There is no code changes in firmware. It's a configuration change of
host memory access.
Zhi
___
ath10k mailing list
ath10k@lists.infradead.org
On Tue, 22 Oct 2019 at 10:17, Peter Oh wrote:
>
>
> On 10/22/19 1:57 AM, Zhi Chen wrote:
> > This reverts commit 76d164f582150fd0259ec0fcbc485470bcd8033e.
> > PCIe hung issue was observed on multiple platforms. The issue was reproduced
> > when DUT was configured as AP and associated with 50+
On 10/22/19 1:57 AM, Zhi Chen wrote:
This reverts commit 76d164f582150fd0259ec0fcbc485470bcd8033e.
PCIe hung issue was observed on multiple platforms. The issue was reproduced
when DUT was configured as AP and associated with 50+ STAs.
With PCIe protocol analyzer, we can see DMA Read crossing
On 22/10/2019, Zhi Chen wrote:
> This reverts commit 76d164f582150fd0259ec0fcbc485470bcd8033e.
> PCIe hung issue was observed on multiple platforms. The issue was
> reproduced
> when DUT was configured as AP and associated with 50+ STAs.
>
> With PCIe protocol analyzer, we can see DMA Read
11 matches
Mail list logo
