All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Caleb Crome <caleb@crome.org>
Cc: Takashi Iwai <tiwai@suse.de>, "Lu, Han" <han.lu@intel.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Gautier, Bernard" <bernard.gautier@intel.com>
Subject: Re: BAT: why MAX_NUMBER_OF_CHANNELS and CHANNEL_MAX separate?
Date: Tue, 20 Oct 2015 16:41:13 +0100	[thread overview]
Message-ID: <1445355673.7033.51.camel@loki> (raw)
In-Reply-To: <CAG5mAdz0XcEwqJtCKps+=WBtu5A6SnkCkL889RpXHWhLvF4OjA@mail.gmail.com>

On Tue, 2015-10-20 at 08:36 -0700, Caleb Crome wrote:
> Hi,
>    I'm starting to bring up BAT on my board to see if it's going to work for me.
> 
> I'm starting from https://github.com/hanlui/bat, is that the correct
> place to start from?

I think that's Han's old git repo. He has a dev branch here :-

https://github.com/01org/bat

and bat support is now also in alsa-utils git too.

> 
> I'm bringing up a 16 channel board, so need BAT to support more
> channels (currently it supports only 2).
> 
> bat/include/common.h has the following defines:
> 
> #define MAX_NUMBER_OF_CHANNELS          2
> #define CHANNEL_MAX                     2
> #define CHANNEL_MIN                     1
> 
> Is there any reason we need both MAX_NUMBER_OF_CHANNELS and
> CHANNEL_MAX?  They sure seem like they can be merged to me.
> 

Yeah, this looks like it's duplicated to me. Han ?

> Once I get the program up and running, I'll add the ramp test, and
> start thinking about the other tests we talked about.
> 

Ok, thanks !

Liam

> Thanks,
>  -Caleb

  reply	other threads:[~2015-10-20 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 15:36 BAT: why MAX_NUMBER_OF_CHANNELS and CHANNEL_MAX separate? Caleb Crome
2015-10-20 15:41 ` Liam Girdwood [this message]
2015-10-20 15:48   ` Takashi Iwai
2015-10-20 17:39     ` Caleb Crome
2015-10-20 18:01       ` Takashi Iwai
2015-10-20 18:41         ` Caleb Crome

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=1445355673.7033.51.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bernard.gautier@intel.com \
    --cc=caleb@crome.org \
    --cc=han.lu@intel.com \
    --cc=tiwai@suse.de \
    /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.