Home
last modified time | relevance | path

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

12345678910>>...15

/linux/Documentation/devicetree/bindings/leds/
H A 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/arch/mips/boot/dts/brcm/
H A 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/drivers/leds/trigger/
H A 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/include/dt-bindings/clock/
H A 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 …]
H A 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/Documentation/ABI/testing/
H A Dsysfs-platform-dell-privacy-wmi1 What: /sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919[-X]/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_support…
37 What: /sys/bus/wmi/devices/6932965F-1671-4CEB-B988-D3AB0A901919[-X]/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…
H A Dsysfs-class-led-trigger-netdev4 Contact: linux-leds@vger.kernel.org
11 Contact: linux-leds@vger.kernel.org
24 Contact: linux-leds@vger.kernel.org
38 Contact: linux-leds@vger.kernel.org
47 When offloaded is true, the blink interval is controlled by
48 hardware and won't reflect the value set in interval.
53 Contact: linux-leds@vger.kernel.org
62 When offloaded is true, the blink interval is controlled by
63 hardware and won't reflect the value set in interval.
68 Contact: linux-leds@vger.kernel.org
[all …]
/linux/drivers/gpu/drm/msm/disp/dpu1/
H A Ddpu_hw_ctl.h1 /* SPDX-License-Identifier: GPL-2.0-only */
2 /* Copyright (c) 2015-2018, The Linux Foundation. All rights reserved.
3 * Copyright (c) 2022-2024 Qualcomm Innovation Center, Inc. All rights reserved.
26 * struct dpu_hw_stage_cfg - blending stage cfg
45 * @stream_sel: Stream selection for multi-stream interfaces
63 * struct dpu_hw_ctl_ops - Interface to the wb Hw driver functions
68 * @trigger_start: kickoff hw operation for Sw controlled interfaces
69 * DSI cmd mode and WB interface are SW controlled
83 * controlled interfaces: DSI cmd mode and WB interface
84 * are SW controlled
[all …]
/linux/Documentation/devicetree/bindings/regulator/
H A 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,mt6893-dvfsrc-regulator
21 - mediatek,mt8183-dvfsrc-regulator
[all …]
/linux/drivers/clk/meson/
H A Dclk-regmap.h1 /* SPDX-License-Identifier: GPL-2.0 */
11 #include <linux/clk-provider.h>
15 * struct clk_regmap - regmap backed clock
17 * @hw: handle between common and hardware-specific interfaces
21 * Clock which is controlled by regmap backed registers. The actual type of
22 * of the clock is controlled by the clock_ops and data.
39 * struct clk_regmap_gate_data - regmap backed gate specific data
43 * @flags: hardware-specific flags
57 return (struct clk_regmap_gate_data *)clk->data; in clk_get_regmap_gate_data()
64 * struct clk_regmap_div_data - regmap backed adjustable divider specific data
[all …]
/linux/include/uapi/linux/
H A 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/Documentation/userspace-api/media/v4l/
H A Dselection-api-configuration.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
10 settings and hardware limits.
12 Video hardware can have various cropping, composing and scaling
21 :ref:`constraint flags <v4l2-selection-flags>`.
27 See figure :ref:`sel-targets-capture` for examples of the selection
42 according to hardware limitations.
56 The part of a buffer into which the image is inserted by the hardware is
57 controlled by the ``V4L2_SEL_TGT_COMPOSE`` target. The rectangle's
62 adjustments according to hardware limitations. The application can
64 :ref:`constraint flags <v4l2-selection-flags>`.
[all …]
H A 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/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A Dmemory.json172 …y accesses with at least 1 store operation. This PEBS event is the precisely-distributed (PDist) t…
199 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
205 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
210 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
216 …on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode. A…
243 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
249 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
265 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
271 …on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode. A…
298 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
[all …]
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A Dmemory.json172 …y accesses with at least 1 store operation. This PEBS event is the precisely-distributed (PDist) t…
199 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
205 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
210 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
216 …on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode. A…
243 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
249 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
265 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
271 …on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode. A…
298 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
[all …]
/linux/Documentation/leds/
H A 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/drivers/net/dsa/ocelot/
H A 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/drivers/reset/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
12 via GPIOs or SoC-internal reset controller modules.
82 specific to ESWIN SoCs and should only be enabled if using such hardware.
93 such hardware.
116 GPIOs. Typically for OF platforms this driver expects "reset-gpios"
119 If compiled as module, it will be called reset-gpio.
168 Support for the Canaan Kendryte K210 RISC-V SoC reset controller.
177 Support for the Canaan Kendryte K230 RISC-V SoC reset controller.
254 Raspberry Pi 4's co-processor controls some of the board's HW
257 interfacing with RPi4's co-processor and model these firmware
[all …]
/linux/Documentation/networking/
H A 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 …]
/linux/Documentation/hwmon/
H A 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 …]
H A Dgigabyte_waterforce.rst1 .. SPDX-License-Identifier: GPL-2.0-or-later
15 -----------
17 This driver enables hardware monitoring support for the listed Gigabyte Waterforce
18 all-in-one CPU liquid coolers. Available sensors are pump and fan speed in RPM, as
21 Attaching a fan is optional and allows it to be controlled from the device. If
22 it's not connected, the fan-related sensors will report zeroes.
25 be controlled through userspace tools.
28 -----------
34 -------------
43 ---------------
/linux/arch/arm/boot/dts/nxp/imx/
H A Dimx6qdl-dhcom-drc02.dtsi1 // SPDX-License-Identifier: GPL-2.0+
8 stdout-path = "serial0:115200n8";
13 * Special SoM hardware required which uses the pins from micro SD card. The
25 * NOTE: On DRC02, the RS485_RX_En is controlled by a separate
30 rs485-rx-en-hog {
31 gpio-hog;
33 line-name = "rs485-rx-en";
34 output-low;
39 gpio-line-names =
43 "", "", "", "DRC02-In1", "", "", "", "";
[all …]
/linux/Documentation/arch/arm64/
H A Dlegacy_instructions.rst9 the instruction execution in hardware.
11 The emulation mode can be controlled by writing to sysctl nodes
13 behaviours and the corresponding values of the sysctl nodes -
29 * Hardware Execution
33 enabling/disabling of hardware support for the execution of these
34 instructions. Using hardware execution generally provides better
46 -----------------------------
66 for this feature to be enabled. If a new CPU - which doesn't support mixed
67 endian - is hotplugged in after this feature has been enabled, there could
/linux/drivers/net/mdio/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
41 tristate "APM X-Gene SoC MDIO bus controller"
45 APM X-Gene SoC's.
54 third revision of the ASPEED MDIO register interface - the first two
83 This hardware can be found in the Broadcom GENET Ethernet MAC
91 tristate "GPIO lib-based bitbanged MDIO buses"
95 Supports GPIO lib-based MDIO busses.
98 will be called mdio-gpio.
151 tristate "PIC64-HPSC/HX MDIO interface support"
155 This driver supports the MDIO interface found on the PIC64-HPSC/HX
[all …]
/linux/drivers/acpi/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
20 Linux requires an ACPI-compliant platform (hardware/firmware),
21 and assumes the presence of OS-directed configuration and power
27 the Plug-and-Play BIOS specification (PnP BIOS), the
37 ACPI is an open industry specification originally co-developed by
38 Hewlett-Packard, Intel, Microsoft, Phoenix, and Toshiba. Currently,
73 Enable in-kernel debugging of AML facilities: statistics,
131 This option enables a DMI-based quirk for the above Dell machine (so
193 performs user-defined actions such as shutting down the system.
194 This is necessary for software-controlled poweroff.
[all …]

12345678910>>...15