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
Subject: Re: [PATCH 0/9] ASoC: Intel: Skylake: Driver updates
Date: Thu, 15 Sep 2016 10:07:18 +0530 [thread overview]
Message-ID: <20160915043717.GT13920@localhost> (raw)
In-Reply-To: <20160914165043.GD27974@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1525 bytes --]
On Wed, Sep 14, 2016 at 05:50:43PM +0100, Mark Brown wrote:
> On Wed, Aug 24, 2016 at 06:03:12PM +0530, Vinod Koul wrote:
>
> > - The module instance IDs are manged in driver now.
>
> > Dharageswari R (5):
> > ASoC: Intel: Skylake: Unload all the loadable modules
> > ASoC: Intel: Skylake: Create dynamic instance ids for DSP modules
> > ASoC: Intel: Skylake: Use private instance id of modules in IPC
> > ASoC: Intel: Skylake: Table for module instance id and private id
> > ASoC: Intel: Skylake: Override the actual instance id's to pvt_id's
>
> I really don't understand what the point of these changes is at all,
> sorry. This makes it really hard to tell if they're doing what they're
> supposed to.
No issues, I will try to add more details on these bits.
The point of these changes is to allocate and manage an 'instance id' in
kernel.
Topology gives its own ID but thats just a free running values and we may
have more instance in complete graph than max allowed instance for that
module as not all parts of graph will be operation simultaneously.
So the way is to allocate and manage them in driver. We have used ffz to
maintain the ids, but ffz works on 32 bits, the max instance of some modules
is more than that so we added implementation on top of ffz for 128bits.
Later the patches use this and add a table for quick ref of used ids for
sending to DSPs.
Please do let me know if it helps, will add more details in patch changelogs...
Thanks
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2016-09-15 4:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 12:33 [PATCH 0/9] ASoC: Intel: Skylake: Driver updates Vinod Koul
2016-08-24 12:33 ` [PATCH 1/9] ASoC: Intel: Skylake: check manifest size Vinod Koul
2016-08-24 12:33 ` [PATCH 2/9] ASoC: Intel: Skylake: Fix the inverted logic check Vinod Koul
2016-08-24 12:33 ` [PATCH 3/9] ASoC: Intel: Skylake: Fix DMA control config size Vinod Koul
2016-08-24 12:33 ` [PATCH 4/9] ASoC: Intel: Skylake: Unload all the loadable modules Vinod Koul
2016-08-24 12:33 ` [PATCH 5/9] ASoC: Intel: Skylake: Create dynamic instance ids for DSP modules Vinod Koul
2016-09-14 16:43 ` Mark Brown
2016-09-15 4:31 ` Vinod Koul
2016-08-24 12:33 ` [PATCH 6/9] ASoC: Intel: Skylake: Use private instance id of modules in IPC Vinod Koul
2016-09-25 5:58 ` Applied "ASoC: Intel: Skylake: Use private instance id of modules in IPC" to the asoc tree Mark Brown
2016-08-24 12:33 ` [PATCH 7/9] ASoC: Intel: Skylake: Table for module instance id and private id Vinod Koul
2016-09-25 5:58 ` Applied "ASoC: Intel: Skylake: Add table for module id for quick ref" to the asoc tree Mark Brown
2016-08-24 12:33 ` [PATCH 8/9] ASoC: Intel: Skylake: Override the actual instance id's to pvt_id's Vinod Koul
2016-09-25 5:58 ` Applied "ASoC: Intel: Skylake: Update to use instance ids generated" to the asoc tree Mark Brown
2016-08-24 12:33 ` [PATCH 9/9] ASoC: Intel: Skylake: Add 32bit support Vinod Koul
2016-09-14 17:15 ` Applied "ASoC: Intel: Skylake: Add 32bit support" to the asoc tree Mark Brown
2016-09-14 16:50 ` [PATCH 0/9] ASoC: Intel: Skylake: Driver updates Mark Brown
2016-09-15 4:37 ` Vinod Koul [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=20160915043717.GT13920@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).