diff for duplicates of <552492E1.3050207@broadcom.com> diff --git a/a/1.txt b/N1/1.txt index 9853571..35ddb45 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -34,8 +34,8 @@ On 15-04-06 09:19 AM, Mark Brown wrote: The hardware updates a read pointer (rdaddr) which we feed to ALSA via the ".pointer" hook. So yes, the hardware does have a register that tells us its progress. This routine (ringbuf_inc) actually updates a -write pointer (wraddr) which is a misnomer. The write pointer doesn’t -actually tell us where we are writing to – ALSA keeps track of that. +write pointer (wraddr) which is a misnomer. The write pointer doesn?t +actually tell us where we are writing to ? ALSA keeps track of that. The wraddr only prevents the hardware from reading past it. We just use it, along with a low water mark configuration register, to keep the periodic interrupts firing. The hardware is tracking the distance diff --git a/a/content_digest b/N1/content_digest index 3921326..5754cdc 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,30 +3,10 @@ "ref\020150331064209.GD2869@sirena.org.uk\0" "ref\0551D8EB6.1050004@broadcom.com\0" "ref\020150406161939.GJ6023@sirena.org.uk\0" - "From\0Lori Hikichi <lhikichi@broadcom.com>\0" - "Subject\0Re: [PATCH 2/2] ASoC: add core audio driver for Broadcom Cygnus SOC.\0" + "From\0lhikichi@broadcom.com (Lori Hikichi)\0" + "Subject\0[PATCH 2/2] ASoC: add core audio driver for Broadcom Cygnus SOC.\0" "Date\0Tue, 7 Apr 2015 19:30:57 -0700\0" - "To\0Mark Brown <broonie@kernel.org>\0" - "Cc\0Scott Branden <sbranden@broadcom.com>" - Rob Herring <robh+dt@kernel.org> - Pawel Moll <pawel.moll@arm.com> - Mark Rutland <mark.rutland@arm.com> - Ian Campbell <ijc+devicetree@hellion.org.uk> - Kumar Gala <galak@codeaurora.org> - Liam Girdwood <lgirdwood@gmail.com> - Jaroslav Kysela <perex@perex.cz> - Takashi Iwai <tiwai@suse.de> - alsa-devel@alsa-project.org - linux-kernel@vger.kernel.org - devicetree@vger.kernel.org - linux-arm-kernel@lists.infradead.org - bcm-kernel-feedback-list@broadcom.com - Dmitry Torokhov <dtor@google.com> - Anatol Pomazao <anatol@google.com> - abrestic@google.com - bryeung@google.com - olofj@google.com - " pwestin@google.com\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "\n" @@ -65,8 +45,8 @@ "The hardware updates a read pointer (rdaddr) which we feed to ALSA via \n" "the \".pointer\" hook. So yes, the hardware does have a register that \n" "tells us its progress. This routine (ringbuf_inc) actually updates a \n" - "write pointer (wraddr) which is a misnomer. The write pointer doesn\342\200\231t \n" - "actually tell us where we are writing to \342\200\223 ALSA keeps track of that. \n" + "write pointer (wraddr) which is a misnomer. The write pointer doesn?t \n" + "actually tell us where we are writing to ? ALSA keeps track of that. \n" "The wraddr only prevents the hardware from reading past it. We just use \n" "it, along with a low water mark configuration register, to keep the \n" "periodic interrupts firing. The hardware is tracking the distance \n" @@ -78,4 +58,4 @@ "period). Missing an interrupt is okay since the hardware will just stop \n" reading from the ring buffer when rdaddr has hit wraddr. -a1ac34ba6e4aec26304eade926eb531a38237534846a18bad9fc336338334acf +d309fb5fdef058bddd222ab34329b9c42151b15ab86c828b469244e40b82f728
diff --git a/a/content_digest b/N2/content_digest index 3921326..41c79b9 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -16,17 +16,17 @@ Liam Girdwood <lgirdwood@gmail.com> Jaroslav Kysela <perex@perex.cz> Takashi Iwai <tiwai@suse.de> - alsa-devel@alsa-project.org - linux-kernel@vger.kernel.org - devicetree@vger.kernel.org - linux-arm-kernel@lists.infradead.org - bcm-kernel-feedback-list@broadcom.com + <alsa-devel@alsa-project.org> + <linux-kernel@vger.kernel.org> + <devicetree@vger.kernel.org> + <linux-arm-kernel@lists.infradead.org> + <bcm-kernel-feedback-list@broadcom.com> Dmitry Torokhov <dtor@google.com> Anatol Pomazao <anatol@google.com> - abrestic@google.com - bryeung@google.com - olofj@google.com - " pwestin@google.com\0" + <abrestic@google.com> + <bryeung@google.com> + <olofj@google.com> + " <pwestin@google.com>\0" "\00:1\0" "b\0" "\n" @@ -78,4 +78,4 @@ "period). Missing an interrupt is okay since the hardware will just stop \n" reading from the ring buffer when rdaddr has hit wraddr. -a1ac34ba6e4aec26304eade926eb531a38237534846a18bad9fc336338334acf +7801e2d2ec4af427e449e2c58f86357d279aa9335d6bf9f2634493180922d996
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.