From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Richard Fitzgerald <rf@opensource.cirrus.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: Mon, 19 Sep 2022 10:44:03 +0200 [thread overview]
Message-ID: <9edb1178-7454-eb3f-60a5-d3f73d01c9d6@linux.intel.com> (raw)
In-Reply-To: <20220917140256.689678-1-rf@opensource.cirrus.com>
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.
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> ---
> drivers/soundwire/bus.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/soundwire/bus.c b/drivers/soundwire/bus.c
> index 8eded1a55227..df0ae869ee51 100644
> --- a/drivers/soundwire/bus.c
> +++ b/drivers/soundwire/bus.c
> @@ -1622,7 +1622,7 @@ static int sdw_handle_slave_alerts(struct sdw_slave *slave)
> port = buf2[0] & SDW_SCP_INTSTAT2_PORT4_10;
> for_each_set_bit(bit, &port, 8) {
> /* scp2 ports start from 4 */
> - port_num = bit + 3;
> + port_num = bit + 4;
> sdw_handle_port_interrupt(slave,
> port_num,
> &port_status[port_num]);
> @@ -1634,7 +1634,7 @@ static int sdw_handle_slave_alerts(struct sdw_slave *slave)
> port = buf2[1] & SDW_SCP_INTSTAT3_PORT11_14;
> for_each_set_bit(bit, &port, 8) {
> /* scp3 ports start from 11 */
> - port_num = bit + 10;
> + port_num = bit + 11;
> sdw_handle_port_interrupt(slave,
> port_num,
> &port_status[port_num]);
next prev parent reply other threads:[~2022-09-19 8:53 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 [this message]
2022-09-20 9:17 ` Richard Fitzgerald
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=9edb1178-7454-eb3f-60a5-d3f73d01c9d6@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.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®