在 2016年02月24日 21:24, Bartlomiej Zolnierkiewicz 写道:
Hi,
On Wednesday, February 24, 2016 02:01:59 PM Caesar Wang wrote:
Hi,
Thanks Dinh & Alexander for the intergration testing.
---
@Dinh,
Can you test it again with the patch[0]?
patch[0]:
https://patchwork.kernel.org/patch/8398511/
This
在 2016年02月24日 21:24, Bartlomiej Zolnierkiewicz 写道:
Hi,
On Wednesday, February 24, 2016 02:01:59 PM Caesar Wang wrote:
Hi,
Thanks Dinh & Alexander for the intergration testing.
---
@Dinh,
Can you test it again with the patch[0]?
patch[0]:
https://patchwork.kernel.org/patch/8398511/
This
Hi,
On Wednesday, February 24, 2016 02:01:59 PM Caesar Wang wrote:
> Hi,
>
> Thanks Dinh & Alexander for the intergration testing.
>
> ---
>
> @Dinh,
>
> Can you test it again with the patch[0]?
>
> patch[0]:
> https://patchwork.kernel.org/patch/8398511/
This fixes the problem for me
Hi,
On Wednesday, February 24, 2016 02:01:59 PM Caesar Wang wrote:
> Hi,
>
> Thanks Dinh & Alexander for the intergration testing.
>
> ---
>
> @Dinh,
>
> Can you test it again with the patch[0]?
>
> patch[0]:
> https://patchwork.kernel.org/patch/8398511/
This fixes the problem for me
Hi,
On Thursday, February 18, 2016 07:07:28 PM Alexander Kochetkov wrote:
> Hello!
>
> Bartlomiej, could you please tell what uart driver is used on Samsung
> Exynos4412?
> Dinh, could you please tell what uart driver is used on SoCFPGA?
drivers/tty/serial/samsung.c
> Could you make two test?
Hi,
On Thursday, February 18, 2016 07:07:28 PM Alexander Kochetkov wrote:
> Hello!
>
> Bartlomiej, could you please tell what uart driver is used on Samsung
> Exynos4412?
> Dinh, could you please tell what uart driver is used on SoCFPGA?
drivers/tty/serial/samsung.c
> Could you make two test?
Hi,
Thanks Dinh & Alexander for the intergration testing.
---
@Dinh,
Can you test it again with the patch[0]?
patch[0]:
https://patchwork.kernel.org/patch/8398511/
-
Caesar
在 2016年02月23日 23:14, Dinh Nguyen 写道:
Hi,
Sorry that I couldn't get to this sooner.
On 02/18/2016 10:07 AM,
Hi,
Thanks Dinh & Alexander for the intergration testing.
---
@Dinh,
Can you test it again with the patch[0]?
patch[0]:
https://patchwork.kernel.org/patch/8398511/
-
Caesar
在 2016年02月23日 23:14, Dinh Nguyen 写道:
Hi,
Sorry that I couldn't get to this sooner.
On 02/18/2016 10:07 AM,
Hi,
Sorry that I couldn't get to this sooner.
On 02/18/2016 10:07 AM, Alexander Kochetkov wrote:
> Hello!
>
> Bartlomiej, could you please tell what uart driver is used on Samsung
> Exynos4412?
> Dinh, could you please tell what uart driver is used on SoCFPGA?
>
SoCFPGA is using the 8250_dw.c
Hi,
Sorry that I couldn't get to this sooner.
On 02/18/2016 10:07 AM, Alexander Kochetkov wrote:
> Hello!
>
> Bartlomiej, could you please tell what uart driver is used on Samsung
> Exynos4412?
> Dinh, could you please tell what uart driver is used on SoCFPGA?
>
SoCFPGA is using the 8250_dw.c
Hello, here comments from Shawn Lin:
19 февр. 2016 г., в 9:46, Shawn Lin написал(а):
Seriously review the patch again, commit 271e1b86e691 "dmaengine:
pl330: add quirk for broken no flushp" has not chance to break
the platforms which don't add quirk inside the dts
Hello, here comments from Shawn Lin:
19 февр. 2016 г., в 9:46, Shawn Lin написал(а):
Seriously review the patch again, commit 271e1b86e691 "dmaengine:
pl330: add quirk for broken no flushp" has not chance to break
the platforms which don't add quirk inside the dts stuff.
as well as the other
Hello!
Bartlomiej, could you please tell what uart driver is used on Samsung
Exynos4412?
Dinh, could you please tell what uart driver is used on SoCFPGA?
Could you make two test?
1) Checkout tree at commit 848e9776fee4 "dmaengine: pl330: support
burst mode for
dev-to-mem and mem-to-dev
Hello!
Bartlomiej, could you please tell what uart driver is used on Samsung
Exynos4412?
Dinh, could you please tell what uart driver is used on SoCFPGA?
Could you make two test?
1) Checkout tree at commit 848e9776fee4 "dmaengine: pl330: support
burst mode for
dev-to-mem and mem-to-dev
Hi,
On Thursday, February 11, 2016 02:27:51 PM Vinod Koul wrote:
> On Wed, Feb 10, 2016 at 03:56:17PM -0600, Dinh Nguyen wrote:
> > Hi Vinod,
> >
> > It appears that commit 271e1b86e691 "dmaengine: pl330: add quirk for
> > broken no flushp" is breaking uart dma on SoCFPGA. This commit is in
> >
Hi,
On Thursday, February 11, 2016 02:27:51 PM Vinod Koul wrote:
> On Wed, Feb 10, 2016 at 03:56:17PM -0600, Dinh Nguyen wrote:
> > Hi Vinod,
> >
> > It appears that commit 271e1b86e691 "dmaengine: pl330: add quirk for
> > broken no flushp" is breaking uart dma on SoCFPGA. This commit is in
> >
On Wed, Feb 10, 2016 at 03:56:17PM -0600, Dinh Nguyen wrote:
> Hi Vinod,
>
> It appears that commit 271e1b86e691 "dmaengine: pl330: add quirk for
> broken no flushp" is breaking uart dma on SoCFPGA. This commit is in
> linux-next(next-20160210).
>
> Doing a bisect pointed to commit 271e1b86e691,
On Wed, Feb 10, 2016 at 03:56:17PM -0600, Dinh Nguyen wrote:
> Hi Vinod,
>
> It appears that commit 271e1b86e691 "dmaengine: pl330: add quirk for
> broken no flushp" is breaking uart dma on SoCFPGA. This commit is in
> linux-next(next-20160210).
>
> Doing a bisect pointed to commit 271e1b86e691,
Hi Vinod,
It appears that commit 271e1b86e691 "dmaengine: pl330: add quirk for
broken no flushp" is breaking uart dma on SoCFPGA. This commit is in
linux-next(next-20160210).
Doing a bisect pointed to commit 271e1b86e691, but I had to also revert
the following commits (86a8ce7d4103 "dmaengine:
Hi Vinod,
It appears that commit 271e1b86e691 "dmaengine: pl330: add quirk for
broken no flushp" is breaking uart dma on SoCFPGA. This commit is in
linux-next(next-20160210).
Doing a bisect pointed to commit 271e1b86e691, but I had to also revert
the following commits (86a8ce7d4103 "dmaengine:
20 matches
Mail list logo