From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757383AbcBXNVj (ORCPT <rfc822;w@1wt.eu>);
	Wed, 24 Feb 2016 08:21:39 -0500
Received: from mailout4.samsung.com ([203.254.224.34]:41452 "EHLO
	mailout4.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754921AbcBXNVe (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 24 Feb 2016 08:21:34 -0500
X-AuditID: cbfee61a-f79266d000003652-77-56cdae5c676a
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Alexander Kochetkov <al.kochet@gmail.com>
Cc: Vinod Koul <vinod.koul@intel.com>,
        Dinh Nguyen <dinguyen@opensource.altera.com>, shawn.lin@rockchips.com,
        Addy Ke <addy.ke@rock-chips.com>, Boojin Kim <boojin.kim@samsung.com>,
        wxt@rock-chips.com, dmaengine@vger.kernel.org,
        olof Johansson <olof@lixom.net>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: commit 271e1b86e691 is breaking DMA uart on SoCFPGA
Date: Wed, 24 Feb 2016 14:20:14 +0100
Message-id: <2888688.TklDNiSUc7@amdc1976>
User-Agent: KMail/4.13.3 (Linux/3.13.0-74-generic; KDE/4.13.3; x86_64; ; )
In-reply-to: <CAPUzuU1nDx2PpZrD=JO5mm+Ygq9Pa_zoEjeONqPzzdGvRwb-2A@mail.gmail.com>
References: <56BBB201.7060004@opensource.altera.com>
 <3095560.0L3m2DPBqY@amdc1976>
 <CAPUzuU1nDx2PpZrD=JO5mm+Ygq9Pa_zoEjeONqPzzdGvRwb-2A@mail.gmail.com>
MIME-version: 1.0
Content-transfer-encoding: 7Bit
Content-type: text/plain; charset=us-ascii
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsVy+t9jAd2YdWfDDL5MlbFY9v87k8WKfieL
	Nyf/sFms+rSG2WL11L+sFpd3zWGzOHX9M5vF0sPlFi/79rNYtDcvY3Lg8tg56y67x+I9L5k8
	rpxoYvXovzaJ3ePvrP0sHs8nP2Tx6NuyitHj8ya5AI4oLpuU1JzMstQifbsEroyZH18yFzxi
	r9h8ej5TA2MnWxcjJ4eEgIlE+8f9TBC2mMSFe+uB4lwcQgJLGSV6V85ngnC+Mko8WvmTHaSK
	TcBKYmL7KkYQW0RAV+L72g5GkCJmgTNMEvs6ZwMVcXAICzhIrP7oBVLDIqAqse3nWmYQm1dA
	U2L/5zmsILaogJfEjju7wTZzCgRLnJv0AWrzbEaJC1NvQDUISvyYfI8FxGYWkJfYt38qK4St
	JbF+53GmCYwCs5CUzUJSNgtJ2QJG5lWMEqkFyQXFSem5hnmp5XrFibnFpXnpesn5uZsYwXHy
	TGoH48Fd7ocYBTgYlXh4H2w4EybEmlhWXJl7iFGCg1lJhDdu2tkwId6UxMqq1KL8+KLSnNTi
	Q4zSHCxK4ryP/68LExJITyxJzU5NLUgtgskycXBKNTCe2yLeeXZpk01sjq5l7fGX9ixneaUX
	fF/z+ZSol2TC39OqTxMyc2//9+7UFSoKLQv+6mu88/OhFd7Pd859z7toRe1c6YBypYdZd4Sa
	F+vvfPLG5Xpq6/WTLW7TxZ3kOHa9+DjjacWqW5mMMhyLPlV6rbn+YLNIwEHbQpXNGYaTbzOW
	yppsrWRRYinOSDTUYi4qTgQA3Yez5Y8CAAA=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


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?
> 
> 1) Checkout tree at commit 848e9776fee4 "dmaengine: pl330: support
> burst mode for
>  dev-to-mem and mem-to-dev transmit", make it buildable and see is it
> works. In order to make in buildable remove bursts argument from the
> line:
> 
>     if (*bursts == 1)
>     - return _bursts(pl330, dry_run, buf, pxs, 1);
>     + return _bursts(dry_run, buf, pxs, 1);

This fails (UART DMA doesn't work).

> 2) Checkout next-20160211 kernel tree and set src_maxburst and
> dst_maxburst to 1 inside UART driver to see is it works?

This succeeds (UART DMA works fine).

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics