public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <2888688.TklDNiSUc7@amdc1976> (raw)
In-Reply-To: <CAPUzuU1nDx2PpZrD=JO5mm+Ygq9Pa_zoEjeONqPzzdGvRwb-2A@mail.gmail.com>


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

  parent reply	other threads:[~2016-02-24 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 21:56 commit 271e1b86e691 is breaking DMA uart on SoCFPGA Dinh Nguyen
2016-02-11  8:57 ` Vinod Koul
2016-02-17 11:12   ` Bartlomiej Zolnierkiewicz
2016-02-18 16:07     ` Alexander Kochetkov
2016-02-23 15:14       ` Dinh Nguyen
2016-02-24  6:01         ` Caesar Wang
2016-02-24 13:24           ` Bartlomiej Zolnierkiewicz
2016-02-25  0:29             ` Caesar Wang
2016-02-24 13:20       ` Bartlomiej Zolnierkiewicz [this message]
2016-02-19  6:51     ` Alexander Kochetkov

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=2888688.TklDNiSUc7@amdc1976 \
    --to=b.zolnierkie@samsung.com \
    --cc=addy.ke@rock-chips.com \
    --cc=al.kochet@gmail.com \
    --cc=boojin.kim@samsung.com \
    --cc=dinguyen@opensource.altera.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=shawn.lin@rockchips.com \
    --cc=vinod.koul@intel.com \
    --cc=wxt@rock-chips.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