linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoc: kirkwood: Extend the min and max number of bytes per period
Date: Thu, 26 Sep 2013 11:28:40 +0100	[thread overview]
Message-ID: <20130926102840.GP12758@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130926102408.GE19304@sirena.org.uk>

On Thu, Sep 26, 2013 at 11:24:08AM +0100, Mark Brown wrote:
> On Thu, Sep 19, 2013 at 11:20:43AM +0200, Jean-Francois Moine wrote:
> > This patch extends the min and max number of bytes per period.
> > It mainly permits to reduce the sound delay in MIDI real-time playing.
> 
> Applied, thanks.  For the minimum limit is there any hardware imposed
> limit that could be used rather than tweaking the numbers?

I looked at that, and apart from interrupt rate, I don't see any.

The values I have for these in my tree are:

#define KIRKWOOD_SND_MIN_PERIODS                2
#define KIRKWOOD_SND_MAX_PERIODS                16
#define KIRKWOOD_SND_MIN_PERIOD_BYTES           256
#define KIRKWOOD_SND_MAX_PERIOD_BYTES           0x100000
#define KIRKWOOD_SND_MAX_BUFFER_BYTES           0x100000

which are partly based on patches applied to Rabeeh's kernel, and then
further adjusted.  Yes, the max period bytes won't be reachable since
the minimum period will cause it to be half the max buffer bytes.

  reply	other threads:[~2013-09-26 10:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19  9:20 [PATCH] ASoc: kirkwood: Extend the min and max number of bytes per period Jean-Francois Moine
2013-09-26 10:24 ` Mark Brown
2013-09-26 10:28   ` Russell King - ARM Linux [this message]
2013-09-27 14:42     ` Mark Brown

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=20130926102840.GP12758@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).