mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Kochetkov <al.kochet@gmail.com>
To: "Dan Williams" <dan.j.williams@intel.com>,
	"Vinod Koul" <vinod.koul@intel.com>,
	dmaengine@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-rockchip@lists.infradead.org, hhb <hhb@rock-chips.com>,
	"Shawn Lin" <shawn.lin@rock-chips.com>,
	王晓腾 <caesar.wang@rock-chips.com>,
	张学广 <sugar.zhang@rock-chips.com>,
	黄涛 <ulysses.huang@rock-chips.com>,
	"Stephen Barber" <smbarber@chromium.org>,
	"Krzysztof Kozlowski" <krzk@kernel.org>
Subject: Re: [PATCH 0/2] Free running cyclic transfer implementation for pl330
Date: Wed, 26 Apr 2017 20:01:55 +0300	[thread overview]
Message-ID: <FFF03FEC-4C86-4E2E-BC45-1C8694243203@gmail.com> (raw)
In-Reply-To: <1492180531-1780-1-git-send-email-al.kochet@gmail.com>

Hello!

Just to let you know, that I got following test report from Stephen (thanks a lot!).

The patch won’t work due to full cyclic transfer doesn’t fit into mcbufsz (256 bytes long).
His application requested driver to do cyclic transfer with large number of cycles.
pl330 microcode has restriction on how far PC can change and this limit is 256 bytes,
so increasing mcbufsz will not solve problem. Don’t want to make jump bridges or
something like on the fly CPU modified microcode.

> 14 апр. 2017 г., в 23:24, Stephen Barber <smbarber@chromium.org> написал(а):
> 
> Hi Alexander,
> 
> Thanks for your patches!
> 
> I gave them a try on kevin (Samsung Chromebook Plus) with our
> chromeos-4.4 kernel branch, plus some cherry-picks on top to get
> things to apply cleanly. Here's what my tree looks like:
> 
> 344daf13fa4e (HEAD -> apply-pl330) dmaengine: pl330: don't emit code
> for one iteration loop
> 062596b83fec dmaengine: pl330: make cyclic transfer free runnable
> 0e75f2647b8e dmaengine: pl330: fix double lock
> 7d22b54b79f2 dmaengine: pl330: remove unused ‘regs’
> 8769d7115cec dmaengine: pl330: do not generate unaligned access
> 65ad077f685b dmaengine: pl330: convert callback to helper function
> 368e7aa6dffd dmaengine: add support to provide error result from a DMA
> transation
> 8f8afe84472f dmaengine: Add helper function to prep for error reporting
> 2acc1e704232 dmaengine: pl330: explicitly freeup irq
> ed36cde14cf0 (m/master, cros/chromeos-4.4) UPSTREAM: audit: add tty
> field to LOGIN event
> 
> Unfortunately when I start playing audio, things don't seem to work :(
> Rolling back HEAD to "dmaengine: pl330: fix double lock" works though.
> 
> The only thing I get from dmesg relevant to pl330 is this:
> [   59.203375] dma-pl330 ff6d0000.dma-controller:
> pl330_submit_req:1498 Try increasing mcbufsz (12810/256)
> [   59.203395] dma-pl330 ff6d0000.dma-controller: fill_queue:2023 Bad Desc(2)
> [   63.837390] dma-pl330 ff6d0000.dma-controller:
> pl330_submit_req:1498 Try increasing mcbufsz (12810/256)
> [   63.837410] dma-pl330 ff6d0000.dma-controller: fill_queue:2023 Bad Desc(2)
> 
> Thanks,
> Steve
> 


> 14 апр. 2017 г., в 21:04, Krzysztof Kozlowski <krzk@kernel.org> написал(а):
> 
> Let me know if you need more data. I wonder why you haven't experience
> this?

I don’t have idea why this might happen on Odroid and due to the fact the patch don’t
work for Stephen and I don’t have another idea how to implement that, it is better to
leave the problem along.

Krzysztof, thanks a lot for help. Really.

Regards,
Alexander.

      parent reply	other threads:[~2017-04-26 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 14:35 Alexander Kochetkov
2017-04-14 14:35 ` [PATCH 1/2] dmaengine: pl330: make cyclic transfer free runnable Alexander Kochetkov
2017-04-14 18:04   ` Krzysztof Kozlowski
2017-04-14 14:35 ` [PATCH 2/2] dmaengine: pl330: don't emit code for one iteration loop Alexander Kochetkov
2017-04-18  2:26 ` [PATCH 0/2] Free running cyclic transfer implementation for pl330 sugar
2017-04-26 17:01 ` Alexander Kochetkov [this message]

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=FFF03FEC-4C86-4E2E-BC45-1C8694243203@gmail.com \
    --to=al.kochet@gmail.com \
    --cc=caesar.wang@rock-chips.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=hhb@rock-chips.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=smbarber@chromium.org \
    --cc=sugar.zhang@rock-chips.com \
    --cc=ulysses.huang@rock-chips.com \
    --cc=vinod.koul@intel.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

all inboxes | Powered by JetHome®