From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
Jeeja KP <jeeja.kp@intel.com>,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Subject: Re: [PATCH v2 5/6] ASoC: Intel: Add Skylake IPC library
Date: Thu, 9 Jul 2015 18:48:23 +0530 [thread overview]
Message-ID: <20150709131823.GR836@localhost> (raw)
In-Reply-To: <20150709052613.GK836@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1459 bytes --]
On Thu, Jul 09, 2015 at 10:56:13AM +0530, Vinod Koul wrote:
> On Wed, Jul 08, 2015 at 07:46:27PM +0100, Mark Brown wrote:
> > On Fri, Jul 03, 2015 at 04:04:06PM +0530, Vinod Koul wrote:
> >
> > Mostly looks good - a few small things here, nothing too major:
> >
> > > +static struct ipc_message *skl_ipc_reply_find_msg(struct sst_generic_ipc *ipc,
> > > + u64 ipc_header)
> > > +{
> > > + struct ipc_message *msg = NULL;
> > > + struct skl_ipc_header *header = (struct skl_ipc_header *)(&ipc_header);
> > > +
> > > + if (list_empty(&ipc->rx_list)) {
> > > + dev_err(ipc->dev, "ipc: rx list is empty but received 0x%x\n",
> > > + header->primary);
> > > + goto out;
> > > + }
> > > +
> > > + msg = list_first_entry(&ipc->rx_list, struct ipc_message, list);
> >
> > This says it finds the message but it appears to just return the head of
> > the list without reference to the supplied header other than casting it
> > to skl_ipc_header and possibly using it in an error print?
> Yes you are right. Actually currently we dont expect to queue up so we never
> bother looking up. But yes intention to find messages when they are quued, I
> will add that bit
And it doesn't work. The message comparison fails as we don't have a cookie
for replies :(
That would be reworked in future with FW. For now I am going to rename this
to skl_ipc_reply_get_msg() as it essentially gets first and only message in
queue
--
~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-09 13:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 10:34 [PATCH v2 0/6] ASoC: Intel: Sklyake - add IPC routines Vinod Koul
2015-07-03 10:34 ` [PATCH v2 1/6] ASoC: Intel: Add helper to poll register for DSP status Vinod Koul
2015-07-08 18:36 ` Mark Brown
2015-07-09 4:27 ` Vinod Koul
2015-07-09 10:48 ` Mark Brown
2015-07-09 10:53 ` Vinod Koul
2015-07-03 10:34 ` [PATCH v2 2/6] ASoC: Intel: Define SKL ADSP IPC and general purpose registers Vinod Koul
2015-07-03 10:34 ` [PATCH v2 3/6] ASoC: Intel: Reorganize the common dsp structure Vinod Koul
2015-07-08 18:38 ` Mark Brown
2015-07-09 4:32 ` Vinod Koul
2015-07-03 10:34 ` [PATCH v2 4/6] ASoC: Intel: Add helper to update register bits with attr RWC Vinod Koul
2015-07-08 18:47 ` Mark Brown
2015-07-09 4:44 ` Vinod Koul
2015-07-03 10:34 ` [PATCH v2 5/6] ASoC: Intel: Add Skylake IPC library Vinod Koul
2015-07-08 18:46 ` Mark Brown
2015-07-09 5:26 ` Vinod Koul
2015-07-09 13:18 ` Vinod Koul [this message]
2015-07-03 10:34 ` [PATCH v2 6/6] ASoC: Intel: Add DSP init and boot up functionality for SKL 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=20150709131823.GR836@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 \
--cc=subhransu.s.prusty@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox