From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: broonie@kernel.org, lgirdwood@gmail.com
Cc: alsa-devel@alsa-project.org, misael.lopez@ti.com, tiwai@suse.com,
jsarha@ti.com
Subject: [alsa-devel] [PATCH 0/2] ASoC: ti: davinci-mcasp: sample format constraint fixes
Date: Fri, 26 Jul 2019 09:42:42 +0300 [thread overview]
Message-ID: <20190726064244.3762-1-peter.ujfalusi@ti.com> (raw)
Hi,
The two patch fixes two issues on how the driver have placed constraints on the
format size.
1. When the first stream starts and the TDM slot_width is configured we can
allow formats which require less or equal number of bits on the bus.
2. For the second stream we must allow only formats which uses exact number of
bits on the bus.
These issues are visible around the S24_3LE, S24_LE and S32_LE formats.
Regards,
Peter
---
Peter Ujfalusi (2):
ASoC: ti: davinci-mcasp: Correct slot_width posed constraint
ASoC: ti: davinci-mcasp: Support for correct symmetric sample bits
sound/soc/ti/davinci-mcasp.c | 91 +++++++++++++++++++++++++++++++-----
1 file changed, 79 insertions(+), 12 deletions(-)
--
Peter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2019-07-26 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 6:42 Peter Ujfalusi [this message]
2019-07-26 6:42 ` [PATCH 1/2] ASoC: ti: davinci-mcasp: Correct slot_width posed constraint Peter Ujfalusi
2019-07-26 12:12 ` Applied "ASoC: ti: davinci-mcasp: Correct slot_width posed constraint" to the asoc tree Mark Brown
2019-07-26 6:42 ` [PATCH 2/2] ASoC: ti: davinci-mcasp: Support for correct symmetric sample bits Peter Ujfalusi
2019-07-26 12:12 ` Applied "ASoC: ti: davinci-mcasp: Support for correct symmetric sample bits" to the asoc tree 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=20190726064244.3762-1-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jsarha@ti.com \
--cc=lgirdwood@gmail.com \
--cc=misael.lopez@ti.com \
--cc=tiwai@suse.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.