[meta-intel] [PATCH 1/1] chiefriver: provide ALSA device configuration for NUC

[Tom Zanussi]

On Wed, 2012-12-05 at 11:12 -0600, Kamble, Nitin A wrote:
> 
> > -----Original Message-----
> > From: Zanussi, Tom
> > Sent: Wednesday, December 05, 2012 9:01 AM
> > To: Kamble, Nitin A
> > Cc: meta-intel at yoctoproject.org; Hart, Darren
> > Subject: Re: [PATCH 1/1] chiefriver: provide ALSA device configuration for
> > NUC
> > 
> > On Wed, 2012-12-05 at 10:53 -0600, Kamble, Nitin A wrote:
> > > > -----Original Message-----
> > > > From: Zanussi, Tom
> > > > Sent: Wednesday, December 05, 2012 6:33 AM
> > > > To: Kamble, Nitin A
> > > > Cc: meta-intel at yoctoproject.org; Hart, Darren
> > > > Subject: Re: [PATCH 1/1] chiefriver: provide ALSA device
> > > > configuration for NUC
> > > >
> > > > On Tue, 2012-12-04 at 21:28 -0800, nitin.a.kamble at intel.com wrote:
> > > > > From: Nitin A Kamble <nitin.a.kamble at intel.com>
> > > > >
> > > > > The NUC routes audio through HDMI. The default ALSA config is
> > > > > failing to provide working sound. And this configuration file
> > > > > configures ALSA system to use HDMI-0 port for audio out.
> > > > >
> > > >
> > > > Hmm, this only applies to the NUC, right?  Maybe we should create a
> > > > new BSP for the NUC (I think there are other NUC-specific things
> > > > coming up too e.g. wireless)?
> > > >
> > > > Tom
> > >
> > >
> > > Tom,
> > >   As our chiefriver system is kind of broken, shall we make NUC as the
> > target for the chiefriver BSP now?
> > >
> Tom,
>    In that case we can either create 2 BSPs, or make chiefriver BSP workable for both. The alsa config patch will be harmless for our chiefriver h/w as it does not has sound support.

Our current chiefriver hardware doesn't have sound because it's an old
engineering sample, but I assume the new hardware we'll be getting won't
have that problem, which means we'll need two different alsa configs.

>    If there are more changes coming for NUC which cause trouble on the previous chiefriver h/w then we will be better with a new NUC BSP. Looking at the history of BSPs in the repo we have chosen to create separate BSPs in such situations. And that will be easier option to implement too.
>   Any thoughts?
> 

If there's a clean way to support everything for both from within the
same BSP, then that may be the way to go, but if we find we have to add
conditionals all over the place or otherwise contort the current BSP to
accommodate both, then I'd go with a separate BSP.

The other aspect of this is usability - from a user's perspective it's
nicer to be able to point to meta-nuc that cleanly encapsulates the NUC
bsp with nothing else cluttering things up.

Of course, you have to balance that with maintenance costs for two
separate BSPs, etc, but IMHO BSP layers are meant to be lightweight
constructs designed for that kind of thing...

Tom


> Thanks,
> Nitin
> 
> > 
> > Well, Song is still working on getting a replacement chiefriver CRB, so I think
> > the chiefriver will still be used for that.
> > 
> > Tom
> > 
> > > Thanks,
> > > Nitin
> > >
> > >
> > > >
> > > > > Signed-off-by: Nitin A Kamble <nitin.a.kamble at intel.com>
> > > > > ---
> > > > >  .../recipes-bsp/alsa-state/alsa-state.bbappend     |    1 +
> > > > >  .../alsa-state/alsa-state/chiefriver/asound.conf   |   24
> > > > ++++++++++++++++++++
> > > > >  2 files changed, 25 insertions(+), 0 deletions(-)  create mode
> > > > > 100644 meta-chiefriver/recipes-bsp/alsa-state/alsa-state.bbappend
> > > > >  create mode 100644
> > > > > meta-chiefriver/recipes-bsp/alsa-state/alsa-state/chiefriver/asoun
> > > > > d.co
> > > > > nf
> > > > >
> > > > > diff --git
> > > > > a/meta-chiefriver/recipes-bsp/alsa-state/alsa-state.bbappend
> > > > > b/meta-chiefriver/recipes-bsp/alsa-state/alsa-state.bbappend
> > > > > new file mode 100644
> > > > > index 0000000..72d991c
> > > > > --- /dev/null
> > > > > +++ b/meta-chiefriver/recipes-bsp/alsa-state/alsa-state.bbappend
> > > > > @@ -0,0 +1 @@
> > > > > +FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> > > > > diff --git
> > > > > a/meta-chiefriver/recipes-bsp/alsa-state/alsa-state/chiefriver/asound.
> > > > > conf
> > > > > b/meta-chiefriver/recipes-bsp/alsa-state/alsa-state/chiefriver/asound.
> > > > > conf
> > > > > new file mode 100644
> > > > > index 0000000..3847a50
> > > > > --- /dev/null
> > > > > +++ b/meta-chiefriver/recipes-bsp/alsa-state/alsa-state/chiefriver
> > > > > +++ /aso
> > > > > +++ und.conf
> > > > > @@ -0,0 +1,24 @@
> > > > > +pcm.!default {
> > > > > +    type plug
> > > > > +    slave.pcm "dmixer"
> > > > > +}
> > > > > +
> > > > > +pcm.dmixer {
> > > > > +    type dmix
> > > > > +    ipc_key 1024
> > > > > +    ipc_key_add_uid 0
> > > > > +    ipc_perm 0666
> > > > > +    slave {
> > > > > +        pcm "hw:0,3"    # HDMI CARD AND DEVICE
> > > > > +        period_time 0
> > > > > +        period_size 1024
> > > > > +        buffer_size 8192
> > > > > +        rate 48000 #or 44100
> > > > > +    }
> > > > > +}
> > > > > +
> > > > > +ctl.dmixer {
> > > > > +    type hw
> > > > > +    card 0
> > > > > +}
> > > > > +
> > > >
> > >
> > 
>