From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, Sameer Pujar <spujar@nvidia.com>,
dri-devel@lists.freedesktop.org,
Jon Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH] drm/tegra: sor: Support for audio over HDMI
Date: Tue, 4 Dec 2018 14:09:07 +0300 [thread overview]
Message-ID: <e78a378e-edc3-2d29-e0d7-f2a3b7fe3fd3@gmail.com> (raw)
In-Reply-To: <20181203153642.13562-1-thierry.reding@gmail.com>
On 03.12.2018 18:36, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> This code is very similar to the audio over HDMI support on older chips.
> Interoperation with the audio codec is done via a pair of codec scratch
> registers and an interrupt that is raised at the SOR when the codec has
> written those registers.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
Do you have any plans to implement integration with the sound subsystem? Indeed, there is HDMI audio configuration code for older chips in the Tegra's DRM driver that was added years ago.. but IIUC it's a kinda "dead code" without the integration.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-12-04 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 15:36 [PATCH] drm/tegra: sor: Support for audio over HDMI Thierry Reding
2018-12-03 16:05 ` Jani Nikula
2018-12-04 8:42 ` Thierry Reding
2018-12-04 9:33 ` Jani Nikula
2018-12-04 10:09 ` Thierry Reding
2018-12-04 11:09 ` Dmitry Osipenko [this message]
2018-12-04 13:08 ` Thierry Reding
2018-12-04 13:50 ` Dmitry Osipenko
2018-12-04 14:40 ` Thierry Reding
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=e78a378e-edc3-2d29-e0d7-f2a3b7fe3fd3@gmail.com \
--to=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=spujar@nvidia.com \
--cc=thierry.reding@gmail.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