From: Vinod Koul <vinod.koul@intel.com>
To: Guneshwor Singh <guneshwor.o.singh@intel.com>
Cc: ALSA <alsa-devel@alsa-project.org>, Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Patches Audio <patches.audio@intel.com>,
GuruprasadX <guruprasadx.pawse@intel.com>,
Mark Brown <broonie@kernel.org>,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>,
Pawse@alsa-project.org
Subject: Re: [PATCH 1/2] ASoC: Intel: Skylake: Request IRQ late only after all context are initialized
Date: Wed, 20 Dec 2017 10:58:11 +0530 [thread overview]
Message-ID: <20171220052810.GB18649@localhost> (raw)
In-Reply-To: <20171218051650.7027-1-guneshwor.o.singh@intel.com>
On Mon, Dec 18, 2017 at 10:46:49AM +0530, Guneshwor Singh wrote:
> From: "Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
>
> Sometimes during boot, panic is observed at sst_dsp_shim_read_unlocked().
> This happens when interrupt occurs before the context is initialized. So
> move the irq initialization only after the context is initialized
> completely.
Both:
Acked-By: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
next prev parent reply other threads:[~2017-12-20 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 5:16 [PATCH 1/2] ASoC: Intel: Skylake: Request IRQ late only after all context are initialized Guneshwor Singh
2017-12-18 5:16 ` [PATCH 2/2] ASoC: Intel: Skylake: Ensure dai and dailink registration happens in sequence Guneshwor Singh
2017-12-20 10:50 ` Applied "ASoC: Intel: Skylake: Ensure dai and dailink registration happens in sequence." to the asoc tree Mark Brown
2017-12-20 5:28 ` Vinod Koul [this message]
2017-12-20 10:50 ` Applied "ASoC: Intel: Skylake: Request IRQ late only after all context are initialized" " Mark Brown
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=20171220052810.GB18649@localhost \
--to=vinod.koul@intel.com \
--cc=Pawse@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guneshwor.o.singh@intel.com \
--cc=guruprasadx.pawse@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 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.