From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org, Jeeja KP <jeeja.kp@intel.com>
Subject: Re: [PATCH 3/6] ASoC: Intel: Skylake: Add functions for DSP module configuration
Date: Wed, 29 Jul 2015 22:20:29 +0530 [thread overview]
Message-ID: <20150729165029.GG29916@localhost> (raw)
In-Reply-To: <20150729123323.GC20130@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1337 bytes --]
On Wed, Jul 29, 2015 at 01:33:23PM +0100, Mark Brown wrote:
> On Tue, Jul 21, 2015 at 11:53:57PM +0530, Vinod Koul wrote:
>
> > + case SKL_CH_CFG_I2S_DUAL_STEREO_1:
> > + config = (0xFFFF00FF | (SKL_CHANNEL_LEFT << 8)
> > + | (SKL_CHANNEL_RIGHT << 12));
> > + break;
> > +
> > + default:
> > + config = 0xFFFFFFFF;
> > + }
>
> Missing break.
Should default have one always :)
>
> > +/*
> > + * Allocates queue for each module.
> > + * if dynamic, the pin_index is allocated 0 to max_pin.
> > + * In static, the pin_index is fixed based on module_id and instance id
> > + */
> > +static int skl_alloc_queue(struct skl_module_pin *mpin,
> > + struct skl_module_inst_id id, int max)
> > +{
> > + struct skl_module_pin m_pin = skl_get_queue(mpin, id, max);
> > +
> > + if (m_pin.pin_index < 0)
> > + return -EINVAL;
> > +
> > + if (m_pin.is_dynamic) {
> > + m_pin.in_use = true;
> > + m_pin.id.module_id = id.module_id;
> > + m_pin.id.instance_id = id.instance_id;
> > + }
>
> Double indentation here. It's really unclear to me why a static pin
> doesn't need to get merked as in use?
Oops, will fix
In static pin case, the pins come from topology binary where these are fixed
for a configuration, so don't need to be allocated thus marked and hence
freed.
--
~Vinod
--
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-07-29 16:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 18:23 [PATCH 0/6] ASoC: Intel: Skylake: Add DSP management routines Vinod Koul
2015-07-21 18:23 ` [PATCH 1/6] ASoC: Intel: Skylake: Add NHLT support to get BE config Vinod Koul
2015-07-23 16:41 ` Applied "ASoC: Intel: Skylake: Add NHLT support to get BE config" to the asoc tree Mark Brown
2015-07-21 18:23 ` [PATCH 2/6] ASoC: Intel: Skylake: Add dsp and ipc init helpers Vinod Koul
2015-07-23 16:41 ` Applied "ASoC: Intel: Skylake: Add dsp and ipc init helpers" to the asoc tree Mark Brown
2015-07-21 18:23 ` [PATCH 3/6] ASoC: Intel: Skylake: Add functions for DSP module configuration Vinod Koul
2015-07-29 12:33 ` Mark Brown
2015-07-29 16:50 ` Vinod Koul [this message]
2015-07-29 17:56 ` Mark Brown
2015-07-30 3:15 ` Vinod Koul
2015-07-30 19:01 ` Mark Brown
2015-07-31 4:53 ` Vinod Koul
2015-07-31 18:09 ` Mark Brown
2015-08-01 12:50 ` Vinod Koul
2015-07-21 18:23 ` [PATCH 4/6] ASoC: Intel: Skylake: Add helpers for SRC and converter modules Vinod Koul
2015-07-21 18:23 ` [PATCH 5/6] ASoC: Intel: Skylake: Add DSP module init and binding routines Vinod Koul
2015-07-29 12:35 ` Mark Brown
2015-07-29 16:55 ` Vinod Koul
2015-07-21 18:24 ` [PATCH 6/6] ASoC: Intel: Skylake: Add pipe management helpers Vinod Koul
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=20150729165029.GG29916@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jeeja.kp@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.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.