Searched +full:platform +full:- +full:level (Results 1 – 25 of 197) sorted by relevance
12345678
| /Documentation/ABI/testing/ |
| D | sysfs-platform-mellanox-bootctl | 1 What: /sys/bus/platform/devices/MLNXBF04:00/lifecycle_state 6 The Life-cycle state of the SoC, which could be one of the 12 GA Non-Secured Non-Secure chip and not able to change state 16 What: /sys/bus/platform/devices/MLNXBF04:00/post_reset_wdog 25 What: /sys/bus/platform/devices/MLNXBF04:00/reset_action 39 What: /sys/bus/platform/devices/MLNXBF04:00/second_reset_action 56 What: /sys/bus/platform/devices/MLNXBF04:00/secure_boot_fuse_state 72 What: /sys/bus/platform/devices/MLNXBF04:00/bootfifo 79 What: /sys/bus/platform/devices/MLNXBF04:00/rsh_log 85 "[INFO|WARN|ERR|ASSERT ]<msg>". Log level 'INFO' is used by [all …]
|
| D | sysfs-driver-samsung-laptop | 1 What: /sys/devices/platform/samsung/performance_level 4 Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 10 will show the current performance level. Writing to the 14 - "silent" 15 - "normal" 16 - "overclock" 23 What: /sys/devices/platform/samsung/battery_life_extender 27 Description: Max battery charge level can be modified, battery cycle 29 level. 31 - 0 means normal battery mode (100% charge) [all …]
|
| D | sysfs-platform-lg-laptop | 1 What: /sys/devices/platform/lg-laptop/reader_mode 4 Contact: "Matan Ziv-Av <matan@svgalib.org> 8 What: /sys/devices/platform/lg-laptop/fn_lock 11 Contact: "Matan Ziv-Av <matan@svgalib.org> 15 What: /sys/devices/platform/lg-laptop/battery_care_limit 18 Contact: "Matan Ziv-Av <matan@svgalib.org> 21 Maximal battery charge level. Accepted values are 80 or 100. 23 What: /sys/devices/platform/lg-laptop/fan_mode 26 Contact: "Matan Ziv-Av <matan@svgalib.org> 30 What: /sys/devices/platform/lg-laptop/usb_charge [all …]
|
| D | sysfs-platform-dfl-port | 1 What: /sys/bus/platform/devices/dfl-port.0/id 5 Description: Read-only. It returns id of this port. One DFL FPGA device 9 What: /sys/bus/platform/devices/dfl-port.0/afu_id 13 Description: Read-only. User can program different PR bitstreams to FPGA 18 What: /sys/bus/platform/devices/dfl-port.0/power_state 22 Description: Read-only. It reports the APx (AFU Power) state, different APx 23 means different throttling level. When reading this file, it 24 returns "0" - Normal / "1" - AP1 / "2" - AP2 / "6" - AP6. 26 What: /sys/bus/platform/devices/dfl-port.0/ap1_event 30 Description: Read-write. Read this file for AP1 (AFU Power State 1) event. [all …]
|
| D | sysfs-driver-ufs | 3 Contact: linux-scsi@vger.kernel.org 5 This file contains the auto-hibernate idle timer setting of a 6 UFS host controller. A value of '0' means auto-hibernate is not 11 10-bit values with a power-of-ten multiplier which allows a 15 What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_type 16 What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_type 25 What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_class 26 What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_class 35 What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_sub_class 36 What: /sys/bus/platform/devices/*.ufs/device_descriptor/device_sub_class [all …]
|
| D | sysfs-driver-intc_sar | 1 What: /sys/bus/platform/devices/INTC1092:00/intc_reg 23 - The regulatory mode value has one of the above values. 24 - The default regulatory mode used in the driver is 0. 26 What: /sys/bus/platform/devices/INTC1092:00/intc_data 36 - device_mode 37 - bandtable_index 38 - antennatable_index 39 - sartable_index 44 level using the Band/Antenna/SAR table index information. 46 device-mode like laptop/tablet/clamshell etc. and the [all …]
|
| /Documentation/power/ |
| D | basic-pm-debugging.rst | 21 modes causes the PM core to skip some platform-related callbacks which on ACPI 24 "platform" mode:: 26 # echo platform > /sys/power/disk 31 Unfortunately, the "platform" mode of hibernation does not work on some systems 41 If neither "platform" nor "shutdown" hibernation mode works, you will need to 45 ---------------------------- 53 - test the freezing of processes 56 - test the freezing of processes and suspending of devices 58 platform 59 - test the freezing of processes, suspending of devices and platform [all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | riscv,imsics.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/riscv,imsics.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: RISC-V Incoming MSI Controller (IMSIC) 10 - Anup Patel <anup@brainfault.org> 13 The RISC-V advanced interrupt architecture (AIA) defines a per-CPU incoming 14 MSI controller (IMSIC) for handling MSIs in a RISC-V platform. The RISC-V 15 AIA specification can be found at https://github.com/riscv/riscv-aia. 17 The IMSIC is a per-CPU (or per-HART) device with separate interrupt file [all …]
|
| /Documentation/admin-guide/pm/ |
| D | sleep-states.rst | 1 .. SPDX-License-Identifier: GPL-2.0 13 Sleep states are global low-power states of the entire system in which user 21 Depending on its configuration and the capabilities of the platform it runs on, 28 Suspend-to-Idle 29 --------------- 31 This is a generic, pure software, light-weight variant of system suspend (also 34 I/O devices into low-power states (possibly lower-power than available in the 38 The system is woken up from this state by in-band interrupts, so theoretically 43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the 50 ------- [all …]
|
| D | intel-speed-select.rst | 1 .. SPDX-License-Identifier: GPL-2.0 14 - https://www.intel.com/content/www/us/en/architecture-and-technology/speed-select-technology-artic… 15 - https://builders.intel.com/docs/networkbuilders/intel-speed-select-technology-base-frequency-enha… 19 dynamically without pre-configuring via BIOS setup options. This dynamic 29 intel-speed-select configuration tool 32 Most Linux distribution packages may include the "intel-speed-select" tool. If not, 38 # cd tools/power/x86/intel-speed-select/ 43 ------------ 47 # intel-speed-select --help 49 The top-level help describes arguments and features. Notice that there is a [all …]
|
| D | suspend-flows.rst | 1 .. SPDX-License-Identifier: GPL-2.0 12 At least one global system-wide transition needs to be carried out for the 14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one 16 referred to as *system-wide suspend* (or simply *system suspend*) states, need 27 significant differences between the :ref:`suspend-to-idle <s2idle>` code flows 28 and the code flows related to the :ref:`suspend-to-RAM <s2ram>` and 31 The :ref:`suspend-to-RAM <s2ram>` and :ref:`standby <standby>` sleep states 32 cannot be implemented without platform support and the difference between them 33 boils down to the platform-specific actions carried out by the suspend and 34 resume hooks that need to be provided by the platform driver to make them [all …]
|
| /Documentation/devicetree/bindings/opp/ |
| D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Viresh Kumar <viresh.kumar@linaro.org> 13 Devices work at voltage-current-frequency combinations and some implementations 25 pattern: '^opp-table(-[a-z0-9]+)?$' 27 opp-shared: 36 '^opp(-?[0-9]+)*$': 39 One or more OPP nodes describing voltage-current-frequency combinations. [all …]
|
| /Documentation/process/ |
| D | maintainer-soc.rst | 1 .. SPDX-License-Identifier: GPL-2.0 8 -------- 10 The SoC subsystem is a place of aggregation for SoC-specific code. 13 * devicetrees for 32- & 64-bit ARM and RISC-V 14 * 32-bit ARM board files (arch/arm/mach*) 15 * 32- & 64-bit ARM defconfigs 16 * SoC-specific drivers across architectures, in particular for 32- & 64-bit 17 ARM, RISC-V and Loongarch 19 These "SoC-specific drivers" do not include clock, GPIO etc drivers that have 20 other top-level maintainers. The drivers/soc/ directory is generally meant [all …]
|
| /Documentation/devicetree/bindings/net/bluetooth/ |
| D | mediatek,bluetooth.txt | 13 - compatible: Must be 14 "mediatek,mt7663u-bluetooth": for MT7663U device 15 "mediatek,mt7668u-bluetooth": for MT7668U device 16 - vcc-supply: Main voltage regulator 18 If the pin controller on the platform can support both pinmux and GPIO 19 control such as the most of MediaTek platform. Please use below properties. 21 - pinctrl-names: Should be "default", "runtime" 22 - pinctrl-0: Should contain UART RXD low when the device is powered up to 24 - pinctrl-1: Should contain UART mode pin ctrl 26 Else, the pin controller on the platform only can support pinmux control and [all …]
|
| /Documentation/userspace-api/ |
| D | sysfs-platform_profile.rst | 2 Platform Profile Selection (e.g. /sys/firmware/acpi/platform_profile) 5 On modern systems the platform performance, temperature, fan and other 7 platform configuration is often automatically adjusted to the current 11 These auto platform adjustment mechanisms often can be configured with 12 one of several platform profiles, with either a bias towards low power 16 API for selecting the platform profile of these automatic mechanisms. 18 Note that this API is only for selecting the platform profile, it is 27 about any sub-optimal conditions which are impeding reaching the requested 28 performance level. 33 gets a consistent experience the sysfs-platform_profile ABI document defines [all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-backlight | 9 - 0 (FB_BLANK_UNBLANK) : power on. 10 - 4 (FB_BLANK_POWERDOWN) : power off 20 show the brightness level stored in the driver, which 47 "platform": The driver uses a platform-specific interface 52 control should be preferred to platform control should 56 backlight state. Platform interfaces are mostly a 57 holdover from pre-standardisation of firmware
|
| /Documentation/devicetree/bindings/sound/ |
| D | mediatek,mt8365-mt6357.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mediatek,mt8365-mt6357.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Alexandre Mergnat <amergnat@baylibre.com> 14 const: mediatek,mt8365-mt6357 16 pinctrl-names: 19 - const: default 20 - const: dmic 21 - const: miso_off [all …]
|
| D | mediatek,mt8188-mt6359.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/sound/mediatek,mt8188-mt6359.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Trevor Wu <trevor.wu@mediatek.com> 13 - $ref: sound-card-common.yaml# 18 - mediatek,mt8188-es8326 19 - mediatek,mt8188-mt6359-evb 20 - mediatek,mt8188-nau8825 21 - mediatek,mt8188-rt5682s [all …]
|
| /Documentation/devicetree/bindings/ |
| D | jailhouse.txt | 1 Jailhouse non-root cell device tree bindings 2 -------------------------------------------- 4 When running in a non-root Jailhouse cell (partition), the device tree of this 5 platform shall have a top-level "hypervisor" node with the following 8 - compatible = "jailhouse,cell"
|
| /Documentation/devicetree/bindings/arm/ |
| D | vexpress-scc.txt | 2 ----------------------------------------------------- 4 Test chips for ARM Versatile Express platform implement SCC (Serial 11 like platform configuration control and power management. 15 - compatible value: "arm,vexpress-scc,<model>", "arm,vexpress-scc"; 18 eg. for Coretile Express A15x2 A7x3 (V2P-CA15_A7): 19 compatible = "arm,vexpress-scc,v2p-ca15_a7", "arm,vexpress-scc"; 23 - reg: when the SCC is memory mapped, physical address and size of the 25 - interrupts: when the SCC can generate a system-level interrupt 30 compatible = "arm,vexpress-scc,v2p-ca15_a7", "arm,vexpress-scc";
|
| /Documentation/admin-guide/laptops/ |
| D | lg-laptop.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 7 By Matan Ziv-Av <matan@svgalib.org> 11 ------- 15 - FN-F1 (LG control panel) - Generates F15 16 - FN-F5 (Touchpad toggle) - Generates F21 17 - FN-F6 (Airplane mode) - Generates RFKILL 18 - FN-F9 (Reader mode) - Generates F14 24 ----------- 26 Writing 0/1 to /sys/devices/platform/lg-laptop/reader_mode disables/enables 32 ------- [all …]
|
| /Documentation/arch/x86/ |
| D | intel_txt.rst | 6 Technology (Intel(R) TXT), defines platform-level enhancements that 13 - Provides dynamic root of trust for measurement (DRTM) 14 - Data protection in case of improper shutdown 15 - Measurement and verification of launched environment 18 non-vPro systems. It is currently available on desktop systems 30 - LinuxTAG 2008: 31 http://www.linuxtag.org/2008/en/conf/events/vp-donnerstag.html 33 - TRUST2008: 34 http://www.trust-conference.eu/downloads/Keynote-Speakers/ 35 3_David-Grawrock_The-Front-Door-of-Trusted-Computing.pdf [all …]
|
| /Documentation/sound/soc/ |
| D | overview.rst | 6 provide better ALSA support for embedded system-on-chip processors (e.g. 9 had some limitations:- 12 CPU. This is not ideal and leads to code duplication - for example, 18 machine specific code to re-route audio, enable amps, etc., after such an 31 features :- 54 multiple re-usable component drivers :- 56 * Codec class drivers: The codec class driver is platform independent and 62 * Platform class drivers: The platform class driver includes the audio DMA 64 and any audio DSP drivers for that platform. 69 machine level audio events (e.g. turning on an amp at start of playback).
|
| /Documentation/scsi/ |
| D | scsi.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 https://www.tldp.org/HOWTO/SCSI-2.4-HOWTO . The LDP has single 18 The scsi-core (also known as the "mid level") contains the core of SCSI 27 The individual upper and lower level drivers can be loaded in any order 29 as a module). The disk driver (sd_mod.o), CD-ROM driver (sr_mod.o), 31 level drivers to support the various assorted devices which can be 36 The lower level drivers are the ones that support the individual cards that 37 are supported for the hardware platform that you are running under. Those 40 Adaptec. Almost all lower level drivers can be built either as modules or
|
| /Documentation/virt/gunyah/ |
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 message-queue 12 Gunyah is a Type-1 hypervisor which is independent of any OS kernel, and runs in 13 a more privileged CPU level (EL2 on Aarch64). It does not depend on a less 15 security and can support a much smaller trusted computing base than a Type-2 19 https://github.com/quic/gunyah-hypervisor. 23 - Scheduling: 25 A scheduler for virtual CPUs (vCPUs) on physical CPUs enables time-sharing 30 its own. The default is a real-time priority with round-robin scheduler. 31 2. "Proxy" scheduling in which an owner-VM can donate the remainder of its [all …]
|
12345678