From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A085FC433E6 for ; Tue, 26 Jan 2021 11:21:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 76EE623104 for ; Tue, 26 Jan 2021 11:21:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392252AbhAZLUp (ORCPT ); Tue, 26 Jan 2021 06:20:45 -0500 Received: from mga11.intel.com ([192.55.52.93]:35240 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390377AbhAZIjs (ORCPT ); Tue, 26 Jan 2021 03:39:48 -0500 IronPort-SDR: +Q3xd+7DBfrhR6KudA2y4SHhA/iCoTo9cauN6mWjj7U0AXYd3Nx5Ovabp/mLFZs69vQWeiGSul 5tAKaszJ+abA== X-IronPort-AV: E=McAfee;i="6000,8403,9875"; a="176357405" X-IronPort-AV: E=Sophos;i="5.79,375,1602572400"; d="scan'208";a="176357405" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Jan 2021 00:37:57 -0800 IronPort-SDR: +zyozuRQn8lz0RxRfSC5afVN3ieABG3WvjsYCtO3LcLcwuCoKulEKbGSQMlwIS+Lj7hNH408Ut jzvBWKVYTW0Q== X-IronPort-AV: E=Sophos;i="5.79,375,1602572400"; d="scan'208";a="577731212" Received: from bard-ubuntu.sh.intel.com ([10.239.13.33]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Jan 2021 00:37:53 -0800 From: Bard Liao To: alsa-devel@alsa-project.org, vkoul@kernel.org Cc: vinod.koul@linaro.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: [PATCH 0/3] soundwire: clear bus clash/parity interrupt before the mask is enabled Date: Tue, 26 Jan 2021 16:37:43 +0800 Message-Id: <20210126083746.3238-1-yung-chuan.liao@linux.intel.com> X-Mailer: git-send-email 2.17.1 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Bard Liao (2): soundwire: bus: clear bus clash interrupt before the mask is enabled soundwire: intel: add SDW_MASTER_QUIRKS_CLEAR_INITIAL_CLASH quirk Pierre-Louis Bossart (1): soundwire: bus: clear parity interrupt before the mask is enabled drivers/soundwire/bus.c | 19 +++++++++++++++++++ drivers/soundwire/intel.c | 3 +++ include/linux/soundwire/sdw.h | 5 +++++ 3 files changed, 27 insertions(+) -- 2.17.1