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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id AC581C433EF for ; Thu, 14 Jul 2022 01:10:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231490AbiGNBKx (ORCPT ); Wed, 13 Jul 2022 21:10:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50150 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229492AbiGNBKv (ORCPT ); Wed, 13 Jul 2022 21:10:51 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4CA4520198 for ; Wed, 13 Jul 2022 18:10:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657761050; x=1689297050; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=L+WCKv2qelzFb6SQcNhBxVlX9xUhE7ThSQkIyIWZPRM=; b=igERpRGrSBfe68QZeAZMvnidwzNrCR79YXkaCh3HIZZhNNExXLy4aQcN HUEqul5cF6k5uCsbSZb8isMeXnjDsiYak74nKJJNWQ29+7wCRaVU3rYnZ pdtanv0C5X1T5Wv05UnJN5cB7ScMIfBh8Hu4XQ002NsJMMxmqikwfu/8f Ukmh30Ofyq0Fjl6g8BWG4Bnt6qqmq1W/uWasuSNaJ7GDMbjcfMD5BCdyH A5cm5y+fTIR7u6IZqqkB6afLz8HpKhaEgolW+WoSKi5dTpdzlBg4LsMUc zu0eBT7OiBXifxjjvvEE2TN3bRhxprX3W1PsX735dmFwe1fpzPFOB7egz w==; X-IronPort-AV: E=McAfee;i="6400,9594,10407"; a="282937908" X-IronPort-AV: E=Sophos;i="5.92,269,1650956400"; d="scan'208";a="282937908" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Jul 2022 18:10:50 -0700 X-IronPort-AV: E=Sophos;i="5.92,269,1650956400"; d="scan'208";a="593192503" Received: from bard-ubuntu.sh.intel.com ([10.239.185.57]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Jul 2022 18:10:47 -0700 From: Bard Liao To: alsa-devel@alsa-project.org, vkoul@kernel.org Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org, tiwai@suse.de, broonie@kernel.org, pierre-louis.bossart@linux.intel.com, bard.liao@intel.com Subject: [PATCH 0/4] ASoC/soundwire: log actual PING status on resume issues Date: Thu, 14 Jul 2022 09:10:39 +0800 Message-Id: <20220714011043.46059-1-yung-chuan.liao@linux.intel.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org we've been stuck with problems in the dual-amplifier configurations where one of the two devices seems to become UNATTACHED and never regains sync, see https://github.com/thesofproject/linux/issues/3638. This is a rather infrequent issue that may happen once or twice per month, but still it remains a concern. One possibility is that the device does lose sync but somehow our hardware detection fails to see it resync. This series just adds a basic read directly from the PING frames to help confirm if yes/no the device regain sync. The change is mainly on soundwire. @Mark, Could you ack the ASoC patch if it looks good to you? Pierre-Louis Bossart (4): soundwire: add read_ping_status helper definition in manager ops soundwire: intel/cadence: expose PING status in manager ops soundwire: add sdw_show_ping_status() helper ASoC: codecs: show PING status on resume failures drivers/soundwire/bus.c | 32 ++++++++++++++++++++++++++++++ drivers/soundwire/cadence_master.c | 8 ++++++++ drivers/soundwire/cadence_master.h | 2 ++ drivers/soundwire/intel.c | 1 + include/linux/soundwire/sdw.h | 5 +++++ sound/soc/codecs/max98373-sdw.c | 2 ++ sound/soc/codecs/rt1308-sdw.c | 2 ++ sound/soc/codecs/rt1316-sdw.c | 2 ++ sound/soc/codecs/rt5682-sdw.c | 2 ++ sound/soc/codecs/rt700-sdw.c | 2 ++ sound/soc/codecs/rt711-sdca-sdw.c | 2 ++ sound/soc/codecs/rt715-sdca-sdw.c | 2 ++ sound/soc/codecs/rt715-sdw.c | 2 ++ 13 files changed, 64 insertions(+) -- 2.25.1