Home
last modified time | relevance | path

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

12345678910>>...29

/openbmc/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 …]
/openbmc/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 …]
/openbmc/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 …]
/openbmc/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.
26 * struct dpu_hw_stage_cfg - blending stage cfg
42 * @stream_sel: Stream selection for multi-stream interfaces
56 * struct dpu_hw_ctl_ops - Interface to the wb Hw driver functions
61 * kickoff hw operation for Sw controlled interfaces
62 * DSI cmd mode and WB interface are SW controlled
76 * controlled interfaces: DSI cmd mode and WB interface
77 * are SW controlled
84 * No effect on hardware.
[all …]
/openbmc/u-boot/doc/device-tree-bindings/thermal/
H A Drockchip-thermal.txt4 - compatible : "rockchip,rk3288-tsadc"
5 - reg : physical base address of the controller and length of memory mapped
7 - interrupts : The interrupt number to the cpu. The interrupt specifier format
9 - clocks : Must contain an entry for each entry in clock-names.
10 - clock-names : Shall be "tsadc" for the converter-clock, and "apb_pclk" for
12 - resets : Must contain an entry for each entry in reset-names.
14 - reset-names : Must include the name "tsadc-apb".
15 - #thermal-sensor-cells : Should be 1. See ./thermal.txt for a description.
16 - rockchip,hw-tshut-temp : The hardware-controlled shutdown temperature value.
17 - rockchip,hw-tshut-mode : The hardware-controlled shutdown mode 0:CRU 1:GPIO.
[all …]
/openbmc/u-boot/doc/device-tree-bindings/leds/
H A Dleds-bcm6328.txt4 In these SoCs it's possible to control LEDs both as GPIOs or by hardware.
6 controller), which can either be controlled by software (exporting the 74x164
7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
8 by hardware using this driver.
9 Some of these Serial LEDs are hardware controlled (e.g. ethernet LEDs) and
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
11 controlled, so the only chance to keep them working is by using this driver.
14 - compatible : should be "brcm,bcm6328-leds".
15 - #address-cells : must be 1.
16 - #size-cells : must be 0.
[all …]
/openbmc/linux/Documentation/devicetree/bindings/thermal/
H A 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>
15 - rockchip,px30-tsadc
16 - rockchip,rk3228-tsadc
17 - rockchip,rk3288-tsadc
18 - rockchip,rk3328-tsadc
19 - rockchip,rk3368-tsadc
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A 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_…
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 …]
/openbmc/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 …]
/openbmc/u-boot/include/dt-bindings/clock/
H A Dtegra186-clock.h375 /** @brief output branch of PLL_C for ISP, controlled by gate CLK_ENB_PLLC_OUT_ISP */
377 /** @brief output branch of PLL_C for VI, controlled by gate CLK_ENB_PLLC_OUT_VE */
379 /** @brief output branch of PLL_C for AON domain, controlled by gate CLK_ENB_PLLC_OUT_AON */
383 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_I2S2 */
385 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_I2S3 */
387 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SPDF_IN */
397 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SPI1 */
399 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_ISP */
401 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_VI */
403 /** @brief output of mux controlled by CLK_RST_CONTROLLER_CLK_SOURCE_SDMMC1 */
[all …]
/openbmc/linux/drivers/mux/
H A 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.
/openbmc/linux/include/uapi/sound/
H A 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 …]
/openbmc/docs/designs/
H A Dguard-on-bmc.md40 usecase, and the availability of a redundant hardware resource to keep the
45 hardware resources in a server system. The BMC creates guard records on a
48 be controlled by BMC. The BMC retrieves the guard records for presenting to an
56 ![Guard Usecases](https://user-images.githubusercontent.com/16666879/70852658-0edfda80-1eca-11ea-9d…
58 - When user requests, create a record in the right guard record repository,
59 based on the hardware component.
60 - An option should be given to user to create guard record for DIMM and
62 - An option should be given to the user to delete a guard record.
63 - An option should be given to list the guard records.
64 - An option should be given to delete all guard records
[all …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A Dother.json35 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
44 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
71 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
80 … Sub NUMA Cluster(SNC) Mode. In SNC Mode counts PMM accesses that are controlled by the close or …
116 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
143 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
152 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
161 …"BriefDescription": "Counts data load hardware prefetch requests to the L1 data cache that have an…
170 …"BriefDescription": "Counts hardware prefetches (which bring data to L2) that have any type of res…
179 … "BriefDescription": "Counts hardware prefetches to the L3 only that have any type of response.",
[all …]
/openbmc/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
/openbmc/linux/drivers/clk/meson/
H A 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 …]
/openbmc/qemu/linux-headers/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
/openbmc/phosphor-fan-presence/docs/monitor/
H A Dsensors.md11 - Minimum = ([target] _(100 - [`deviation`](deviation.md)) / 100)_ `factor` +
13 - Maximum = ([target] _(100 + [`deviation`](deviation.md)) / 100)_ `factor` +
21 - `name` - string
22 - The name of the fan tach sensors located under the
23 `/xyz/openbmc_project/sensors/fan_tach` D-Bus path.
24 - `has_target` - boolean
25 - Whether this sensor D-Bus object contains the `Target` property or not.
26 - `target_interface` - string (Optional)
27 - The D-Bus interface containing the `Target` property. This defaults to
28 `xyz.openbmc_project.Control.FanSpeed` for RPM controlled fans or can be set
[all …]
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A 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 …]
/openbmc/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 …]
/openbmc/linux/arch/s390/kvm/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
21 prompt "Kernel-based Virtual Machine (KVM) support"
42 This module provides access to the hardware capabilities through
51 bool "Userspace controlled virtual machines"
55 controlled by userspace.
/openbmc/linux/drivers/gpio/
H A 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 …]
/openbmc/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A Dother.json3 … where the core was running in a manner where Turbo may be clipped to the Non-AVX turbo schedule.",
6 …s running with power-delivery for baseline license level 0. This includes non-AVX codes, SSE, AVX…
14 … running with power-delivery for license level 1. This includes high current AVX 256-bit instruct…
22 … running with power-delivery for license level 2 (introduced in Skylake Server microarchtecture). …
101 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
110 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
137 …uster(SNC) Mode. In SNC Mode counts only those DRAM accesses that are controlled by the close SNC…
146 …luster(SNC) Mode. In SNC Mode counts only those PMM accesses that are controlled by the close SNC…
182 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
191 … on a distant memory controller of this socket when the system is in SNC (sub-NUMA cluster) mode.",
[all …]

12345678910>>...29