From: Daniel Mack <daniel@zonque.org>
To: Matthew Bucknall <matthew.bucknall@gmail.com>,
alsa-devel@alsa-project.org
Subject: Re: Non-I2C/SPI ASoC codec
Date: Thu, 03 Jul 2014 13:28:05 +0200 [thread overview]
Message-ID: <53B53E45.9070402@zonque.org> (raw)
In-Reply-To: <CAOr_jfL+fMBVi82RaLBAcnygNFhVXPoRoyFMGTp4HOEZecSyMA@mail.gmail.com>
On 07/03/2014 01:14 PM, Matthew Bucknall wrote:
> I'm trying to get audio support for a custom ARM board to work and have
> written codec and machine drivers - The platform driver already existed
> (atmel_ssc_dai). The codec I am supporting is extremely simple and has no
> SPI/I2C interface for configuration and just accepts fixed format/fixed
> rate I2S.
>
> Previously, when I've gotten ASoC support for another board working, the
> codec it used (TLV320AIC32) had an I2C interface. Declaring I2C_BOARD_INFO
> for this in my board file seemed sufficient to get the machine driver to
> probe and initialize. For this new board, I have no SPI/I2C device to
> declare in the board file and its associated machine driver is not probing.
> All I get from the kernel is 'No soundcards found.'
>
> My driver modules are getting compiled and are linked statically. What do I
> need to do to get the machine driver going?
You need to
a) get the driver compiled into your kernel (statically or as module),
and
b) instantiate the driver, from either DTB or a platform_device struct.
There are plenty of good examples in the mainline kernel for both ways,
but note that board-file driven (non-DTB) boards are considered legacy.
FWIW, A very simple ASoC codec that doesn't have any control bus such as
I2C/SPI is already present in sound/soc/codecs/ak5386.c.
Daniel
prev parent reply other threads:[~2014-07-03 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 11:14 Non-I2C/SPI ASoC codec Matthew Bucknall
2014-07-03 11:28 ` Daniel Mack [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=53B53E45.9070402@zonque.org \
--to=daniel@zonque.org \
--cc=alsa-devel@alsa-project.org \
--cc=matthew.bucknall@gmail.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.