From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, jank@cadence.com,
srinivas.kandagatla@linaro.org, rander.wang@linux.intel.com,
ranjani.sridharan@linux.intel.com, hui.wang@canonical.com,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
bard.liao@intel.com
Subject: Re: [PATCH 1/3] soundwire: bus: clear bus clash interrupt before the mask is enabled
Date: Mon, 1 Feb 2021 15:58:44 +0530 [thread overview]
Message-ID: <20210201102844.GU2771@vkoul-mobl> (raw)
In-Reply-To: <20210126083746.3238-2-yung-chuan.liao@linux.intel.com>
On 26-01-21, 16:37, Bard Liao wrote:
> The SoundWire specification allows a Slave device to report a bus clash
> with the in-band interrupt mechanism when it detects a conflict while
> driving a bitSlot it owns. This can be a symptom of an electrical conflict
> or a programming error, and it's vital to detect reliably.
>
> Unfortunately, on some platforms, bus clashes are randomly reported by
> Slave devices after a bus reset, with an interrupt status set even before
> the bus clash interrupt is enabled. These initial spurious interrupts are
> not relevant and should optionally be filtered out, while leaving the
> interrupt mechanism enabled to detect 'true' issues.
>
> This patch suggests the addition of a Master level quirk to discard such
> interrupts. The quirk should in theory have been added at the Slave level,
> but since the problem was detected with different generations of Slave
> devices it's hard to point to a specific IP. The problem might also be
> board-dependent and hence dealing with a Master quirk is simpler.
>
> Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
> Reviewed-by: Rander Wang <rander.wang@linux.intel.com>
> Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> ---
> drivers/soundwire/bus.c | 10 ++++++++++
> include/linux/soundwire/sdw.h | 4 ++++
> 2 files changed, 14 insertions(+)
>
> diff --git a/drivers/soundwire/bus.c b/drivers/soundwire/bus.c
> index 6e1c988f3845..d394905936e4 100644
> --- a/drivers/soundwire/bus.c
> +++ b/drivers/soundwire/bus.c
> @@ -1240,6 +1240,7 @@ static int sdw_slave_set_frequency(struct sdw_slave *slave)
> static int sdw_initialize_slave(struct sdw_slave *slave)
> {
> struct sdw_slave_prop *prop = &slave->prop;
> + int status;
> int ret;
> u8 val;
>
> @@ -1247,6 +1248,15 @@ static int sdw_initialize_slave(struct sdw_slave *slave)
> if (ret < 0)
> return ret;
>
> + if (slave->bus->prop.quirks & SDW_MASTER_QUIRKS_CLEAR_INITIAL_CLASH) {
> + /* Clear bus clash interrupt before enabling interrupt mask */
> + status = sdw_read_no_pm(slave, SDW_SCP_INT1);
> + if (status & SDW_SCP_INT1_BUS_CLASH) {
> + dev_warn(&slave->dev, "Bus clash detected before INT mask is enabled\n");
> + sdw_write_no_pm(slave, SDW_SCP_INT1, SDW_SCP_INT1_BUS_CLASH);
> + }
> + }
> +
> /*
> * Set SCP_INT1_MASK register, typically bus clash and
> * implementation-defined interrupt mask. The Parity detection
> diff --git a/include/linux/soundwire/sdw.h b/include/linux/soundwire/sdw.h
> index f0b01b728640..a2766c3b603d 100644
> --- a/include/linux/soundwire/sdw.h
> +++ b/include/linux/soundwire/sdw.h
> @@ -405,6 +405,7 @@ struct sdw_slave_prop {
> * command
> * @mclk_freq: clock reference passed to SoundWire Master, in Hz.
> * @hw_disabled: if true, the Master is not functional, typically due to pin-mux
> + * @quirks: bitmask identifying optional behavior beyond the scope of the MIPI specification
> */
> struct sdw_master_prop {
> u32 revision;
> @@ -421,8 +422,11 @@ struct sdw_master_prop {
> u32 err_threshold;
> u32 mclk_freq;
> bool hw_disabled;
> + u32 quirks;
Can we do u64 here please.. I dont know where we would end up.. but
would hate if we start running out of space ..
> };
>
> +#define SDW_MASTER_QUIRKS_CLEAR_INITIAL_CLASH BIT(0)
> +
> int sdw_master_read_prop(struct sdw_bus *bus);
> int sdw_slave_read_prop(struct sdw_slave *slave);
>
> --
> 2.17.1
--
~Vinod
next prev parent reply other threads:[~2021-02-01 10:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 8:37 [PATCH 0/3] soundwire: clear bus clash/parity interrupt before the mask is enabled Bard Liao
2021-01-26 8:37 ` [PATCH 1/3] soundwire: bus: clear bus clash " Bard Liao
2021-02-01 10:28 ` Vinod Koul [this message]
2021-02-01 10:38 ` Vinod Koul
2021-02-01 16:18 ` Pierre-Louis Bossart
2021-02-02 4:39 ` Vinod Koul
2021-02-02 16:52 ` Pierre-Louis Bossart
2021-02-03 11:03 ` Vinod Koul
2021-01-26 8:37 ` [PATCH 2/3] soundwire: intel: add SDW_MASTER_QUIRKS_CLEAR_INITIAL_CLASH quirk Bard Liao
2021-02-01 10:42 ` Vinod Koul
2021-02-01 16:20 ` Pierre-Louis Bossart
2021-02-02 4:41 ` Vinod Koul
2021-02-02 16:53 ` Pierre-Louis Bossart
2021-01-26 8:37 ` [PATCH 3/3] soundwire: bus: clear parity interrupt before the mask is enabled Bard Liao
2021-02-01 11:09 ` Vinod Koul
2021-02-01 16:29 ` Pierre-Louis Bossart
2021-02-02 4:44 ` 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=20210201102844.GU2771@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.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