From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, broonie@kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: [alsa-devel] [PATCH 0/2] ASoC: SOF: make hw_info platform specific
Date: Tue, 22 Oct 2019 14:39:53 -0500 [thread overview]
Message-ID: <20191022193955.21766-1-pierre-louis.bossart@linux.intel.com> (raw)
The SOF core blindly sets the hw_info, when it should really be
platform-specific.
This move enable us to temporarily fix PulseAudio issues resulting
from inaccuracies in the hw_ptr position provided by the firmware on
Baytrail-Broadwell.
This is the first time we experiment with the GitHub low-level API to
automagically keep track of 'approvers' by inserting a Reviewed-by tag
when merging a pull-request, thanks to Ranjani for her initial work
and bearing with my habit of breaking things :-)
Pierre-Louis Bossart (2):
ASoC: SOF: define INFO_ flags in dsp_ops
ASoC: SOF: Intel: only support INFO_BATCH for legacy platforms
sound/soc/sof/imx/imx8.c | 7 +++++++
sound/soc/sof/intel/apl.c | 7 +++++++
sound/soc/sof/intel/bdw.c | 9 ++++++++-
sound/soc/sof/intel/byt.c | 21 +++++++++++++++++++++
sound/soc/sof/intel/cnl.c | 7 +++++++
sound/soc/sof/pcm.c | 8 +++-----
sound/soc/sof/sof-priv.h | 3 +++
7 files changed, 56 insertions(+), 6 deletions(-)
--
2.20.1
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2019-10-22 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 19:39 Pierre-Louis Bossart [this message]
2019-10-22 19:39 ` [alsa-devel] [PATCH 1/2] ASoC: SOF: define INFO_ flags in dsp_ops Pierre-Louis Bossart
2019-10-24 11:49 ` Mark Brown
2019-10-22 19:39 ` [alsa-devel] [PATCH 2/2] ASoC: SOF: Intel: only support INFO_BATCH for legacy platforms Pierre-Louis Bossart
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=20191022193955.21766-1-pierre-louis.bossart@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=tiwai@suse.de \
/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.