From: Bard Liao <yung-chuan.liao@linux.intel.com> To: alsa-devel@alsa-project.org, vkoul@kernel.org Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org, rander.wang@linux.intel.com, hui.wang@canonical.com, pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com, bard.liao@intel.com Subject: [PATCH v2 0/3] soundwire: clear bus clash/parity interrupt before the mask is enabled Date: Tue, 2 Mar 2021 16:27:17 +0800 [thread overview] Message-ID: <20210302082720.12322-1-yung-chuan.liao@linux.intel.com> (raw) The SoundWire specification allows a Slave device to report a bus clash or parity error with the in-band interrupt mechanism. Unfortunately, on some platforms, these errors are randomly reported and don't seem to be valid. This series 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. v2: - Reorder the patches sequence. - Add comments about each quirk. - Use u64 quirks. Bard Liao (3): soundwire: add master quirks for bus clash and parity soundwire: bus: handle master quirks for bus clash and parity soundwire: intel: add master quirks for bus clash and parity drivers/soundwire/bus.c | 39 +++++++++++++++++++++++++++++++++++ drivers/soundwire/intel.c | 3 +++ include/linux/soundwire/sdw.h | 22 ++++++++++++++++++++ 3 files changed, 64 insertions(+) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Bard Liao <yung-chuan.liao@linux.intel.com> To: alsa-devel@alsa-project.org, vkoul@kernel.org Cc: vinod.koul@linaro.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, pierre-louis.bossart@linux.intel.com, hui.wang@canonical.com, srinivas.kandagatla@linaro.org, sanyog.r.kale@intel.com, rander.wang@linux.intel.com, bard.liao@intel.com Subject: [PATCH v2 0/3] soundwire: clear bus clash/parity interrupt before the mask is enabled Date: Tue, 2 Mar 2021 16:27:17 +0800 [thread overview] Message-ID: <20210302082720.12322-1-yung-chuan.liao@linux.intel.com> (raw) The SoundWire specification allows a Slave device to report a bus clash or parity error with the in-band interrupt mechanism. Unfortunately, on some platforms, these errors are randomly reported and don't seem to be valid. This series 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. v2: - Reorder the patches sequence. - Add comments about each quirk. - Use u64 quirks. Bard Liao (3): soundwire: add master quirks for bus clash and parity soundwire: bus: handle master quirks for bus clash and parity soundwire: intel: add master quirks for bus clash and parity drivers/soundwire/bus.c | 39 +++++++++++++++++++++++++++++++++++ drivers/soundwire/intel.c | 3 +++ include/linux/soundwire/sdw.h | 22 ++++++++++++++++++++ 3 files changed, 64 insertions(+) -- 2.17.1
next reply other threads:[~2021-03-02 8:50 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-02 8:27 Bard Liao [this message] 2021-03-02 8:27 ` [PATCH v2 0/3] soundwire: clear bus clash/parity interrupt before the mask is enabled Bard Liao 2021-03-02 8:27 ` [PATCH v2 1/3] soundwire: add master quirks for bus clash and parity Bard Liao 2021-03-02 8:27 ` Bard Liao 2021-03-22 12:07 ` Vinod Koul 2021-03-22 12:07 ` Vinod Koul 2021-03-02 8:27 ` [PATCH v2 2/3] soundwire: bus: handle " Bard Liao 2021-03-02 8:27 ` Bard Liao 2021-03-02 8:27 ` [PATCH v2 3/3] soundwire: intel: add " Bard Liao 2021-03-02 8:27 ` Bard Liao 2021-03-22 12:10 ` [PATCH v2 0/3] soundwire: clear bus clash/parity interrupt before the mask is enabled Vinod Koul 2021-03-22 12:10 ` 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=20210302082720.12322-1-yung-chuan.liao@linux.intel.com \ --to=yung-chuan.liao@linux.intel.com \ --cc=alsa-devel@alsa-project.org \ --cc=bard.liao@intel.com \ --cc=gregkh@linuxfoundation.org \ --cc=hui.wang@canonical.com \ --cc=linux-kernel@vger.kernel.org \ --cc=pierre-louis.bossart@linux.intel.com \ --cc=rander.wang@linux.intel.com \ --cc=sanyog.r.kale@intel.com \ --cc=srinivas.kandagatla@linaro.org \ --cc=vinod.koul@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.