Searched +full:default +full:- +full:brightness +full:- +full:level (Results 1 – 20 of 20) sorted by relevance
| /Documentation/devicetree/bindings/leds/backlight/ |
| 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 | 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 | 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 | 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,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 | 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 | 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 | 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 …]
|
| 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 …]
|
| /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-bus-pci | 4 Contact: linux-pci@vger.kernel.org 8 this location. This is useful for overriding default 15 (Note: kernels before 2.6.28 may require echo -n). 20 Contact: linux-pci@vger.kernel.org 24 this location. This may be useful when overriding default 31 (Note: kernels before 2.6.28 may require echo -n). 36 Contact: linux-pci@vger.kernel.org 55 Contact: Chris Wright <chrisw@sous-sol.org> 72 Contact: Linux PCI developers <linux-pci@vger.kernel.org> 74 Writing a non-zero value to this attribute will [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/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/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/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/v4l/ |
| 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 13 values, and the default value will vary from device to device. The 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 35 Different in the sense of other bounds, another default and current 57 .. _control-id: [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 …]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 3 default: lazy 4 By default, unaccepted memory is accepted lazily to 16 force -- enable ACPI if default was off 17 on -- enable ACPI but allow fallback to DT [arm64,riscv64] 18 off -- disable ACPI if default was on 19 noirq -- do not use ACPI for IRQ routing 20 strict -- Be less tolerant of platforms that are not 22 rsdt -- prefer RSDT over (default) XSDT 23 copy_dsdt -- copy DSDT to memory 24 nospcr -- disable console in ACPI SPCR table as [all …]
|
| /Documentation/admin-guide/media/ |
| D | ipu3.rst | 1 .. SPDX-License-Identifier: GPL-2.0 24 ImgU). The CIO2 driver is available as drivers/media/pci/intel/ipu3/ipu3-cio2* 36 Both of the drivers implement V4L2, Media Controller and V4L2 sub-device 38 MIPI CSI-2 interfaces through V4L2 sub-device sensor drivers. 44 interface to the user space. There is a video node for each CSI-2 receiver, 47 The CIO2 contains four independent capture channel, each with its own MIPI CSI-2 48 receiver and DMA engine. Each channel is modelled as a V4L2 sub-device exposed 49 to userspace as a V4L2 sub-device node and has two pads: 53 .. flat-table:: 54 :header-rows: 1 [all …]
|