From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, vkoul@kernel.org
Cc: robh@kernel.org, alsa-devel@alsa-project.org,
bgoswami@codeaurora.org, spapothi@codeaurora.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
broonie@kernel.org
Subject: Re: [alsa-devel] [PATCH v5 2/2] soundwire: qcom: add support for SoundWire controller
Date: Fri, 10 Jan 2020 10:35:19 -0600 [thread overview]
Message-ID: <94aefed4-9f0d-f81a-b5c0-0ad4cafc6a96@linux.intel.com> (raw)
In-Reply-To: <4dab7ee8-dc0e-bf61-24db-3e227c459575@linaro.org>
>>>> + if (sts & SWRM_INTERRUPT_STATUS_CMD_ERROR) {
>>>> + ctrl->reg_read(ctrl, SWRM_CMD_FIFO_STATUS, &value);
>>>> + dev_err_ratelimited(ctrl->dev,
>>>> + "CMD error, fifo status 0x%x\n",
>>>> + value);
>>>> + ctrl->reg_write(ctrl, SWRM_CMD_FIFO_CMD, 0x1);
>>>> + }
>>>> +
>>>> + if ((sts & SWRM_INTERRUPT_STATUS_NEW_SLAVE_ATTACHED) ||
>>>> + sts & SWRM_INTERRUPT_STATUS_CHANGE_ENUM_SLAVE_STATUS)
>>>> + schedule_work(&ctrl->slave_work);
>>>> +
>>>> + ctrl->reg_write(ctrl, SWRM_INTERRUPT_CLEAR, sts);
>>>
>>> is it intentional to clear the interrupts first, before doing
>>> additional checks?
>>>
>>
>> No, I can move it to right to the end!
>
> Reason why I did this was that if we run complete() before irq is
> cleared complete might trigger another read/write which can raise an
> interrupt. And with interrupt status not cleared we might miss it. This
> is very much timing dependent specially with the threaded irq.
>
> So code needs no change atm!
ok, a comment to keep track of this timing dependency could help future
generations then...
prev parent reply other threads:[~2020-01-10 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 9:28 [PATCH v5 0/2] soundwire: Add support to Qualcomm SoundWire master Srinivas Kandagatla
2019-12-19 9:28 ` [PATCH v5 1/2] dt-bindings: soundwire: add bindings for Qcom controller Srinivas Kandagatla
2019-12-19 9:28 ` [PATCH v5 2/2] soundwire: qcom: add support for SoundWire controller Srinivas Kandagatla
2019-12-19 16:07 ` [alsa-devel] " Pierre-Louis Bossart
2019-12-19 17:14 ` Srinivas Kandagatla
2020-01-10 12:12 ` Srinivas Kandagatla
2020-01-10 16:35 ` Pierre-Louis Bossart [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=94aefed4-9f0d-f81a-b5c0-0ad4cafc6a96@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=spapothi@codeaurora.org \
--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®