All of lore.kernel.org
 help / color / mirror / Atom feed
* Add ALSA driver to Buildroot image or add / load it after booting the image
@ 2013-03-10 20:19 Marc Schultz
  2013-03-11  0:20 ` Gabriel M. Beddingfield
  0 siblings, 1 reply; 2+ messages in thread
From: Marc Schultz @ 2013-03-10 20:19 UTC (permalink / raw)
  To: alsa-devel

Hey ALSA-Devel community,

I'm successfully booting a Buildroot made Linux image on my board.
This board has an Cirrus Logic CS4270 sound chip and now I want to
activate the specific sound card driver for it. Is there a good way to
put the CS4270 driver files into the Linux Kernel folders of Buildroot
to get them compressed into the Linux image or do I have to go one of
the following ways after booting the image on my target hardware?

http://www.alsa-project.org/main/index.php/Matrix:Module-cs4270

http://www.alsa-project.org/main/index.php/Driver_Compilation)

Do you have a good workflow for me to get this thing working?

Best regards,
Marc Schultz

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Add ALSA driver to Buildroot image or add / load it after booting the image
  2013-03-10 20:19 Add ALSA driver to Buildroot image or add / load it after booting the image Marc Schultz
@ 2013-03-11  0:20 ` Gabriel M. Beddingfield
  0 siblings, 0 replies; 2+ messages in thread
From: Gabriel M. Beddingfield @ 2013-03-11  0:20 UTC (permalink / raw)
  To: alsa-devel


Hi Marc,

On 03/10/2013 01:19 PM, Marc Schultz wrote:
> Hey ALSA-Devel community,
>
> I'm successfully booting a Buildroot made Linux image on my board.
> This board has an Cirrus Logic CS4270 sound chip and now I want to
> activate the specific sound card driver for it. Is there a good way to
> put the CS4270 driver files into the Linux Kernel folders of Buildroot
> to get them compressed into the Linux image or do I have to go one of
> the following ways after booting the image on my target hardware?
>
> http://www.alsa-project.org/main/index.php/Matrix:Module-cs4270
>
> http://www.alsa-project.org/main/index.php/Driver_Compilation)
>
> Do you have a good workflow for me to get this thing working?

Long story short... making this work is /very/ board-specific.  If 
someone hasn't already done the work for your specific board -- doing 
the work isn't trivial.  It's not like PC's where the sound card is on 
the PCI bus and you simply have to load the driver module.  Someone 
experienced in ASoC and board bring-up would spend anywhere from 2 days 
to a week to do this board-specific integration work.

If you're starting from less, then the lower estimate is "weeks."

So, if you're up for the journey... here's some starting points...

Start here:  Documentation/sound/alsa/soc/*

One example of this kind of integration can be found for the BeagleBoard:

         arch/arm/mach-omap2/board-omap3beagle.c (board file)
         sound/soc/omap/omap-twl4030.c (ASoC machine driver)

Each component will need board-specific platform data added to the board 
file (or device tree), and a machine driver will be needed to glue 
together the audio components (CPU platform + CPU Driver + Audio Codec) 
into a "sound card".

-gabriel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-03-11  0:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-10 20:19 Add ALSA driver to Buildroot image or add / load it after booting the image Marc Schultz
2013-03-11  0:20 ` Gabriel M. Beddingfield

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.