mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	<vkoul@kernel.org>, <yung-chuan.liao@linux.intel.com>,
	<sanyog.r.kale@intel.com>
Cc: <patches@opensource.cirrus.com>, <alsa-devel@alsa-project.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soundwire: bus: Fix wrong port number in sdw_handle_slave_alerts()
Date: Tue, 20 Sep 2022 10:17:28 +0100	[thread overview]
Message-ID: <633a7b75-91f8-9a54-c042-87079d27cc8c@opensource.cirrus.com> (raw)
In-Reply-To: <9edb1178-7454-eb3f-60a5-d3f73d01c9d6@linux.intel.com>

On 19/09/2022 09:44, Pierre-Louis Bossart wrote:
> 
> 
> On 9/17/22 16:02, Richard Fitzgerald wrote:
>> for_each_set_bit() gives the bit-number counting from 0 (LSbit==0).
>> When processing INTSTAT2, bit 0 is DP4 so the port number is (bit + 4).
>> Likewise for INTSTAT3 bit 0 is DP11 so port number is (bit + 11).
>>
>> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
> 
> Another thing that never worked, but no one has used port interrupts so
> far. I only used it for PRBS tests in early enabling some 3 years ago,
> and it was for port 2 IIRC.
> 

Except us because Cirrus Soundwire requires a full DP prepare sequence,
it doesn't support simplified DP_SM.

There's still the problem of the code deadlocking while waiting for the
prepare interrupt, because it holds the bus lock while waiting for the
completion, so the alert handler can't run. That's something I need to
look at fixing. But it's not a blocker, just means that the code has to
wait the whole timeout for each amp. (That's another thing, couldn't we
issue all the DP prepares first so the amps prepare in parallel, then
wait for them to ack?)

      reply	other threads:[~2022-09-20  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 14:02 Richard Fitzgerald
2022-09-19  8:44 ` Pierre-Louis Bossart
2022-09-20  9:17   ` Richard Fitzgerald [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=633a7b75-91f8-9a54-c042-87079d27cc8c@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=sanyog.r.kale@intel.com \
    --cc=vkoul@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

all inboxes | Powered by JetHome®