linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <Mario.Limonciello@dell.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Bastien Nocera <hadess@hadess.net>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Linux PM <linux-pm@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Hans de Goede <hdegoede@redhat.com>
Subject: RE: How to enable auto-suspend by default
Date: Tue, 10 Nov 2020 18:08:42 +0000	[thread overview]
Message-ID: <DM6PR19MB263696FE5FA50F344B559488FAE90@DM6PR19MB2636.namprd19.prod.outlook.com> (raw)
In-Reply-To: <X6rVT6IXHYQpqjic@kroah.com>

> On Tue, Nov 10, 2020 at 05:45:43PM +0000, Limonciello, Mario wrote:
> > > > I guess what Bastien is getting at is for newer devices supported by
> class
> > > > drivers rather than having to store an allowlist in udev rules, can we
> set
> > > > the allowlist in the kernel instead.  Then distributions that either
> don't
> > > > use systemd or don't regularly update udev rules from systemd can take
> > > > advantage of better defaults on modern hardware.
> > >
> > > That's what the "hardware ids" database is supposed to be handling.
> > > It's easier to manage this in userspace than in the kernel.
> > >
> > > I just love systems where people feel it is safer to update the kernel
> > > than it is to update a hardware database file :)
> > >
> > > > The one item that stood out to me in that rules file was 8086:a0ed.
> > > > It's listed as "Volteer XHCI", but that same device ID is actually
> present
> > > > in an XPS 9310 in front of me as well and used by the xhci-pci kernel
> > > module.
> > >
> > > That's an Intel PCI device id.  If someone else is abusing that number,
> > > I'm sure Intel would want to know about it and would be glad to go after
> > > them.
> >
> > Sorry I wasn't intending to insinuate an abuse of the number, but rather
> that
> > the PCI device in the "Volteer" product and that in XPS 9310 appear are the
> > same so they are possibly using the same hardware for this device.
> 
> Ok, but again, given that the device might be on different transports,
> the ability for the device to properly autosuspend might be different,
> right?
> 

I would think since it's provided by the PCH unlikely to be different transports.
I'm not sure though, Matthias might need to confirm.

On my side if I don't put that device into autosuspend the power consumption
goes up.

  reply	other threads:[~2020-11-10 18:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 10:57 How to enable auto-suspend by default Bastien Nocera
2020-11-10 11:34 ` Greg KH
2020-11-10 16:02   ` Limonciello, Mario
2020-11-10 17:18     ` Greg KH
2020-11-10 17:45       ` Limonciello, Mario
2020-11-10 18:00         ` Greg KH
2020-11-10 18:08           ` Limonciello, Mario [this message]
2020-11-10 19:55             ` Theodore Y. Ts'o
2020-11-10 20:45               ` Limonciello, Mario
2020-11-10 17:25     ` Mika Westerberg
2020-11-11 11:27       ` Hans de Goede
2020-11-11 14:31         ` Mika Westerberg
2020-11-23 13:54           ` Hans de Goede
2020-11-23 14:01             ` Mika Westerberg
2020-11-24 12:37             ` Mathias Nyman
2020-11-24 12:38               ` Hans de Goede
2020-11-24 15:53               ` Bastien Nocera
2020-11-11 16:03         ` Limonciello, Mario
2020-11-11 16:32           ` Greg KH
2020-11-24 16:02             ` Bastien Nocera
2020-11-24 16:35               ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR19MB263696FE5FA50F344B559488FAE90@DM6PR19MB2636.namprd19.prod.outlook.com \
    --to=mario.limonciello@dell.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hadess@hadess.net \
    --cc=hdegoede@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).