Home
last modified time | relevance | path

Searched +full:hardware +full:- +full:controlled (Results 1 – 25 of 606) sorted by relevance

12345678910>>...25

/linux-6.12.1/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/leds/leds-bcm6328.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Álvaro Fernández Rojas <noltari@gmail.com>
14 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
16 controller), which can either be controlled by software (exporting the 74x164
17 as spi-gpio. See
18 Documentation/devicetree/bindings/gpio/fairchild,74hc595.yaml), or by hardware
20 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
[all …]
/linux-6.12.1/arch/mips/boot/dts/brcm/
Dbcm63268-comtrend-vr-3032u.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
7 compatible = "comtrend,vr-3032u", "brcm,bcm63268";
8 model = "Comtrend VR-3032u";
17 stdout-path = &uart0;
23 brcm,serial-leds;
24 brcm,serial-dat-low;
25 brcm,serial-shift-inv;
29 brcm,hardware-controlled;
30 brcm,link-signal-sources = <0>;
[all …]
/linux-6.12.1/drivers/leds/trigger/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
15 This allows LEDs to be controlled by a programmable timer
16 via sysfs. Some LED hardware can be programmed to start
18 For more details read Documentation/leds/leds-class.rst.
23 tristate "LED One-shot Trigger"
25 This allows LEDs to blink in one-shot pulses with parameters
26 controlled via sysfs. It's useful to notify the user on
39 This allows LEDs to be controlled by disk activity.
46 This allows LEDs to be controlled by MTD activity.
52 This allows LEDs to be controlled by a CPU load average.
[all …]
/linux-6.12.1/drivers/gpu/drm/msm/disp/dpu1/
Ddpu_hw_ctl.h1 /* SPDX-License-Identifier: GPL-2.0-only */
2 /* Copyright (c) 2015-2018, The Linux Foundation. All rights reserved.
26 * struct dpu_hw_stage_cfg - blending stage cfg
43 * @stream_sel: Stream selection for multi-stream interfaces
58 * struct dpu_hw_ctl_ops - Interface to the wb Hw driver functions
63 * kickoff hw operation for Sw controlled interfaces
64 * DSI cmd mode and WB interface are SW controlled
78 * controlled interfaces: DSI cmd mode and WB interface
79 * are SW controlled
86 * No effect on hardware.
[all …]
/linux-6.12.1/Documentation/devicetree/bindings/thermal/
Drockchip-thermal.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/thermal/rockchip-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Heiko Stuebner <heiko@sntech.de>
12 $ref: thermal-sensor.yaml#
17 - rockchip,px30-tsadc
18 - rockchip,rk3228-tsadc
19 - rockchip,rk3288-tsadc
20 - rockchip,rk3328-tsadc
[all …]
/linux-6.12.1/include/dt-bindings/clock/
Dtegra186-clock.h1 /* SPDX-License-Identifier: GPL-2.0 */
376 /** @brief output branch of PLL_C for ISP, controlled by gate CLK_ENB_PLLC_OUT_ISP */
378 /** @brief output branch of PLL_C for VI, controlled by gate CLK_ENB_PLLC_OUT_VE */
380 /** @brief output branch of PLL_C for AON domain, controlled by gate CLK_ENB_PLLC_OUT_AON */
384 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_I2S2 */
386 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_I2S3 */
388 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SPDF_IN */
398 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SPI1 */
400 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_ISP */
402 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_VI */
[all …]
Dtegra234-clock.h1 /* SPDX-License-Identifier: GPL-2.0 */
2 /* Copyright (c) 2018-2022, NVIDIA CORPORATION. All rights reserved. */
12 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_ACTMON */
18 /** output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_AHUB */
22 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_APE */
24 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_AUD_MCLK */
26 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_AXI_CBB */
28 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_CAN1 */
32 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_CAN2 */
38 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_DMIC1 */
[all …]
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-platform-dell-privacy-wmi1 What: /sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supported_type
6 Display which dell hardware level privacy devices are supported
10 The supported hardware privacy devices are:
14 Identifies the local microphone can be muted by hardware, no applications
18 Identifies camera shutter controlled by hardware, which is a micromechanical
32 …# cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_supporte…
37 What: /sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_state
49 Identifies the local microphone can be muted by hardware, no applications
53 Identifies camera shutter controlled by hardware, which is a micromechanical
69 …# cat /sys/bus/wmi/drivers/dell-privacy/6932965F-1671-4CEB-B988-D3AB0A901919/dell_privacy_current_…
/linux-6.12.1/Documentation/devicetree/bindings/regulator/
Dmediatek,mt6873-dvfsrc-regulator.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/regulator/mediatek,mt6873-dvfsrc-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MediaTek DVFSRC-controlled Regulators
11 are controlled with votes to the DVFSRC hardware.
14 - AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
19 - mediatek,mt6873-dvfsrc-regulator
20 - mediatek,mt8183-dvfsrc-regulator
21 - mediatek,mt8192-dvfsrc-regulator
[all …]
/linux-6.12.1/drivers/mux/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
22 be called mux-adg792a.
32 be called mux-adgs1408.
35 tristate "GPIO-controlled Multiplexer"
38 GPIO-controlled Multiplexer controller.
42 states. The GPIO pins can be connected (by the hardware) to several
46 be called mux-gpio.
49 tristate "MMIO/Regmap register bitfield-controlled Multiplexer"
52 MMIO/Regmap register bitfield-controlled Multiplexer controller.
59 be called mux-mmio.
/linux-6.12.1/include/uapi/sound/
Dfirewire.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
30 unsigned int notification; /* DICE-specific bits */
33 #define SND_EFW_TRANSACTION_USER_SEQNUM_MAX ((__u32)((__u16)~0) - 1)
51 __u32 message; /* Digi00x-specific message */
56 __u32 message; /* MOTU-specific bits. */
77 * struct snd_firewire_event_ff400_message - the container for message from Fireface 400 when
78 * operating hardware knob.
82 * @messages.message: The messages expressing hardware knob operation.
89 * The structure expresses message transmitted by Fireface 400 when operating hardware knob.
139 * Returns -EBUSY if the driver is already streaming.
[all …]
/linux-6.12.1/include/uapi/linux/
Dvfio_ccw.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
3 * Interfaces for vfio-ccw
28 * Note: this is controlled by a capability
38 * Used for processing commands that read the subchannel-information block
39 * Reading this region triggers a stsch() to hardware
40 * Note: this is controlled by a capability
49 * Note: this is controlled by a capability
/linux-6.12.1/drivers/clk/meson/
Dclk-regmap.h1 /* SPDX-License-Identifier: GPL-2.0 */
10 #include <linux/clk-provider.h>
14 * struct clk_regmap - regmap backed clock
16 * @hw: handle between common and hardware-specific interfaces
20 * Clock which is controlled by regmap backed registers. The actual type of
21 * of the clock is controlled by the clock_ops and data.
35 * struct clk_regmap_gate_data - regmap backed gate specific data
39 * @flags: hardware-specific flags
53 return (struct clk_regmap_gate_data *)clk->data; in clk_get_regmap_gate_data()
60 * struct clk_regmap_div_data - regmap backed adjustable divider specific data
[all …]
/linux-6.12.1/Documentation/hwmon/
Dasus_rog_ryujin.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
13 -----------
15 This driver enables hardware monitoring support for the listed ASUS ROG RYUJIN
16 all-in-one CPU liquid coolers. Available sensors are pump, internal and external
20 controlled from the device. If not connected, the fan-related sensors will
21 report zeroes. The controller is a separate hardware unit that comes bundled
25 be controlled through userspace tools.
28 -----------
34 -------------
Dlm85.rst79 - Philip Pokorny <ppokorny@penguincomputing.com>,
80 - Frodo Looijaard <frodol@dds.nl>,
81 - Richard Barrington <rich_b_nz@clear.net.nz>,
82 - Margit Schubert-While <margitsw@t-online.de>,
83 - Justin Thiessen <jthiessen@penguincomputing.com>
86 -----------
92 The LM85 uses the 2-wire interface compatible with the SMBUS 2.0
94 temperatures and five (5) voltages. It has four (4) 16-bit counters for
127 ----------------
133 for 3-wire and 2-wire mode. For this reason, the 2-wire fan modes are not
[all …]
/linux-6.12.1/tools/perf/pmu-events/arch/x86/sapphirerapids/
Dother.json39 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
49 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
79 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
89 … Sub NUMA Cluster(SNC) Mode. In SNC Mode counts PMM accesses that are controlled by the close or …
129 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
159 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
169 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
179 …"BriefDescription": "Counts data load hardware prefetch requests to the L1 data cache that have an…
189 …"BriefDescription": "Counts hardware prefetches (which bring data to L2) that have any type of res…
199 … "BriefDescription": "Counts hardware prefetches to the L3 only that have any type of response.",
[all …]
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dselection-api-configuration.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
9 settings and hardware limits.
11 Video hardware can have various cropping, composing and scaling
20 :ref:`constraint flags <v4l2-selection-flags>`.
26 See figure :ref:`sel-targets-capture` for examples of the selection
41 according to hardware limitations.
55 The part of a buffer into which the image is inserted by the hardware is
56 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's
61 adjustments according to hardware limitations. The application can
63 :ref:`constraint flags <v4l2-selection-flags>`.
[all …]
Dopen.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
12 Controlling a hardware peripheral via V4L2
15 Hardware that is supported using the V4L2 uAPI often consists of multiple
22 the hardware, which may also expose device nodes, called V4L2 sub-devices.
24 When such V4L2 sub-devices are exposed, they allow controlling those
25 other hardware components - usually connected via a serial bus (like
26 I²C, SMBus or SPI). Depending on the bridge driver, those sub-devices
27 can be controlled indirectly via the bridge driver or explicitly via
29 :ref:`V4L2 sub-devices <subdev>`.
32 :ref:`Media Controller <media_controller>` are called **MC-centric**
[all …]
/linux-6.12.1/Documentation/leds/
Dleds-lm3556.rst6 1.5 A Synchronous Boost LED Flash Driver w/ High-Side Current Source
10 - Daniel Jeong
12 Contact:Daniel Jeong(daniel.jeong-at-ti.com, gshark.jeong-at-gmail.com)
15 -----------
26 LM3556 Flash can be controlled through /sys/class/leds/flash/brightness file
29 ON / OFF will be controlled by STROBE pin.
52 hardware TORCH input.
54 LM3556 torch can be controlled through /sys/class/leds/torch/brightness file.
56 and ON / OFF will be controlled by TORCH pin.
78 and 4 patterns are pre-defined in indicator_pattern array.
[all …]
/linux-6.12.1/drivers/gpio/
Dgpio-stp-xway.c1 // SPDX-License-Identifier: GPL-2.0-only
22 * 3 groups of 8 bits can be driven. The hardware is able to allow the DSL modem
37 /* software or hardware update select bit */
85 u8 groups; /* we can drive 1-3 groups of 8bit each */
95 * xway_stp_get() - gpio_chip->get - get gpios.
105 return (xway_stp_r32(chip->virt, XWAY_STP_CPU0) & BIT(gpio)); in xway_stp_get()
109 * xway_stp_set() - gpio_chip->set - set gpios.
121 chip->shadow |= BIT(gpio); in xway_stp_set()
123 chip->shadow &= ~BIT(gpio); in xway_stp_set()
124 xway_stp_w32(chip->virt, chip->shadow, XWAY_STP_CPU0); in xway_stp_set()
[all …]
/linux-6.12.1/tools/perf/pmu-events/arch/x86/emeraldrapids/
Dother.json39 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
49 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
79 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
99 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
129 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
139 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
149 …"BriefDescription": "Counts data load hardware prefetch requests to the L1 data cache that have an…
159 …"BriefDescription": "Counts hardware prefetches (which bring data to L2) that have any type of res…
169 … "BriefDescription": "Counts hardware prefetches to the L3 only that have any type of response.",
179 …"BriefDescription": "Counts hardware prefetches to the L3 only that were not supplied by the local…
[all …]
/linux-6.12.1/arch/s390/kvm/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
21 prompt "Kernel-based Virtual Machine (KVM) support"
38 This module provides access to the hardware capabilities through
47 bool "Userspace controlled virtual machines"
51 controlled by userspace.
/linux-6.12.1/drivers/net/dsa/ocelot/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
6 register-compatible with Ocelot and that perform I/O to their host
8 Its name comes from the first hardware chip to make use of it
24 when controlled through SPI.
26 The Ocelot switch family is a set of multi-port networking chips. All
27 of these chips have the ability to be controlled externally through
/linux-6.12.1/tools/perf/pmu-events/arch/x86/icelakex/
Dother.json3 … where the core was running in a manner where Turbo may be clipped to the Non-AVX turbo schedule.",
7 …s running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, AVX…
16 … running with power-delivery for license level 1. This includes high current AVX 256-bit instruct…
25 …running with power-delivery for license level 2 (introduced in Skylake Server microarchitecture). …
113 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
123 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
153 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
163 …luster(SNC) Mode. In SNC Mode counts only those PMM accesses that are controlled by the close SNC…
203 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
213 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
[all …]
/linux-6.12.1/Documentation/networking/
Drepresentors.rst1 .. SPDX-License-Identifier: GPL-2.0
9 used to control internal switching on SmartNICs. For the closely-related port
10 representors on physical (multi-port) switches, see
14 ----------
16 Since the mid-2010s, network cards have started offering more complex
17 virtualisation capabilities than the legacy SR-IOV approach (with its simple
18 MAC/VLAN-based switching model) can support. This led to a desire to offload
19 software-defined networks (such as OpenVSwitch) to these NICs to specify the
24 virtual switches and IOV devices. Just as each physical port of a Linux-
25 controlled switch has a separate netdev, so does each virtual port of a virtual
[all …]

12345678910>>...25