From: Vinod Koul <vkoul@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org, linux-arm-msm@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] soundwire: qcom: Check device status before reading devid
Date: Wed, 6 Jul 2022 22:15:34 +0530 [thread overview]
Message-ID: <YsW8Lnhu19Wn2fZJ@matsya> (raw)
In-Reply-To: <20220706095644.5852-1-srinivas.kandagatla@linaro.org>
On 06-07-22, 10:56, Srinivas Kandagatla wrote:
> As per hardware datasheet its recommended that we check the device
> status before reading devid assigned by auto-enumeration.
>
> Without this patch we see SoundWire devices with invalid enumeration
> addresses on the bus.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2022-07-06 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 9:56 [PATCH] soundwire: qcom: Check device status before reading devid Srinivas Kandagatla
2022-07-06 16:45 ` Vinod Koul [this message]
2022-08-13 14:12 ` Amit Pundir
2022-08-13 14:23 ` Amit Pundir
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=YsW8Lnhu19Wn2fZJ@matsya \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.kernel.org \
--cc=yung-chuan.liao@linux.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