From: Vinod Koul <vinod.koul@intel.com>
To: David Henningsson <david.henningsson@canonical.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Ramesh <ramesh.babu@intel.com>
Subject: Re: Out-of-tree HDMI audio driver for BayTrail-T
Date: Thu, 27 Aug 2015 19:01:05 +0530 [thread overview]
Message-ID: <20150827133105.GV13546@localhost> (raw)
In-Reply-To: <55DEA7D8.5060106@canonical.com>
On Thu, Aug 27, 2015 at 08:02:00AM +0200, David Henningsson wrote:
> I don't usually deal with out-of-tree drivers, but when Canonical
> enabled the Intel Compute Stick [1] (which is using a BayTrail-T
> processor), we were using an out-of-tree driver to enable HDMI
> audio.
>
> The driver has earlier been made public by Intel [2], and I've put
> my modifications to it here [3].
>
> Unfortunately, it looks like the effort and hardware knowledge
> required to make this driver upstreamable is beyond what I can
> currently manage.
>
> Also, I cannot answer for whether or not other parties (such as
> Intel) plan to upstream the driver.
Hi David,
Thanks for bringing this up. My team (Ramesh) wrote the driver so we can
answer the questions around it
The only reason we didn't upstream the driver was the display interface it
relied on. To configure HDMI the driver needs to access display registers
which are exposed by display using a private interface. If that or something
else is available for us to configure HDMI upstream, We can push this
upstream.
--
~Vinod
prev parent reply other threads:[~2015-08-27 13:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 6:02 Out-of-tree HDMI audio driver for BayTrail-T David Henningsson
2015-08-27 13:31 ` Vinod Koul [this message]
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=20150827133105.GV13546@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=ramesh.babu@intel.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.