alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Michael Jordan <jordan.mymail@gmail.com>
To: "Hebbar, Gururaja" <gururaja.hebbar@ti.com>, alsa-devel@alsa-project.org
Subject: Hello
Date: Wed, 11 Sep 2013 23:12:24 -0400	[thread overview]
Message-ID: <20130911231224.2d52a2e3@mach1> (raw)

Hello Gururaja,

If I am trying to ask some questions about the alsa system, do I need
to copy somebody directly to get a response? I have posted about 4
questions on the group in the last few months, and I have not even
gotten a slap on the hand.

The reason I am contacting you is you have mentioned working on the
TLV320AIC3X which is the chip used on the OMAPL138 board that we have.
I am attempting to write a driver for a PCM3168A which we have already
constructed a board for, and plugs into the 100 pin audio expander
connecter. I have the basic draft of a driver, but everything in the
code seems to be fairly strongly coded for the DA850 boards to use the
TLV320AIC. I can prevent it loading, and my module will load, but
things are not "connecting" internally. I assumed that I would need to
make some changes in the arch/arm/mach-davinci/board-da850-evm.c.

However what I am running into is chasing me up a trail that eventually
has me modifying mach-types.h and creating a whole new board
configuration. I said ok, so I copied board-da850-evm.c to
board-da850-evm-mod.c which made it necessary for me to begin modifying
some Kconfig's, etc., and I still cannot get the kernel to compile with
the new kernel driver.

I just need to know, am I heading down the wrong path with this? I have
a pcm3168a.c and pcm3168a.h which have a basic structure for the new
codec, but I cannot figure out how to get the system to actually use it
because it basically appears that the TLV320AIC3X is "hard-wired" into
the system.

Help please,

Michael

             reply	other threads:[~2013-09-12  3:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12  3:12 Michael Jordan [this message]
2013-09-12 17:33 ` Hello Daniel Mack
  -- strict thread matches above, loose matches on Subject: below --
2013-08-11 19:37 Hello Michael Jordan
2012-11-21 15:56 Hello l9jj
2007-01-06 15:13 HELLO Rudolph Moseley

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=20130911231224.2d52a2e3@mach1 \
    --to=jordan.mymail@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=gururaja.hebbar@ti.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;
as well as URLs for NNTP newsgroup(s).