linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] 86xx: Enable the AC97 interface on 8641D board.
Date: Thu, 03 May 2007 10:55:25 -0500	[thread overview]
Message-ID: <1178207725.17201.33.camel@ld0161-tx32> (raw)
In-Reply-To: <08D3A1CE-12E0-4759-B055-DE227EA4135E@kernel.crashing.org>

On Thu, 2007-05-03 at 09:44, Kumar Gala wrote:
> On May 2, 2007, at 4:53 PM, Jon Loeliger wrote:
> 
> > From: Jason Jin <jason.jin@freescale.com>
> >
> > HD interface and AC97 interface share some pins and they are  
> > enabled at
> > the same time, In order to use AC97 interface, we need to disable  
> > the HD
> > interface first.
> >
> > Signed-off-by:Jason Jin<jason.jin@freescale.com>
> > Acked-by: Jon Loeliger <jdl@freescale.com>
> > ---
> >  arch/powerpc/platforms/86xx/mpc86xx_hpcn.c |    7 ++++++-
> >  1 files changed, 6 insertions(+), 1 deletions(-)
> 
> Is the HD feature not used at all?  Is there a AC97 Driver CONFIG_  
> that makes sense to wrap that with?  Just wondering about the mutual  
> exclusion (and how to provide flexibility to the user).
> 
> - k


The ULI supports both the HD and AC97 interfaces, but the 8641
only supports the AC97 interface.  Thus we can straight disable
the HD and convert/configure the shared pins to be AC97.  Thus,
there is no real CONFIG_ need at all.  It's only AC97.  And then
ultimately, the presence of sound support is controlled by
the ALSA config options as per normal.

Thanks,
jdl

  reply	other threads:[~2007-05-03 15:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 21:53 [PATCH] 86xx: Enable the AC97 interface on 8641D board Jon Loeliger
2007-05-03 14:44 ` Kumar Gala
2007-05-03 15:55   ` Jon Loeliger [this message]
2007-05-03 16:01     ` Kumar Gala
2007-05-03 16:03       ` Jon Loeliger
2007-05-03 16:10     ` Olof Johansson
2007-05-03 16:17       ` Jon Loeliger
2007-05-03 16:19         ` Kumar Gala
2007-05-03 17:28           ` Olof Johansson
2007-05-09 16:14           ` Jon Loeliger
2007-05-09 16:19             ` Kumar Gala
2007-05-03 17:26         ` Olof Johansson
2007-05-03 17:38           ` Scott Wood
2007-05-06 22:42         ` Matt Sealey
2007-05-10  5:16 ` Kumar Gala
2007-05-10 15:45   ` Jon Loeliger

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=1178207725.17201.33.camel@ld0161-tx32 \
    --to=jdl@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).