Searched +full:brightness +full:- +full:level (Results 1 – 25 of 29) sorted by relevance
12
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | pwm-backlight.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 4 $id: http://devicetree.org/schemas/leds/backlight/pwm-backlight.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: pwm-backlight 10 - Lee Jones <lee@kernel.org> 11 - Daniel Thompson <daniel.thompson@linaro.org> 12 - Jingoo Han <jingoohan1@gmail.com> 15 - $ref: common.yaml# 19 const: pwm-backlight [all …]
|
| D | common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Lee Jones <lee@kernel.org> 11 - Daniel Thompson <daniel.thompson@linaro.org> 12 - Jingoo Han <jingoohan1@gmail.com> 20 default-brightness: 22 The default brightness that should be applied to the LED by the operating 23 system on start-up. The brightness should not exceed the brightness the 27 max-brightness: [all …]
|
| D | mediatek,mt6370-backlight.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/backlight/mediatek,mt6370-backlight.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - ChiaEn Wu <chiaen_wu@richtek.com> 21 - $ref: common.yaml# 26 - mediatek,mt6370-backlight 27 - mediatek,mt6372-backlight 29 default-brightness: 32 max-brightness: [all …]
|
| D | kinetic,ktd2801.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Kinetic Technologies KTD2801 one-wire backlight 10 - Duje Mihanović <duje.mihanovic@skole.hr> 15 or by pulsing the GPIO line to set the backlight level. This is called 19 - $ref: common.yaml# 25 ctrl-gpios: 28 default-brightness: true 29 max-brightness: true [all …]
|
| D | tps65217-backlight.txt | 7 - compatible: "ti,tps65217" 8 - reg: I2C slave address 9 - backlight: node for specifying WLED1 and WLED2 lines in TPS65217 10 - isel: selection bit, valid values: 1 for ISEL1 (low-level) and 2 for ISEL2 (high-level) 11 - fdim: PWM dimming frequency, valid values: 100, 200, 500, 1000 12 - default-brightness: valid values: 0-100 22 isel = <1>; /* 1 - ISET1, 2 ISET2 */ 24 default-brightness = <50>;
|
| D | kinetic,ktd253.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Kinetic Technologies KTD253 and KTD259 one-wire backlight 10 - Linus Walleij <linus.walleij@linaro.org> 15 it goes to maximum backlight then you can set the level of backlight 20 - $ref: common.yaml# 25 - enum: 26 - kinetic,ktd253 27 - kinetic,ktd259 [all …]
|
| D | lm3630a-backlight.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/backlight/lm3630a-backlight.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: TI LM3630A High-Efficiency Dual-String White LED 10 - Lee Jones <lee@kernel.org> 11 - Daniel Thompson <daniel.thompson@linaro.org> 12 - Jingoo Han <jingoohan1@gmail.com> 15 The LM3630A is a current-mode boost converter which supplies the power and 26 '#address-cells': [all …]
|
| D | richtek,rt4831-backlight.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/backlight/richtek,rt4831-backlight.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - ChiYuan Huang <cy_huang@richtek.com> 20 https://www.richtek.com/assets/product_file/RT4831A/DS4831A-05.pdf 23 - $ref: common.yaml# 27 const: richtek,rt4831-backlight 29 default-brightness: 33 max-brightness: [all …]
|
| D | led-backlight.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only 3 --- 4 $id: http://devicetree.org/schemas/leds/backlight/led-backlight.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: led-backlight 10 - Lee Jones <lee@kernel.org> 11 - Daniel Thompson <daniel.thompson@linaro.org> 12 - Jingoo Han <jingoohan1@gmail.com> 20 - $ref: common.yaml# 24 const: led-backlight [all …]
|
| D | qcom-wled.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/backlight/qcom-wled.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Bjorn Andersson <andersson@kernel.org> 11 - Kiran Gunda <quic_kgunda@quicinc.com> 21 - qcom,pm8941-wled 22 - qcom,pmi8950-wled 23 - qcom,pmi8994-wled 24 - qcom,pmi8998-wled [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led | 1 What: /sys/class/leds/<led>/brightness 6 Set the brightness of the LED. 8 Most LEDs don't have hardware brightness support, so will 9 just be turned on for non-zero brightness settings. 20 led_brightness = brightness * multi_intensity/max_brightness 23 Documentation/leds/leds-class-multicolor.rst. 30 Writing non-zero to this file while trigger is active changes the 31 top brightness trigger is going to use. 40 Maximum brightness level for this LED, default is 255 (LED_FULL). 42 If the LED does not support different brightness levels, this [all …]
|
| D | sysfs-class-backlight | 6 Description of the scale of the brightness curve. 8 The human eye senses brightness approximately logarithmically, 9 hence linear changes in brightness are perceived as being 10 non-linear. To achieve a linear perception of brightness changes 12 backlights with a linear brightness curve. 17 The scale of the brightness curve is unknown. 20 The brightness changes linearly with each step. Brightness 24 non-linear 25 The brightness changes non-linearly with each step. Brightness 38 The value range is device-driver specific: [all …]
|
| D | sysfs-class-led-driver-aw200xx | 3 Description: 64-level DIM current. If you write a negative value or 5 brightness.
|
| D | sysfs-class-led-flash | 6 Set the brightness of this LED in the flash strobe mode, in 8 that support setting flash brightness. 18 Maximum brightness level for this LED in the flash strobe mode, 55 Flash faults are re-read after strobing the flash. Possible 58 * led-over-voltage 61 * flash-timeout-exceeded 65 * controller-over-temperature 68 * controller-short-circuit 71 * led-power-supply-over-current 75 * indicator-led-fault [all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 1 .. SPDX-License-Identifier: GPL-2.0 16 Export a sysfs interface for user space to control backlight level 26 Documentation/ABI/stable/sysfs-class-backlight. 32 get the brightness level the firmware thinks it is at; 34 not implemented, will set the current brightness instead; 35 brightness: 36 on write, control method _BCM will run to set the requested brightness level; 43 brightness, actual_brightness and max_brightness. So if we have 68 corresponds to the 0x0A brightness value) to 9 (that corresponds to the 69 0x64 brightness value) inclusive. Each of those index values is regarded [all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | ti-lmu.txt | 6 ------ --------------------------------- 14 - compatible: Should be one of: 20 - reg: I2C slave address. 28 - enable-gpios: A GPIO specifier for hardware enable pin. 29 - ramp-up-us: Current ramping from one brightness level to 30 the a higher brightness level. 31 Range from 2048 us - 117.44 s 32 - ramp-down-us: Current ramping from one brightness level to 33 the a lower brightness level. 34 Range from 2048 us - 117.44 s [all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-backlight | 9 - 0 (FB_BLANK_UNBLANK) : power on. 10 - 4 (FB_BLANK_POWERDOWN) : power off 13 What: /sys/class/backlight/<backlight>/brightness 18 Control the brightness for this <backlight>. Values 20 show the brightness level stored in the driver, which 21 may not be the actual brightness (see actual_brightness). 29 Show the actual brightness by querying the hardware. 37 Maximum brightness for <backlight>. 47 "platform": The driver uses a platform-specific interface 57 holdover from pre-standardisation of firmware
|
| /Documentation/leds/ |
| D | leds-class-multicolor.rst | 1 .. SPDX-License-Identifier: GPL-2.0 12 via brightness file. 18 led_class framework. The led_class framework is documented in led-class.rst 34 root:/sys/class/leds/multicolor:status# ls -lR 35 -rw-r--r-- 1 root root 4096 Oct 19 16:16 brightness 36 -r--r--r-- 1 root root 4096 Oct 19 16:16 max_brightness 37 -r--r--r-- 1 root root 4096 Oct 19 16:16 multi_index 38 -rw-r--r-- 1 root root 4096 Oct 19 16:16 multi_intensity 40 Multicolor Class Brightness Control 42 The brightness level for each LED is calculated based on the color LED [all …]
|
| /Documentation/admin-guide/laptops/ |
| D | thinkpad-acpi.rst | 9 - Borislav Deianov <borislav@users.sf.net> 10 - Henrique de Moraes Holschuh <hmh@hmh.eng.br> 12 http://ibm-acpi.sf.net/ 19 This driver used to be named ibm-acpi until kernel 2.6.21 and release 20 0.13-20070314. It used to be in the drivers/acpi tree, but it was 21 moved to the drivers/misc tree and renamed to thinkpad-acpi for kernel 25 The driver is named "thinkpad-acpi". In some places, like module 29 "tpacpi" is used as a shorthand where "thinkpad-acpi" would be too 33 ------ 38 - Fn key combinations [all …]
|
| /Documentation/devicetree/bindings/auxdisplay/ |
| D | holtek,ht16k33.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Robin van der Gracht <robin@protonic.nl> 13 - $ref: /schemas/input/matrix-keymap.yaml# 18 - items: 19 - enum: 20 - adafruit,3108 # 0.56" 4-Digit 7-Segment FeatherWing Display (Red) 21 - adafruit,3130 # 0.54" Quad Alphanumeric FeatherWing Display (Red) 22 - const: holtek,ht16k33 [all …]
|
| /Documentation/power/regulator/ |
| D | overview.rst | 26 - Regulator 27 - Electronic device that supplies power to other devices. 31 Input Voltage -> Regulator -> Output Voltage 34 - PMIC 35 - Power Management IC. An IC that contains numerous 39 - Consumer 40 - Electronic device that is supplied power by a regulator. 41 Consumers can be classified into two types:- 52 - Power Domain 53 - Electronic circuit that is supplied its input power by the [all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-colorimetry.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _colorimetry-controls: 15 ----------------------- 17 .. _colorimetry-control-id: 25 The Content Light Level defines upper bounds for the nominal target 26 brightness light level of the pictures. 32 .. flat-table:: struct v4l2_ctrl_hdr10_cll_info 33 :header-rows: 0 34 :stub-columns: 0 37 * - __u16 [all …]
|
| D | control.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 9 Devices typically have a number of user-settable controls such as 10 brightness, saturation and so on, which would be presented to the user 21 pre-defined control IDs have the prefix ``V4L2_CID_``, and are listed in 22 :ref:`control-id`. The ID is used when querying the attributes of a 27 the user is supposed to understand. When the purpose is non-intuitive 28 the driver writer should provide a user manual, a user interface plug-in 57 .. _control-id: 69 Picture brightness, or more precisely, the black level. 104 Another name for brightness (not a synonym of [all …]
|
| /Documentation/gpu/ |
| D | todo.rst | 11 ---------- 29 Subsystem-wide refactorings 33 --------------------------------------------- 42 Level: Intermediate 45 -------------------------------------------------- 53 non-converted driver. The "Atomic mode setting design overview" series [2]_ 60 .. [1] https://blog.ffwll.ch/2014/11/atomic-modeset-support-for-kms-drivers.html 66 Level: Advanced 69 --------------------------------------------------------- 75 avoid confusion - the other helpers in that file are all deprecated legacy [all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | uvcvideo.rst | 1 .. SPDX-License-Identifier: GPL-2.0 6 This file documents some driver-specific aspects of the UVC driver, such as 7 driver-specific ioctls and implementation notes. 10 linux-media@vger.kernel.org. 14 --------------------------- 19 The UVC specification allows for vendor-specific extensions through extension 23 - through mappings of XU controls to V4L2 controls 24 - through a driver-specific ioctl interface 30 The second mechanism requires uvcvideo-specific knowledge for the application to 40 The UVC driver provides an API for user space applications to define so-called [all …]
|
12