shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-06 17:18:12 +03:00
Code
80d4ea4457
systemd/tools/chromiumos/gen_autosuspend_rules.py

403 lines
8.3 KiB
Python
Raw Normal View History

hwdb: update for v248 Seems to be additions and corrections as usual. Includes an update of the chromiumos autosuspend rules.
2021-03-08 15:13:27 +03:00
#!/usr/bin/env python3
licensing: add spdx header to chromiumos helper, move license file It makes it easier to process the license automatically like other files. The text of the license in tools/chromiumos/LICENSE matches https://spdx.org/licenses/BSD-3-Clause.html exactly.
2021-10-01 13:49:36 +03:00
# SPDX-License-Identifier: BSD-3-Clause
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# -*- coding: utf-8 -*-
# Copyright 2017 The Chromium OS Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
licensing: add spdx header to chromiumos helper, move license file It makes it easier to process the license automatically like other files. The text of the license in tools/chromiumos/LICENSE matches https://spdx.org/licenses/BSD-3-Clause.html exactly.
2021-10-01 13:49:36 +03:00
# found in the LICENSES/BSD-3-Clause.txt file.
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
"""Autosuspend udev rule generator
This script is executed at build time to generate udev rules. The
resulting rules file is installed on the device, the script itself
is not.
"""
# List of USB devices (vendorid:productid) for which it is safe to enable
# autosuspend.
USB_IDS = []
# Host Controllers and internal hubs
USB_IDS += [
# Linux Host Controller (UHCI) (most older x86 boards)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"1d6b:0001",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Linux Host Controller (EHCI) (all boards)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"1d6b:0002",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Linux Host Controller (XHCI) (most newer boards)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"1d6b:0003",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# SMSC (Internal HSIC Hub) (most Exynos boards)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0424:3503",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Intel (Rate Matching Hub) (all x86 boards)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"05e3:0610",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Intel (Internal Hub?) (peppy, falco)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8087:0024",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Genesys Logic (Internal Hub) (rambi)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8087:8000",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# Microchip (Composite HID + CDC) (kefka)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04d8:0b28",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# Webcams
USB_IDS += [
# Chicony (zgb)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04f2:b1d8",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Chicony (mario)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04f2:b262",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Chicony (stout)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04f2:b2fe",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Chicony (butterfly)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04f2:b35f",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Chicony (rambi)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04f2:b443",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Chicony (glados)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04f2:b552",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# LiteOn (spring)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"058f:b001",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Foxlink? (butterfly)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"05c8:0351",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Foxlink? (butterfly)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"05c8:0355",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Cheng Uei? (falco)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"05c8:036e",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# SuYin (parrot)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"064e:d251",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Realtek (falco)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0bda:571c",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# IMC Networks (squawks)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"13d3:5657",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Sunplus (parrot)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"1bcf:2c17",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# (C-13HDO10B39N) (alex)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2232:1013",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# (C-10HDP11538N) (lumpy)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2232:1017",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# (Namuga) (link)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2232:1033",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# (C-03FFM12339N) (daisy)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2232:1037",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# (C-10HDO13531N) (peach)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2232:1056",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# (NCM-G102) (samus)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2232:6001",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Acer (stout)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"5986:0299",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# Bluetooth Host Controller
USB_IDS += [
# Hon-hai (parrot)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0489:e04e",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Hon-hai (peppy)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0489:e056",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Hon-hai (Kahlee)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0489:e09f",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# QCA6174A (delan)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0489:e0a2",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# LiteOn (parrot)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04ca:3006",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# LiteOn (aleena)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04ca:3016",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# LiteOn (scarlet)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"04ca:301a",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# Realtek (blooglet)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0bda:b00c",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Atheros (stumpy, stout)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0cf3:3004",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Atheros (AR3011) (mario, alex, zgb)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0cf3:3005",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Atheros (stumyp)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0cf3:3007",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Atheros (butterfly)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0cf3:311e",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Atheros (scarlet)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0cf3:e300",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Marvell (rambi)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"1286:2046",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Marvell (gru)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"1286:204e",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Intel (rambi, samus)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8087:07dc",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Intel (strago, glados)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8087:0a2a",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Intel (octopus)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8087:0aaa",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Intel (hatch)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8087:0026",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Intel (atlas)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8087:0025",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# WWAN (LTE)
USB_IDS += [
# Huawei (ME936) (kip)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"12d1:15bb",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Fibocom (L850-GL) (coral, nautilus, sarien)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2cb7:0007",
hwdb: update chromiumos autosuspend rules
2020-11-26 15:54:08 +03:00
# Fibocom (NL668, NL652)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2cb7:01a0",
# Fibocom (FM101-GL) (mbim)
"2cb7:01a2",
# Fibocom (FM101-GL) (adb)
"2cb7:01a4",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# Mass Storage
USB_IDS += [
# Genesys (SD card reader) (lumpy, link, peppy)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"05e3:0727",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Realtek (SD card reader) (mario, alex)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0bda:0138",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Realtek (SD card reader) (helios)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0bda:0136",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Realtek (SD card reader) (falco)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0bda:0177",
Update hwdb autosuspend rules
2023-11-01 16:44:24 +03:00
# Realtek (SD card reader) (pirrha)
"0bda:0129",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# Security Key
USB_IDS += [
# Yubico.com
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"1050:0211",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Yubico.com (HID firmware)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"1050:0200",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Google Titan key
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"18d1:5026",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# USB Audio devices
USB_IDS += [
# Google USB-C to 3.5mm Digital Headphone Jack Adapter 'Mir'
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"18d1:5025",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Google USB-C to 3.5mm Digital Headphone Jack Adapter 'Mir' (HID only)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"18d1:5029",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Google USB-C to 3.5mm Digital Headphone Jack Adapter 2018 'Condor'
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"18d1:5034",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Google Pixel USB-C Earbuds 'Blackbird'
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"18d1:5033",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Libratone Q Adapt In-Ear USB-C Earphones, Made for Google
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"03eb:2433",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Moshi USB-C to 3.5 mm Adapter/Charger, Made for Google
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"282b:48f0",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Moshi USB-C to 3.5 mm Adapter/Charger, Made for Google (HID only)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"282b:0026",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# AiAiAi TMA-2 C60 Cable, Made for Google
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"0572:1a08",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Apple USB-C to 3.5mm Headphone Jack Adapter
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"05ac:110a",
]
# RGB Keyboard
USB_IDS += [
# Google Prism
"18d1:5022",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# List of PCI devices (vendorid:deviceid) for which it is safe to enable
# autosuspend.
PCI_IDS = []
# Intel
PCI_IDS += [
# Host bridge
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:590c",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# i915
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:591e",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# proc_thermal
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:1903",
trivial: update tools/chromeos/gen_autosuspend_rules.py Adds CNP PCH xHCI device PCIID to udev rules
2019-10-05 04:57:46 +03:00
# SPT PCH xHCI controller
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9d2f",
trivial: update tools/chromeos/gen_autosuspend_rules.py Adds CNP PCH xHCI device PCIID to udev rules
2019-10-05 04:57:46 +03:00
# CNP PCH xHCI controller
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9ded",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# intel_pmc_core
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9d21",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# i801_smbus
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9d23",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# iwlwifi
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:095a",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# GMM
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:1911",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Thermal
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9d31",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# MME
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9d3a",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# CrOS EC
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9d4b",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# PCH SPI
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9d24",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# SATA
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:02d3",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# RAM memory
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:02ef",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# ISA bridge
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:0284",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Communication controller
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:02e0",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Network controller
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:02f0",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Serial bus controller
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:02a4",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# USB controller
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:02ed",
# JSL xHCI controller
"8086:4ded",
hwdb: update chromiumos autosuspend rules
2020-10-15 13:33:12 +03:00
# Volteer xHCI controller
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:a0ed",
# Brya xHCI controller
"8086:51ed",
# ADL-N PCH xHCI controller
"8086:54ed",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Graphics
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9b41",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# DSP
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:02f9",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Host bridge
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9b61",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# Host bridge
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:9b71",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# PCI Bridge
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:02b0",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# i915 (atlas)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:591c",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# iwlwifi (atlas)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:2526",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# i915 (kefka)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:22b1",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# proc_thermal (kefka)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:22dc",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# xchi_hdc (kefka)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:22b5",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# snd_hda (kefka)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:2284",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# pcieport (kefka)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:22c8",
"8086:22cc",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# lpc_ich (kefka)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:229c",
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# iosf_mbi_pci (kefka)
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"8086:2280",
# Host bridge (nami)
"8086:5904",
"8086:5914",
# Graphics (nami)
"8086:5906",
"8086:5917",
# ISA bridge (nami)
"8086:9d4e",
# wifi 7265 (nami)
"8086:095b",
# Graphics (brya)
"8086:46a8",
# Core 12G GNA (brya)
"8086:464f",
# PCH Shared SRAM (brya)
"8086:51ef",
# PCH eSPI (brya)
"8086:5182",
"8086:4601",
# Core 12G DTT (brya)
"8086:461d",
# Wifi (Brya)
"8086:51f0",
# PCH SPI (brya)
"8086:51a4",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# Samsung
PCI_IDS += [
# NVMe KUS030205M-B001
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"144d:a806",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
# NVMe MZVLB256HAHQ
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"144d:a808",
# NVMe MZ9LQ256HBJD-00BH1 (brya)
"144d:a809",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# Lite-on
PCI_IDS += [
# 3C07110288
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"14a4:9100",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# Seagate
PCI_IDS += [
# ZP256CM30011
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"7089:5012",
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
# Kingston
PCI_IDS += [
# RBUSNS8154P3128GJ3
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
"2646:5008",
]
# Genesys Logic
PCI_IDS += [
# SD Host Controller (brya)
"17a0:9755",
]
# Phison
PCI_IDS += [
# E13 NVMe Controller (redrix)
'1987:5013',
# E18 PCIe4 NVMe Controller (vell)
'1987:5018',
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
]
chromiumos: sync auto suspend rules with chromeos commit e348a229bacc3 Enables autosuspend for the following: - Microchip (Composite HID + CDC) - i915 - proc_thermal - xchi_hdc - snd_hda - pcieport - lpc_ich - iosf_mbi_pci - Realtek RTL8822C BT
2020-02-06 18:55:42 +03:00
# Do not edit below this line. #################################################
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
UDEV_RULE = """\
ACTION!="add", GOTO="autosuspend_end"
SUBSYSTEM!="i2c|pci|usb", GOTO="autosuspend_end"
SUBSYSTEM=="i2c", GOTO="autosuspend_i2c"
SUBSYSTEM=="pci", GOTO="autosuspend_pci"
SUBSYSTEM=="usb", GOTO="autosuspend_usb"
# I2C rules
LABEL="autosuspend_i2c"
ATTR{name}=="cyapa", ATTR{power/control}="on", GOTO="autosuspend_end"
GOTO="autosuspend_end"
# PCI rules
LABEL="autosuspend_pci"
%(pci_rules)s\
GOTO="autosuspend_end"
# USB rules
LABEL="autosuspend_usb"
%(usb_rules)s\
GOTO="autosuspend_end"
# Enable autosuspend
LABEL="autosuspend_enable"
TEST=="power/control", ATTR{power/control}="auto", GOTO="autosuspend_end"
LABEL="autosuspend_end"
"""
def main():
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
pci_rules = ""
for dev_ids in PCI_IDS:
vendor, device = dev_ids.split(":")
pci_rules += (
'ATTR{vendor}=="0x%s", ATTR{device}=="0x%s", '
'GOTO="autosuspend_enable"\n' % (vendor, device)
)
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
usb_rules = ""
for dev_ids in USB_IDS:
vid, pid = dev_ids.split(":")
usb_rules += (
'ATTR{idVendor}=="%s", ATTR{idProduct}=="%s", '
'GOTO="autosuspend_enable"\n' % (vid, pid)
)
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
print(UDEV_RULE % {"pci_rules": pci_rules, "usb_rules": usb_rules})
rules: Add automatic suspend udev rules The ChromeOS ecosystem has a large amount of testing, both automated and manual across devices including measurement of power regressions. It's safe to assume that any of these devices will handle USB auto-suspend appropriately. Use the script from ChromeOS https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/udev/gen_autosuspend_rules.py to generate udev rules at build time. This script in systemd `tools/chromeos/gen_autosuspend_rules.py` should be kept in sync with the ChromeOS version of the script. Manually added autosuspend devices should be placed in the new template `rules/61-autosuspend-manual.rules` Suggested-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
2019-09-10 00:49:35 +03:00
hwdb: update autosuspend rules ninja -C build update-hwdb-autosuspend
2023-08-16 04:08:08 +03:00
if __name__ == "__main__":
main()
Copy Permalink