From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, vkoul@kernel.org
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
bard.liao@intel.com,
Srinivasa Rao Mandadapu <quic_srivasam@quicinc.com>
Subject: Re: [PATCH v2] soundwire: qcom: adjust autoenumeration timeout
Date: Mon, 9 May 2022 09:36:31 -0500 [thread overview]
Message-ID: <0d645ee0-a54f-d9b4-9392-06ea1c37b29a@linux.intel.com> (raw)
In-Reply-To: <d17db27d-ad1b-f52c-50e9-4aab78ae0ff0@linaro.org>
>>> Even if enumeration timeout, we will not access the registers because
>>> the ASoC codec is not registered yet from WCD938x component master.
>>
>> What happens when the codec is registered then? the autoenumeration
> Codec is only registered after reset and when both TX and RX components
> are probed.
>
>> still didn't complete, so what prevents the read/writes from failing
>> then?
> If codec is reset and registered and for some reason autoenum took more
> than 100ms which will be hw bug then :-).
> In this case register read/writes will fail.
Does this reset result in the 'bus reset' in the SoundWire sence and
restart hence the autoenumeration?
It looks like you have a race between different components and starting
the bus before it's needed, no?
next prev parent reply other threads:[~2022-05-09 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 8:47 Srinivas Kandagatla
2022-05-06 14:13 ` Pierre-Louis Bossart
2022-05-07 6:52 ` Srinivas Kandagatla
2022-05-09 13:31 ` Pierre-Louis Bossart
2022-05-09 14:08 ` Srinivas Kandagatla
2022-05-09 14:24 ` Pierre-Louis Bossart
2022-05-09 14:32 ` Srinivas Kandagatla
2022-05-09 14:36 ` Pierre-Louis Bossart [this message]
2022-05-09 14:42 ` Srinivas Kandagatla
2022-05-09 6:33 ` 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=0d645ee0-a54f-d9b4-9392-06ea1c37b29a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_srivasam@quicinc.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=vkoul@kernel.org \
/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
all inboxes | Powered by JetHome®