Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp590163pxb; Sat, 10 Apr 2021 12:24:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyWtBOy+wcuPCs+QK995liFr7ThfIdAdFIQcSloiUob4tKdS0FFLWHQXC+V5rEGVk/RRM0W X-Received: by 2002:a63:5066:: with SMTP id q38mr1613165pgl.119.1618082669401; Sat, 10 Apr 2021 12:24:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618082669; cv=none; d=google.com; s=arc-20160816; b=m5owGCAlBbp2u7dYrbtZmCxlvPiNTHrV+UNSFbSY6MhGJeJiemI48hmNdwWlPe+2mi knBzfwdWNd4T9AWzEfRMfEjCD+cSDvaZg8ggM4VAymsiO7hx+a/JSiT8fAM9jGJkSrll RoWaLtlRxwMYN3HaJzpbTkEJJo0I5pW4aHPvfQ+1/msDzFQ1TOadbzLZlPbciR2F4iOH HbRh6J6ywqY3c3wMacATZ74kuAe51S0skX9jl9NBWGzWMSLnkB/4+q+tfPCK8iLGzXIl f375hDmngBPjSW8IebCs0ujI9UYjVLHZiTNUgapPe4c9tdgQi1wQID3fYlnG9tBkIfmn lv3w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=hvWsHSad8ZyYZrc1LEM9/dspV57w3cIikmRneJ0MQxc=; b=vMLFPvKH67GdhX7vogRIvm9nK7J6dc+XsmPCuL1OklbdGYrMcIr66I5wZT8XaV2HUR t0ig9oFJ0/tHBF/vBjL42wxIXJXySzrYt4UZ7MmnFWaxGKEHrY1Trkpp3xSHBotWU5Kt NXELhZrwh+sCI/4BndyUoNkRN1ZUrBcL1ncbIBhNii6uHzQgcjc3JS6kMeDHMwytTKcn u31R5tuqnMA4s9k272lpjBqHjGbh3+oISTqTI4zuvV2roJovHmKV1CnBS88hXuwkZWPU Te80frXnqhFmh5if5mCZ4O2lk6xnEnWQ/TYw9oatX/Jx5yA8/bTY4OS45qE9vuvB+VLn EQEw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s128si7439866pgc.80.2021.04.10.12.24.17; Sat, 10 Apr 2021 12:24:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234948AbhDJTXf (ORCPT + 99 others); Sat, 10 Apr 2021 15:23:35 -0400 Received: from bmailout3.hostsharing.net ([176.9.242.62]:44405 "EHLO bmailout3.hostsharing.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234751AbhDJTXd (ORCPT ); Sat, 10 Apr 2021 15:23:33 -0400 Received: from h08.hostsharing.net (h08.hostsharing.net [IPv6:2a01:37:1000::53df:5f1c:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.hostsharing.net", Issuer "RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1" (verified OK)) by bmailout3.hostsharing.net (Postfix) with ESMTPS id 1A9A51003D000; Sat, 10 Apr 2021 21:23:15 +0200 (CEST) Received: by h08.hostsharing.net (Postfix, from userid 100393) id DCAFB1E6B5; Sat, 10 Apr 2021 21:23:14 +0200 (CEST) Date: Sat, 10 Apr 2021 21:23:14 +0200 From: Lukas Wunner To: Roy Spliet Cc: Karol Herbst , Kai-Heng Feng , "moderated list:SOUND" , Kai Vehmanen , Takashi Iwai , nouveau , Pierre-Louis Bossart , tiwai@suse.com, Alex Deucher , Alan Stern , Mike Rapoport , Linux PCI , Bjorn Helgaas , Jaroslav Kysela , open list Subject: Re: [Nouveau] [PATCH v2] ALSA: hda: Continue to probe when codec probe fails Message-ID: <20210410192314.GB16240@wunner.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 10, 2021 at 04:51:27PM +0100, Roy Spliet wrote: > Can I ask someone with more > technical knowledge of snd_hda_intel and vgaswitcheroo to brainstorm about > the possible challenges of nouveau taking matters into its own hand rather > than keeping this PCI quirk around? It sounds to me like the HDA is not powered if no cable is plugged in. What is reponsible then for powering it up or down, firmware code on the GPU or in the host's BIOS? Ideally, we should try to find out how to control HDA power from the operating system rather than trying to cooperate with whatever firmware is doing. If we have that capability, the OS should power the HDA up and down as it sees fit. Thanks, Lukas