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=-9.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_PASS autolearn=ham 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 D434AC43387 for ; Sat, 5 Jan 2019 09:27:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9941F20874 for ; Sat, 5 Jan 2019 09:27:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1546680441; bh=6+3XDY9rNXUBoXnj2n2jhodgCxsEQLLDnirIg863o8s=; h=Subject:To:Cc:From:Date:List-ID:From; b=i594LIVfH32EW9pe+PE8KFJcERGMqZQ96jy1/SQd0v+W/mZpbZ6CyTuPvm3Mj2jIz tcwQ7cuGgiEVmpRDiCnS9i8DkStXdlxIUVqqz9lEeFwOK0/DEX9BwmAyUJrqGzpZru MoHDSb+Qvpy6YTz62h8DZVmrRGmTa0eY/WJ2bwa0= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726141AbfAEJ1U (ORCPT ); Sat, 5 Jan 2019 04:27:20 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:44765 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726140AbfAEJ1U (ORCPT ); Sat, 5 Jan 2019 04:27:20 -0500 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 57B4823154; Sat, 5 Jan 2019 04:27:19 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Sat, 05 Jan 2019 04:27:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=AgN6jx vdFqX51vnz29p7j5bzT65UXOUMHMEefHmZrek=; b=tBxYmPJoD7iGKl4AVPKoCw w3Sc4CP+bOaPdb3q1e91lMrADMHcUbwjGt084xzMaP7lOd02oIHuI0TjseuFxeKx AG9U/4GASK1ehvoZ4b/IMHqy/mJdmGSAWr+7D8vrpKebWlF2a249POfAqAdf30N0 mugn+FVB/FEZX4B7BN9mRa24F0IFGs4BWXg9vHh0+u+d1xE6wSobyA0yC5fl6kVt MBrxT56zdkV181D8++5avbOjZ/p6aw2TXCfSRFXP1bSlfr6BWpDFXFy26erc4iup 9uYDFcolDxt3lloK1I5auH4PjtEHuPmfAf1Kui/LzO/yS8GFHhJ4Q6jiIqginN5Q == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrvdefgddtheculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvffhfffkgggtgfesthekredttd dtlfenucfhrhhomhepoehgrhgvghhkhheslhhinhhugihfohhunhgurghtihhonhdrohhr gheqnecukfhppeeivddrudduledrudeiiedrleenucfrrghrrghmpehmrghilhhfrhhomh epghhrvghgsehkrhhorghhrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from localhost (unknown [62.119.166.9]) by mail.messagingengine.com (Postfix) with ESMTPA id DAF5DE4664; Sat, 5 Jan 2019 04:27:17 -0500 (EST) Subject: FAILED: patch "[PATCH] ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for" failed to apply to 4.14-stable tree To: hdegoede@redhat.com, broonie@kernel.org, pierre-louis.bossart@linux.intel.com Cc: From: Date: Sat, 05 Jan 2019 10:27:15 +0100 Message-ID: <1546680435163211@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ANSI_X3.4-1968 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org The patch below does not apply to the 4.14-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to . thanks, greg k-h ------------------ original commit in Linus's tree ------------------ >From 984bfb398a3af6fa9b7e80165e524933b0616686 Mon Sep 17 00:00:00 2001 From: Hans de Goede Date: Sun, 2 Dec 2018 13:21:22 +0100 Subject: [PATCH] ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Clapper The Clapper model Chromebook uses pmc_plt_clk_0 instead of pmc_plt_clk_3 for the mclk, just like the Swanky model. This commit adds a DMI based quirk for this. This fixing audio no longer working on these devices after commit 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL") that commit fixes us unnecessary keeping unused clocks on, but in case of the Clapper that was breaking audio support since we were not using the right clock in the cht_bsw_max98090_ti machine driver. Cc: stable@vger.kernel.org Fixes: 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL") Signed-off-by: Hans de Goede Acked-by: Pierre-Louis Bossart Signed-off-by: Mark Brown diff --git a/sound/soc/intel/boards/cht_bsw_max98090_ti.c b/sound/soc/intel/boards/cht_bsw_max98090_ti.c index 9d9f6e41d81c..ad0c98383853 100644 --- a/sound/soc/intel/boards/cht_bsw_max98090_ti.c +++ b/sound/soc/intel/boards/cht_bsw_max98090_ti.c @@ -389,6 +389,13 @@ static struct snd_soc_card snd_soc_card_cht = { }; static const struct dmi_system_id cht_max98090_quirk_table[] = { + { + /* Clapper model Chromebook */ + .matches = { + DMI_MATCH(DMI_PRODUCT_NAME, "Clapper"), + }, + .driver_data = (void *)QUIRK_PMC_PLT_CLK_0, + }, { /* Swanky model Chromebook (Toshiba Chromebook 2) */ .matches = {