From: Jyri Sarha <jsarha@ti.com>
To: alsa-devel@alsa-project.org, linux-fbdev@vger.kernel.org,
linux-omap@vger.kernel.org
Cc: peter.ujfalusi@ti.com, liam.r.girdwood@linux.intel.com,
tomi.valkeinen@ti.com, broonie@kernel.org,
Jyri Sarha <jsarha@ti.com>
Subject: [PATCH 0/2] OMAPDSS: Couple of HDMI audio fixes
Date: Wed, 26 Aug 2015 16:11:38 +0300 [thread overview]
Message-ID: <cover.1440594174.git.jsarha@ti.com> (raw)
The first fix is a hairy one, but I think the locking is fool proof
now. It is needed because there is no telling in which order user
space starts an audio and video stream playback. If the audio is
started first and the video mode is changed when video playback starts
the audio setup needs to survive display turning off and back on
again. After this patch the audio streams should survive a
suspend-resume cycle too.
The second one is a trivial work-around to a problem in ALSA constraint
resolver code.
The two fixes are totally independent and the video and audio side
patches applied separately trough their own trees.
Jyri Sarha (2):
OMAPDSS: hdmi: Reconfigure and restart audio when display is enabled
ASoC: omap-hdmi-audio: Set buffer bytes step constraint to 128
drivers/video/fbdev/omap2/dss/hdmi.h | 10 +++-
drivers/video/fbdev/omap2/dss/hdmi4.c | 65 ++++++++++++++++++++-----
drivers/video/fbdev/omap2/dss/hdmi5.c | 89 +++++++++++++++++++++++++++++------
sound/soc/omap/omap-hdmi-audio.c | 10 +++-
4 files changed, 146 insertions(+), 28 deletions(-)
--
1.9.1
next reply other threads:[~2015-08-26 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 13:11 Jyri Sarha [this message]
2015-08-26 13:11 ` [PATCH 1/2] OMAPDSS: hdmi: Reconfigure and restart audio when display is enabled Jyri Sarha
2015-08-27 14:30 ` Tomi Valkeinen
2015-08-28 10:37 ` Tomi Valkeinen
2015-08-28 11:35 ` Jyri Sarha
2015-08-26 13:11 ` [PATCH 2/2] ASoC: omap-hdmi-audio: Set buffer bytes step constraint to 128 Jyri Sarha
2015-08-26 17:42 ` [PATCH 0/2] OMAPDSS: Couple of HDMI audio fixes 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=cover.1440594174.git.jsarha@ti.com \
--to=jsarha@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=tomi.valkeinen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox