From: Michael Jordan <jordan.mymail@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Request for information
Date: Fri, 6 Sep 2013 22:18:36 -0400 [thread overview]
Message-ID: <20130906221836.50bae68e@mach1> (raw)
Hello,
I am developing a driver for the PCM3168A. We have created an expansion
board with the codec, op-amp buffers, etc. which is designed to connect
to the audio expansion connector on an OMAPL138 EXPKIT from LogicPD. I
have the rough draft of the pcm3168a.c and pcm3168a.h. Looking through
the code, I see that the DA850 is "hard-wired" in the code to expect
the TLV320AIC3106, which is the on-board codec on the kit.
My question is, would it be proper for me to create entries in
davinci-evm.c, mach-types.h, etc. in order to provide a way to register
this new driver? Or is there a different way I should proceed?
I'll be modifying my code base for testing purposes, but when it comes
time for submission, I would like to know the proper way to handle this.
Thank you,
Michael
reply other threads:[~2013-09-07 2:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130906221836.50bae68e@mach1 \
--to=jordan.mymail@gmail.com \
--cc=alsa-devel@alsa-project.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).