From: Vinod Koul <vinod.koul@intel.com>
To: Guneshwor Singh <guneshwor.o.singh@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Patches Audio <patches.audio@intel.com>
Subject: Re: [PATCH 1/4] ASoC: Intel: Skylake: Reset the controller in probe
Date: Sat, 29 Jul 2017 10:05:28 +0530 [thread overview]
Message-ID: <20170729043527.GZ3053@localhost> (raw)
In-Reply-To: <20170728104216.26859-1-guneshwor.o.singh@intel.com>
On Fri, Jul 28, 2017 at 04:12:13PM +0530, Guneshwor Singh wrote:
> Controller can be in reset state by default. Capability structure
> traversal requires the controller to be out of reset else it
> results in broken capability parsing. Hence make sure that controller is
> out of reset before parsing capabilities by doing a full reset.
Good series and nice changelogs...
Whole series:
Acked-By: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
next prev parent reply other threads:[~2017-07-29 4:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 10:42 [PATCH 1/4] ASoC: Intel: Skylake: Reset the controller in probe Guneshwor Singh
2017-07-28 10:42 ` [PATCH 2/4] ASoC: Intel: bxtn: Remove code loader reference in cleanup Guneshwor Singh
2017-08-01 14:16 ` Applied "ASoC: Intel: bxtn: Remove code loader reference in cleanup" to the asoc tree Mark Brown
2017-07-28 10:42 ` [PATCH 3/4] ASoC: Intel: Skylake: Remove return check for skl_codec_create() Guneshwor Singh
2017-08-01 14:16 ` Applied "ASoC: Intel: Skylake: Remove return check for skl_codec_create()" to the asoc tree Mark Brown
2017-07-28 10:42 ` [PATCH 4/4] ASoC: Intel: Skylake: Fix potential null pointer dereference Guneshwor Singh
2017-08-01 14:16 ` Applied "ASoC: Intel: Skylake: Fix potential null pointer dereference" to the asoc tree Mark Brown
2017-07-29 4:35 ` Vinod Koul [this message]
2017-08-01 14:16 ` Applied "ASoC: Intel: Skylake: Reset the controller in probe" " 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=20170729043527.GZ3053@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guneshwor.o.singh@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@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