From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: bcousson@baylibre.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: DTS: am335x-evmsk: Enable the McASP FIFO for audio
Date: Mon, 7 Jul 2014 04:35:16 -0700 [thread overview]
Message-ID: <20140707113516.GR28884@atomide.com> (raw)
In-Reply-To: <1404381083-27029-2-git-send-email-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [140703 02:53]:
> The use of FIFO in McASP can reduce the risk of audio under/overrun and
> lowers the load on the memories since the DMA will operate in bursts.
Applying both into omap-for-v3.16/fixes thanks.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: DTS: am335x-evmsk: Enable the McASP FIFO for audio
Date: Mon, 7 Jul 2014 04:35:16 -0700 [thread overview]
Message-ID: <20140707113516.GR28884@atomide.com> (raw)
In-Reply-To: <1404381083-27029-2-git-send-email-peter.ujfalusi@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti.com> [140703 02:53]:
> The use of FIFO in McASP can reduce the risk of audio under/overrun and
> lowers the load on the memories since the DMA will operate in bursts.
Applying both into omap-for-v3.16/fixes thanks.
Tony
next prev parent reply other threads:[~2014-07-07 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 9:51 [PATCH 1/2] ARM: DTS: am335x-evm: Enable the McASP FIFO for audio Peter Ujfalusi
2014-07-03 9:51 ` Peter Ujfalusi
2014-07-03 9:51 ` [PATCH 2/2] ARM: DTS: am335x-evmsk: " Peter Ujfalusi
2014-07-03 9:51 ` Peter Ujfalusi
2014-07-07 11:35 ` Tony Lindgren [this message]
2014-07-07 11:35 ` Tony Lindgren
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=20140707113516.GR28884@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.