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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no 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 1FA14C32771 for ; Thu, 16 Jan 2020 01:44:00 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 9448320723 for ; Thu, 16 Jan 2020 01:43:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="GoVVIyM4" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9448320723 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=renesas.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id D889817A9; Thu, 16 Jan 2020 02:43:07 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz D889817A9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1579139037; bh=E+iVHS4aTVsJHEfSUO+iM+KvZpp5fCjrIK6FdpPww/U=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=GoVVIyM4gTc+uHcFmEwfDJ365hzSAzDF6QwJYNENJy0e0rZcOJ7iKGxWvmUh8ypBL 6oQGXooTlRiQ6wguq2KwQ5kTbGdMwcs0yVz13cDww+HB8UFIu0gPFDBg6SO5dHzImT CAx2qc7lML69xWuGRaH49RBrRTfudKXhWUaPr4Mw= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 4C868F8014B; Thu, 16 Jan 2020 02:43:07 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 570F4F801EB; Thu, 16 Jan 2020 02:43:06 +0100 (CET) Received: from relmlie5.idc.renesas.com (relmlor1.renesas.com [210.160.252.171]) by alsa1.perex.cz (Postfix) with ESMTP id BD181F800E9 for ; Thu, 16 Jan 2020 02:43:00 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz BD181F800E9 Date: 16 Jan 2020 10:42:57 +0900 X-IronPort-AV: E=Sophos;i="5.70,323,1574089200"; d="scan'208";a="36791105" Received: from unknown (HELO relmlir6.idc.renesas.com) ([10.200.68.152]) by relmlie5.idc.renesas.com with ESMTP; 16 Jan 2020 10:42:57 +0900 Received: from morimoto-PC.renesas.com (unknown [10.166.18.140]) by relmlir6.idc.renesas.com (Postfix) with ESMTP id 418EF412BC6B; Thu, 16 Jan 2020 10:42:57 +0900 (JST) Message-ID: <87lfq818im.wl-kuninori.morimoto.gx@renesas.com> From: Kuninori Morimoto To: Pierre-Louis Bossart In-Reply-To: <6d0f1830-a2f0-997a-99cc-05c268acefc6@linux.intel.com> References: <87h80x8t41.wl-kuninori.morimoto.gx@renesas.com> <130af222-1086-ebcf-6a0f-9a390f9afbc3@linux.intel.com> <14259e97-72f5-439f-b2f1-356b6e45bcfb@linux.intel.com> <7de214eb-d6a0-3f86-9eb3-76488f0ec99f@linux.intel.com> <87r2001bsi.wl-kuninori.morimoto.gx@renesas.com> <6d0f1830-a2f0-997a-99cc-05c268acefc6@linux.intel.com> User-Agent: Wanderlust/2.15.9 Emacs/24.5 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Cc: Linux-ALSA , Mark Brown , ojab // , Ranjani Sridharan Subject: Re: [alsa-devel] No sound since 5.4 on skl_n88l25_s4567 X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" Hi Pierre-Louis, Mark > > Is it possible to *real* fixup in the future, some day ? > > Quite unlikely I am afraid. This is a mismatch between topology and > machine driver, and there are no planned updates of those topologies > (which were never released for upstream use). > > In this case I guess the topology file was taken from a ChromeOS > distribution (based on v4.4 IIRC), so there's really no guarantee that > a fix would ever reach the user without a convoluted set of manual > updates. (snip) > Maybe we could have some sort of boolean flag in the component->driver > definition and explicitly request a backwards-compatible behavior > (e.g. for all SKL/KBL machine drivers) when that driver is known to be > flaky. There's already things like 'fully_routed', maybe we can add > something such as 'disable_route_check'? Hmm... I have no idea, but have no objection about this. Thank you for your help !! Best regards --- Kuninori Morimoto _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel