From: Stephen Warren <swarren@wwwdotorg.org>
To: Dylan Reid <dgreid@chromium.org>, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>, Stephen Warren <swarren@nvidia.com>
Subject: Re: Using HDA on an SoC without PCI
Date: Fri, 14 Feb 2014 11:01:14 -0700 [thread overview]
Message-ID: <52FE59EA.2030808@wwwdotorg.org> (raw)
In-Reply-To: <CAEUnVG525yyj_X9c5ND6jdHA+N8YXPkfhB9=vAG_RuRPtZUKbA@mail.gmail.com>
On 02/14/2014 10:47 AM, Dylan Reid wrote:
> Hi,
>
> I'm working on an system with an HDMI codec on an HDA interface, but
> that interface doesn't use PCI. I want to re-use as much of the code
> as possible, but I want to avoid scattering ifdefs all over
> hda_intel.c.
I think the relevant APIs stub themselves out when appropriate, so you
can do this all without compile-time ifdefs.
> Would gathering the pci specific functions from hda_intel.c into an
> interface struct of some kind make sense? If azx was probed from pci,
> then a pci interface would be used, if it was a platform driver, then
> the correct interface for the platform would be used. It would add
> some overhead to operations such as azx_writel, but that would be
> measured to make sure it isn't detrimental to performance.
Our downstream trees do have patches to allow the HDA driver to be
instantiated from either PCI or from platform devices. You can find the
code in branch:
git://nv-tegra.nvidia.com/linux-2.6.git rel-roth-r3
e.g. ef8491346266 "ALSA: hda: Add hda platform driver support"
There are many other patches to sound/pci/hda after that. I don't recall
exactly how clean taht first patch was, and probably never saw anything
after it, but it might be a good start...
We've only recently had HDMI support upstream on Tegra, otherwise it's
possible I may have found time to try to upstream those patches before.
Not that I have spare time:-)
next prev parent reply other threads:[~2014-02-14 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 17:47 Using HDA on an SoC without PCI Dylan Reid
2014-02-14 18:01 ` Stephen Warren [this message]
2014-02-14 18:50 ` Dylan Reid
2014-02-14 20:13 ` Takashi Iwai
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=52FE59EA.2030808@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alsa-devel@alsa-project.org \
--cc=dgreid@chromium.org \
--cc=swarren@nvidia.com \
--cc=tiwai@suse.de \
/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.