From: Sameer Pujar <spujar@nvidia.com>
To: "Sheetal ." <sheetal@nvidia.com>,
perex@perex.cz, tiwai@suse.com, broonie@kernel.org,
linux-sound@vger.kernel.org
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
lgirdwood@gmail.com, jonathanh@nvidia.com,
thierry.reding@gmail.com, mkumard@nvidia.com,
Ritu Chaudhary <rituc@nvidia.com>
Subject: Re: [PATCH] ASoC: tegra: Add support for S24_LE audio format
Date: Tue, 22 Oct 2024 11:01:09 +0530 [thread overview]
Message-ID: <be5a4452-5042-4785-8ac1-6f5cae7fe871@nvidia.com> (raw)
In-Reply-To: <20241022041330.3421765-1-sheetal@nvidia.com>
On 22-10-2024 09:43, Sheetal . wrote:
> From: Ritu Chaudhary <rituc@nvidia.com>
>
> Add support for S24_LE format for all internal and IO AHUB
> modules, except for ASRC (which is already supported).
>
> The data flow happens as mentioned below:
>
> - ADMAIF picks 24-bit valid data and converts it to 32-bit before
> sending to internal AHUB modules. This makes the driver change
> simpler for internal AHUB modules.
> - IO modules CIF converts the 32-bit data to 24-bit before sending it
> to the external world.
> - To maintain consistency across modules, conversions between 24-bit
> and 32-bit occur either at ADMAIF or at the IO modules CIF.
>
> This feature has been thoroughly tested and verified with all internal
> AHUB modules on the Jetson AGX Orin Platform, as well as with the
> external RT5640 codec.
>
> Signed-off-by: Ritu Chaudhary <rituc@nvidia.com>
> Signed-off-by: Sheetal <sheetal@nvidia.com>
> ---
> sound/soc/tegra/tegra186_dspk.c | 3 +++
> sound/soc/tegra/tegra210_admaif.c | 11 +++++++++--
> sound/soc/tegra/tegra210_adx.c | 9 +++++++--
> sound/soc/tegra/tegra210_amx.c | 9 +++++++--
> sound/soc/tegra/tegra210_dmic.c | 7 +++++--
> sound/soc/tegra/tegra210_i2s.c | 14 ++++++++++++--
> sound/soc/tegra/tegra210_i2s.h | 9 +++++----
> sound/soc/tegra/tegra210_mixer.c | 9 +++++++--
> sound/soc/tegra/tegra210_mvc.c | 9 +++++++--
> sound/soc/tegra/tegra210_ope.c | 9 +++++++--
> sound/soc/tegra/tegra210_sfc.c | 9 +++++++--
> 11 files changed, 76 insertions(+), 22 deletions(-)
Reviewed-by: Sameer Pujar <spujar@nvidia.com>
next prev parent reply other threads:[~2024-10-22 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 4:13 Sheetal .
2024-10-22 5:31 ` Sameer Pujar [this message]
2024-10-22 19:37 ` 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=be5a4452-5042-4785-8ac1-6f5cae7fe871@nvidia.com \
--to=spujar@nvidia.com \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=rituc@nvidia.com \
--cc=sheetal@nvidia.com \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®