/linux-6.1.9/drivers/leds/ |
D | TODO | 29 really different from driver for RGB color LED that can run its own 32 * Figure out what to do with RGB leds 36 RGB, and not even RGB-White or RGB-Yellow variants emerged. 38 Multicolor is not a good fit for RGB LED. It does not really know 46 multicolor for RGB LEDs. 50 RGB LEDs are quite common, and it would be good to be able to turn LED
|
/linux-6.1.9/Documentation/devicetree/bindings/leds/ |
D | cznic,turris-omnia-leds.yaml | 13 This module adds support for the RGB LEDs found on the front panel of the 14 Turris Omnia router. There are 12 RGB LEDs that are controlled by a 39 This node represents one of the RGB LED devices on Turris Omnia. 41 supports RGB LEDs. 73 * No subnodes are needed, this controller only supports RGB
|
D | leds-lp50xx.yaml | 7 title: LED driver for LP50XX RGB LED from Texas Instruments. 13 The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into 16 The difference in these RGB LED drivers is the number of supported RGB
|
/linux-6.1.9/Documentation/leds/ |
D | leds-lp5562.rst | 26 Value: RGB or W 46 Engine mux has two different mode, RGB and W. 47 RGB is used for loading RGB program data, W is used for W program data. 52 echo "RGB" > /sys/bus/i2c/devices/xxxx/engine_mux # engine mux for RGB
|
D | leds-qcom-lpg.rst | 11 number of PWM channels, a programmable pattern lookup table and a RGB LED 15 individual LEDs, grouped together as RGB LEDs or otherwise be accessed as PWM 17 blocks, such as the RGB current sink, GPIO pins etc.
|
D | leds-blinkm.rst | 7 They are RGB-LED modules driven by a (AT)tiny microcontroller and 12 The device accepts RGB and HSB color values through separate commands.
|
/linux-6.1.9/Documentation/fb/ |
D | arkfb.rst | 21 * 16 bpp truecolor modes (RGB 555 and RGB 565) 22 * 24 bpp truecolor mode (RGB 888) 23 * 32 bpp truecolor mode (RGB 888)
|
D | s3fb.rst | 28 * 16 bpp truecolor modes (RGB 555 and RGB 565) 29 * 24 bpp truecolor mode (RGB 888) on (only on Virge VX) 30 * 32 bpp truecolor mode (RGB 888) on (not on Virge VX)
|
D | vt8623fb.rst | 20 * 16 bpp truecolor mode (RGB 565) 21 * 32 bpp truecolor mode (RGB 888)
|
D | pxafb.rst | 89 support palette and no-palette RGB formats, as well as YUV formats (only 144 4) var->{red, green, blue, transp} if RGB mode is to be used 165 - 0 - RGB
|
/linux-6.1.9/drivers/gpu/drm/panel/ |
D | Kconfig | 48 uses 24 bit RGB per pixel. It provides a MIPI DSI interface to 59 24 bit RGB per pixel. It provides a MIPI DSI interface to 163 QVGA (320x240) RGB, YUV and ITU-T BT.656 panels. 174 QVGA (240x320) RGB panels. support serial & parallel rgb 203 24 bit RGB per pixel. It provides a MIPI DSI interface to 214 The panel has a 1200(RGB)×1920 (WUXGA) resolution and uses 234 24 bit RGB per pixel. It provides a MIPI DSI interface to 245 24 bit RGB per pixel. It provides a MIPI DSI interface to 256 24 bit RGB per pixel. It provides a MIPI DSI interface to 267 24 bit RGB per pixel. It provides a MIPI DSI interface to [all …]
|
/linux-6.1.9/Documentation/userspace-api/media/v4l/ |
D | pixfmt-meta-vsp1-hgo.rst | 18 The VSP1 HGO is a histogram computation engine that can operate on RGB, YCrCb 24 three channels (RGB data only) or on the Y channel only (YCbCr only). It can 29 to compute three 64-bins histograms. RGB, YCbCr and HSV image formats are 32 channels to compute a single 64-bins histogram. Only the RGB image format is 37 channels to compute a single 256-bins histogram. Only the RGB image format is
|
D | pixfmt-rgb.rst | 6 RGB Formats 9 These formats encode each pixel as a triplet of RGB values. They are packed 10 formats, meaning that the RGB values for one pixel are stored consecutively in 15 The formats differ by the number of bits per RGB component (typically but not 53 These formats store an RGB triplet in one, two or four bytes. They are named 54 based on the order of the RGB components as seen in a 8-, 16- or 32-bit word, 75 .. flat-table:: RGB Formats With Less Than 8 Bits Per Component 645 These formats store an RGB triplet in three or four bytes. They are named based 646 on the order of the RGB components as stored in memory, and on the total number 660 .. flat-table:: RGB Formats With 8 Bits Per Component [all …]
|
D | colorspaces.rst | 13 actually *means* to have an RGB value of e.g. (255, 0, 0). That is, 23 different wavelengths, so instead of RGB we would be using the 91 Both the CIE XYZ and the RGB colorspace that are derived from the 99 values are denoted RGB, non-linear are denoted as R'G'B'. In general 101 linear RGB. Special care should be taken when dealing with openGL to 102 provide linear RGB colors or to use the built-in openGL support to apply 121 The final step is how the RGB, R'G'B' or Y'CbCr values are quantized. 130 definition. In practice RGB or R'G'B' values are full range, i.e. they 134 Unfortunately, in some cases limited range RGB is also used where the
|
/linux-6.1.9/Documentation/devicetree/bindings/display/bridge/ |
D | toshiba,tc358768.yaml | 7 title: Toschiba TC358768/TC358778 Parallel RGB to MIPI DSI bridge 13 The TC358768/TC358778 is bridge device which converts RGB to DSI. 52 Video port for RGB input
|
D | chipone,icn6211.yaml | 7 title: Chipone ICN6211 MIPI-DSI to RGB Converter bridge 13 ICN6211 is MIPI-DSI to RGB Converter bridge from chipone. 46 description: A 1.8V/2.5V/3.3V supply that power the RGB output.
|
/linux-6.1.9/Documentation/gpu/ |
D | afbc.rst | 28 (AFBC_FORMAT_MOD_YTR, which should be enabled for RGB buffers for 126 - 10-bit per component RGB, with 2-bit alpha 134 - 8-bit per component RGB, with 8-bit alpha 142 - 8-bit per component RGB 149 - 5/6-bit per component RGB 156 - 5-bit per component RGB, with 1-bit alpha
|
D | kms-properties.csv | 20 i915,Generic,"""Broadcast RGB""",ENUM,"{ ""Automatic"", ""Full"", ""Limited 16:235"" }",Connector,"… 40 CDV gma-500,Generic,"""Broadcast RGB""",ENUM,"{ “Full”, “Limited 16:235” }",Connector,TBD 41 ,,"""Broadcast RGB""",ENUM,"{ “off”, “auto”, “on” }",Connector,TBD 68 …NUM,"{ ""disabled"", ""Y component"", ""U component"" , ""V component"", ""RGB"", “R component"", …
|
/linux-6.1.9/drivers/leds/rgb/ |
D | Kconfig | 24 sink, intended to drive RGB LEDs. Each channel can either be used as 25 a LED, grouped to represent a RGB LED or exposed as PWM channels.
|
/linux-6.1.9/arch/arm/boot/dts/ |
D | am335x-boneblack-hdmi.dtsi | 56 /* If you want to get 24 bit RGB and 16 BGR mode instead of 57 * current 16 bit RGB and 24 BGR modes, set the propety 81 /* Convert 24bit BGR to RGB, e.g. cross red and blue wiring */
|
/linux-6.1.9/Documentation/hwmon/ |
D | aquacomputer_d5next.rst | 9 * Aquacomputer Farbwerk RGB controller 10 * Aquacomputer Farbwerk 360 RGB controller 33 RGB LEDs, for which there is no standard sysfs interface. Thus, that task is
|
/linux-6.1.9/Documentation/admin-guide/media/ |
D | vimc.dot | 21 …n00000013 [label="{{} | RGB/YUV Input\n/dev/v4l-subdev4 | {<port0> 0}}", shape=Mrecord, style=fill… 25 n00000018 [label="RGB/YUV Capture\n/dev/video2", shape=box, style=filled, fillcolor=yellow]
|
/linux-6.1.9/drivers/gpu/drm/rockchip/ |
D | Kconfig | 93 bool "Rockchip RGB support" 97 Choose this option to enable support for Rockchip RGB output. 99 and serial RGB format to panel or connect to a conversion chip.
|
/linux-6.1.9/Documentation/devicetree/bindings/display/panel/ |
D | tpo,tpg110.yaml | 15 between an RGB output and a variety of panels. The panel 24 RGB -> | TPG110 |
|
/linux-6.1.9/drivers/gpu/drm/bridge/imx/ |
D | imx8qxp-pixel-combiner.c | 55 RGB, enumerator 171 val |= PC_DISP0_PIX_DATA_FORMAT(RGB); in imx8qxp_pc_bridge_mode_set() 174 val |= PC_DISP1_PIX_DATA_FORMAT(RGB); in imx8qxp_pc_bridge_mode_set()
|