Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp488907pxb; Wed, 11 Nov 2020 08:33:53 -0800 (PST) X-Google-Smtp-Source: ABdhPJyUsGI2TZZuQ00Zfbffd1pt1WWewY7tU9sCR/Q2ombAmKBGo5kZKXZsdeIt7Khzc7VxJ5yI X-Received: by 2002:a17:906:ca83:: with SMTP id js3mr27113959ejb.42.1605112431361; Wed, 11 Nov 2020 08:33:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605112431; cv=none; d=google.com; s=arc-20160816; b=Aae59Ykl5MFOsWUfOXfs4/qO80P3ndeICTWi6J2fT1RzAaAS1ojHEY7lqS57MHCQVy ffTpMiP863CzC2kUVxCDJfFPjMJCR1Q5trPMvLWjJJGs/Man1pi2JueOTtH30yP09H42 /CToi0/2nXuGmtI94u50JTCxGzUnb63n+JOJ64wzZwlYNesELcmUC7noZbaQcstrdqO4 RhggTTIrdg7uVtsU+IilbgQhXQ+oFJhJAYS83E9tMJHO1feTRW8bc6N+tQHm8F7N+IDO RZdBOxcKvI1vUJ3MUzw17YSEuSKuWEpGTDMHJFXyGoxmeH2fujvkMylOHy3P2cIoEvCy Duiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=JjoJNEJwgRvqwWdwGnz/N+84jQr+1c9srwA20JPJIMw=; b=1ITJgBic5jhJau4Mqt9wiqB4okeMHVn0CHd40m6SjIijdgd96ZTAqYuJx5O2PVwlNW XG3iiJYUw6r900jA182oCWyl++xv63L276BGJ24T4im4G/ZwBIetOpDxlOfJLL58WoQ/ LVv852GmD2JE1eQOJfDXi2R1Qp0HThYTN6hbFuAdd3Lv7Q85QlAGbo+CBRFsc8jgOzt1 Gjmd8CBV1h9GCP6w4bKZ2FBNr0pNiLUkkl4+uENhJHYAbL4zZhZUcPLlEs7Tpn/zBQzw T6PlWL+SmCLQGQxApfCeIDlZVHXjyngGxnmKdKXaK5Mb0Q4ytnxrla9kA8or7TyJIlXc k84Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=pTJO7zCD; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i59si1846611edd.308.2020.11.11.08.33.27; Wed, 11 Nov 2020 08:33:51 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=pTJO7zCD; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727377AbgKKQbY (ORCPT + 99 others); Wed, 11 Nov 2020 11:31:24 -0500 Received: from mail.kernel.org ([198.145.29.99]:53796 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726208AbgKKQbX (ORCPT ); Wed, 11 Nov 2020 11:31:23 -0500 Received: from localhost (83-86-74-64.cable.dynamic.v4.ziggo.nl [83.86.74.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 06267206B5; Wed, 11 Nov 2020 16:31:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605112282; bh=u1W79eBhFJDijrV1bXsrDHc02dojBuPzlmTjNRwzECM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pTJO7zCDEAIc4ENcSgzN9lsMdGt7wXtmAxlhGhYh9RxxpVjT7DGXoeXUS10GeaFoJ TqdEeulUJiiE6h4kRf+qbVUdou0DBrWTQpZdIfznMNMFg0Uy+wXHd5P9E0SvPkdoXw eDeNfg3jKEyZgGrNPO6pRBc2UXlWpwDPeeHKE9T4= Date: Wed, 11 Nov 2020 17:32:22 +0100 From: Greg KH To: "Limonciello, Mario" Cc: Hans de Goede , Mika Westerberg , Bastien Nocera , Linux PM , "linux-usb@vger.kernel.org" , Linux Kernel Mailing List , "linux-input@vger.kernel.org" , Mathias Nyman Subject: Re: How to enable auto-suspend by default Message-ID: References: <20201110172517.GC2495@lahna.fi.intel.com> <30957f1a-1fe5-5d9a-101b-25f12fb93907@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 11, 2020 at 04:03:30PM +0000, Limonciello, Mario wrote: > > >> Given we're effectively ending up with the combination of runtime PM turned > > >> on by udev rules, do we need something like this for that ID: > > >> > > >> > > https://github.com/torvalds/linux/commit/6a7c533d4a1854f54901a065d8c672e890400 > > d8a > > >> > > >> @Mika Westerberg should 8086:a0ed be quirked like the TCSS xHCI too? > > > > > > I think this one is the TGL PCH xHCI. The quirk currently for xHCI > > > controllers that are part of the TCSS (Type-C SubSystem) where it is > > > important to put all devices into low power mode whenever possible, > > > otherwise it keeps the whole block on. > > > > Note that there are currently some IDs missing from the xHCIs which > > are part of the TCSS too. At least the id for the xHCI in the thunderbolt > > controller on the Lenovo T14 gen 1 is missing. I started a discussion > > about extending the kernel quirk list for this vs switching to hwdb > > a while a go: > > > > https://lore.kernel.org/linux-usb/b8b21ba3-0a8a-ff54-5e12- > > cf8960651086@redhat.com/ > > > > The conclusion back then was to switch to hwdb, but I never got around to > > this. > > I guess the problem I see with switching to a hwdb for this type of thing is > that if there is a "bug" in your kernel driver around autosuspend you will > then be potentially causing it to occur more regularly on a kernel that didn't > necessarily pick up the fix but does have the newer hwdb. > > I don't know how common that will really be though. > > Since Mika mentioned the really light userspace scenario, what about shipping > the hwdb "with" the kernel in tree? This could allow evicting all these quirk > scenarios from the kernel at the same time as switching to a hwdb and also cover > the problem I suggested might happen with a bug in older kernel and newer userspace. We took things out of the kernel to put it in hwdb years ago as it was easier for people to update a "text file" than it was their kernel image. I don't think you want to go backwards here :) thanks, greg k-h