All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: yang.a.fang@intel.com
Cc: broonie@kernel.org, lgirdwood@gmail.com,
	alsa-devel@alsa-project.org, sathyanarayana.nujella@intel.com,
	kevin.strasser@linux.intel.com, srinivas.sripathi@intel.com,
	shilpa.sreeramalu@intel.com, dinesh.mirche@intel.com,
	stable@vger.kernel.org
Subject: Re: [PATCH v3] ASoC: Intel: Get correct usage_count value to load firmware
Date: Wed, 15 Jul 2015 21:46:10 +0530	[thread overview]
Message-ID: <20150715161610.GE5086@localhost> (raw)
In-Reply-To: <1436972289-29835-1-git-send-email-yang.a.fang@intel.com>

On Wed, Jul 15, 2015 at 07:58:09AM -0700, yang.a.fang@intel.com wrote:
> From: Shilpa Sreeramalu <shilpa.sreeramalu@intel.com>
> 
> The usage_count variable was read before it was set to the correct
> value, due to which the firmware load was failing. Because of this
> IPC messages sent to the firmware were timing out causing a delay
> of about 1 second while playing audio from the internal speakers.
> 
> With this patch the usage_count is read after the function call
> pm_runtime_get_sync which will increment the usage_count variable
> and the firmware load is successful and all the IPC messages are
> processed correctly.

Acked-by: Vinod Koul <vinod.koul@intel.com>

-- 
~Vinod


      reply	other threads:[~2015-07-15 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 18:13 [PATCH] ASoC: Intel: Get correct usage_count value to load firmware yang.a.fang
2015-07-14 18:16 ` Mark Brown
2015-07-14 18:17   ` Fang, Yang A
2015-07-14 18:17     ` Fang, Yang A
2015-07-14 18:23 ` [PATCH v2] " yang.a.fang
2015-07-15 11:52   ` Mark Brown
2015-07-15 14:58   ` [PATCH v3] " yang.a.fang
2015-07-15 16:16     ` 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=20150715161610.GE5086@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=dinesh.mirche@intel.com \
    --cc=kevin.strasser@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=sathyanarayana.nujella@intel.com \
    --cc=shilpa.sreeramalu@intel.com \
    --cc=srinivas.sripathi@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=yang.a.fang@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.