Searched +full:platform +full:- +full:level (Results 1 – 25 of 1013) sorted by relevance
12345678910>>...41
/linux-5.10/include/linux/mtd/ |
D | platnand.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 3 * Copyright © 2000-2010 David Woodhouse <dwmw2@infradead.org> 7 * Contains all platform NAND related definitions. 18 * struct platform_nand_chip - chip level device structure 26 * @part_probe_types: NULL-terminated array of probe types 40 * struct platform_nand_ctrl - controller level device structure 41 * @probe: platform specific function to probe/setup hardware 42 * @remove: platform specific function to remove/teardown hardware 43 * @dev_ready: platform specific function to read ready/busy pin 44 * @select_chip: platform specific chip select function [all …]
|
/linux-5.10/Documentation/ABI/testing/ |
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-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 24 What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_class 33 What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/device_sub_class 42 What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/protocol 52 What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_luns 61 What: /sys/bus/platform/drivers/ufshcd/*/device_descriptor/number_of_wluns [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> 20 Maximal battery charge level. Accepted values are 80 or 100. 22 What: /sys/devices/platform/lg-laptop/fan_mode 25 Contact: "Matan Ziv-Av <matan@svgalib.org> 29 What: /sys/devices/platform/lg-laptop/usb_charge [all …]
|
/linux-5.10/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 …]
|
/linux-5.10/arch/hexagon/kernel/ |
D | irq_cpu.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * First-level interrupt controller model for Hexagon. 5 * Copyright (c) 2010-2011, The Linux Foundation. All rights reserved. 14 __vmintop_locdis((long) data->irq); in mask_irq() 24 __vmintop_locen((long) data->irq); in unmask_irq() 30 __vmintop_globen((long) data->irq); in eoi_irq() 34 * if this is absent, then an -ENXIO error is returned to the 54 * The hexagon core comes with a first-level interrupt controller 57 * macro cells that provide one or more second-level interrupt 58 * controllers that are cascaded into one or more of the first-level [all …]
|
/linux-5.10/arch/arm/mach-s3c/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 5 source "arch/arm/mach-s3c/Kconfig.s3c24xx" 6 source "arch/arm/mach-s3c/Kconfig.s3c64xx" 16 Base platform code for all Samsung SoC based systems 23 Base platform power management code for samsung code 33 int "S3C UART to use for low-level messages" 37 Choice of which UART port to use for the low-level messages, 40 must have been initialised by the boot-loader before use. 47 Samsung platforms, including static platform devices, legacy 68 chip tracking if the platform requires it. [all …]
|
/linux-5.10/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 …]
|
/linux-5.10/arch/arm/ |
D | Kconfig.debug | 1 # SPDX-License-Identifier: GPL-2.0 44 once the kernel has booted up - it's a one time check. 96 1 - undefined instruction events 97 2 - system calls 98 4 - invalid data aborts 99 8 - SIGSEGV faults 100 16 - SIGBUS faults 104 bool "Kernel low-level debugging functions (read help!)" 113 image on a different platform *will not work*, so this option should 117 prompt "Kernel low-level debugging port" [all …]
|
/linux-5.10/arch/powerpc/include/asm/ |
D | pmac_pfunc.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 20 * Arguments to a platform function call. 42 * ends with an end() call. This allows the low level driver to implement 43 * locking policy or per-function instance data. 116 * Drivers who expose platform functions register at init time, this 117 * causes the platform functions for that device node to be parsed in 119 * partially public so a driver can walk the list of platform functions 135 /* The name is the "xxx" in "platform-do-xxx", this is how 136 * platform functions are identified by this code. Some functions 160 * For platform functions that are interrupts, one can register [all …]
|
/linux-5.10/drivers/platform/chrome/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 3 # Platform support for Chrome OS hardware (Chromebooks and Chromeboxes) 7 bool "Platform support for Chrome hardware" 10 Say Y here to get to see options for platform support for 36 The range of memory used is 0xf00000-0x1000000, traditionally 72 EC through an I2C bus. This uses a simple byte-level protocol with 81 through rpmsg. This uses a simple byte-level protocol with a 82 checksum. Also since there's no addition EC-to-host interrupt, this 95 ISH Transport protocol (ISH-TP). This uses a simple byte-level 107 through a SPI bus, using a byte-level protocol. Since the EC's [all …]
|
/linux-5.10/arch/arm/include/asm/ |
D | mcpm.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 6 * Copyright: (C) 2012-2013 Linaro Limited 33 * Platform specific code should use this symbol to set up secondary 40 * branch once it is ready to re-enter the kernel using ptr, or NULL if it 59 * mcpm_is_available - returns whether MCPM is initialized and available 66 * mcpm_cpu_power_up - make given CPU in given cluster runable 87 * mcpm_cpu_power_down - power the calling CPU down 92 * then the cluster is prepared for power-down too. 96 * On success this does not return. Re-entry in the kernel is expected 103 * mcpm_wait_for_cpu_powerdown() subsequently returns non-zero for the [all …]
|
/linux-5.10/include/linux/ |
D | platform_device.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 3 * platform_device.h - generic, centralized driver model 5 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org> 7 * See Documentation/driver-api/driver-model/ for more information. 15 #define PLATFORM_DEVID_NONE (-1) 16 #define PLATFORM_DEVID_AUTO (-2) 42 #define platform_get_device_id(pdev) ((pdev)->id_entry) 44 #define dev_is_platform(dev) ((dev)->bus == &platform_bus_type) 102 * platform_device_register_resndata - add a platform-level device with 103 * resources and platform-specific data [all …]
|
/linux-5.10/drivers/acpi/dptf/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 4 bool "Intel DPTF (Dynamic Platform and Thermal Framework) Support" 7 Intel Dynamic Platform and Thermal Framework (DPTF) is a platform 8 level hardware/software solution for power and thermal management. 15 <https://01.org/intel%C2%AE-dynamic-platform-and-thermal-framework-dptf-chromium-os/overview> 20 tristate "Platform Power DPTF Participant" 23 This driver adds support for Dynamic Platform and Thermal Framework 24 (DPTF) Platform Power Participant device (INT3407) support. 25 This participant is responsible for exposing platform telemetry: 39 This driver adds support for Dynamic Platform and Thermal Framework
|
/linux-5.10/Documentation/devicetree/bindings/opp/ |
D | opp.txt | 2 ---------------------------------------------------- 4 Devices work at voltage-current-frequency combinations and some implementations 13 Binding 1: operating-points 16 This binding only supports voltage-frequency pairs. 19 - operating-points: An array of 2-tuples items, and each item consists 20 of frequency and voltage like <freq-kHz vol-uV>. 27 compatible = "arm,cortex-a9"; 29 next-level-cache = <&L2>; 30 operating-points = < 39 Binding 2: operating-points-v2 [all …]
|
/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
D | sifive,plic-1.0.0.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 4 --- 5 $id: http://devicetree.org/schemas/interrupt-controller/sifive,plic-1.0.0.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 8 title: SiFive Platform-Level Interrupt Controller (PLIC) 11 SiFive SOCs include an implementation of the Platform-Level Interrupt Controller 12 (PLIC) high-level specification in the RISC-V Privileged Architecture 17 in an 4 core system with 2-way SMT, you have 8 harts and probably at least two 20 Each interrupt can be enabled on per-context basis. Any context can claim 28 While the PLIC supports both edge-triggered and level-triggered interrupts, [all …]
|
/linux-5.10/drivers/base/ |
D | platform.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * platform.c - platform 'pseudo' bus for legacy devices 5 * Copyright (c) 2002-3 Patrick Mochel 6 * Copyright (c) 2002-3 Open Source Development Labs 8 * Please see Documentation/driver-api/driver-model/platform.rst for more 18 #include <linux/dma-mapping.h> 26 #include <linux/clk/clk-conf.h> 39 .init_name = "platform", 44 * platform_get_resource - get a resource for a device 45 * @dev: platform device [all …]
|
/linux-5.10/Documentation/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 …]
|
/linux-5.10/Documentation/devicetree/ |
D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0 44 ---------- 56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit 57 and 64-bit support, the decision was made to require DT support on all 61 blob without requiring a real Open Firmware implementation. U-Boot, 66 existing non-DT aware firmware. 71 out of mainline (nios) have some level of DT support. 74 ------------- 78 2.1 High Level View 79 ------------------- [all …]
|
/linux-5.10/arch/sparc/kernel/ |
D | mdesc.c | 1 // SPDX-License-Identifier: GPL-2.0 26 /* Unlike the OBP device tree, the machine description is a full-on 106 {"virtual-device-port", get_vdev_port_node_info, 108 {"domain-services-port", get_ds_port_node_info, 152 BUG_ON(((unsigned long)&hp->mdesc) & (16UL - 1)); in mdesc_handle_init() 155 INIT_LIST_HEAD(&hp->list); in mdesc_handle_init() 156 hp->self_base = base; in mdesc_handle_init() 157 refcount_set(&hp->refcnt, 1); in mdesc_handle_init() 158 hp->handle_size = handle_size; in mdesc_handle_init() 167 handle_size = (sizeof(struct mdesc_handle) - in mdesc_memblock_alloc() [all …]
|
/linux-5.10/arch/arc/include/asm/ |
D | mach_desc.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */ 12 * struct machine_desc - Board specific callbacks, called from ARC common code 14 * a multi-platform kernel builds with array of such descriptors. 25 * @init_machine: arch initcall level callback (e.g. populate static 26 * platform devices or parse Devicetree) 27 * @init_late: Late initcall level callback 41 * Current machine - only accessible during boot. 46 * Machine type table - also only accessible during boot
|
/linux-5.10/Documentation/driver-api/gpio/ |
D | legacy.rst | 13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled 21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every 22 non-dedicated pin can be configured as a GPIO; and most chips have at least 27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS 32 - Output values are writable (high=1, low=0). Some chips also have 34 value might be driven ... supporting "wire-OR" and similar schemes 37 - Input values are likewise readable (1, 0). Some chips support readback 38 of pins configured as "output", which is very useful in such "wire-OR" 40 input de-glitch/debounce logic, sometimes with software controls. 42 - Inputs can often be used as IRQ signals, often edge triggered but [all …]
|
/linux-5.10/Documentation/devicetree/bindings/net/ |
D | mediatek-bluetooth.txt | 1 MediaTek SoC built-in Bluetooth Devices 5 child node of the serial node with BTIF. The dt-bindings details for BTIF 10 - compatible: Must be 11 "mediatek,mt7622-bluetooth": for MT7622 SoC 12 - clocks: Should be the clock specifiers corresponding to the entry in 13 clock-names property. 14 - clock-names: Should contain "ref" entries. 15 - power-domains: Phandle to the power domain that the device is part of 20 compatible = "mediatek,mt7622-btif", 21 "mediatek,mtk-btif"; [all …]
|
/linux-5.10/security/integrity/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 11 (EVM), IMA-appraisal extension, digital signature verification 27 of the different use cases - evm, ima, and modules. 56 bool "Provide keyring for platform/firmware trusted keys" 60 Provide a separate, distinct keyring for platform trusted keys, which 62 provided by the platform for verifying the kexec'ed kerned image 76 bool "Enable loading of platform and blacklisted keys for POWER" 81 Enable loading of keys to the .platform keyring and blacklisted 91 controls the level of integrity auditing messages. 92 0 - basic integrity auditing messages (default) [all …]
|
12345678910>>...41