| /Documentation/leds/ |
| D | leds-mlxcpld.rst | 15 - mlxcpld:fan1:red
17 - mlxcpld:fan2:red
19 - mlxcpld:fan3:red
21 - mlxcpld:fan4:red
23 - mlxcpld:psu:red
25 - mlxcpld:status:red
57 - [0,1,0,1] = Red static ON
59 - [0,1,1,0] = Red blink 3Hz
61 - [0,1,1,1] = Red blink 6Hz
67 - mlxcpld:fan:red
[all …]
|
| D | leds-blinkm.rst | 54 /sys/class/leds/blinkm-6-9-red:
59 We can control the colors separated into red, green and blue and
83 blue green red test
85 Currently supported is just setting red, green, blue
99 $ echo 255 > red
|
| /Documentation/fb/ |
| D | cmap_xfbdev.rst | 12 .red = { 4, 3, 0 },
20 info->cmap.red[i] = (((2*i)+1)*(0xFFFF))/16;
21 memcpy(info->cmap.green, info->cmap.red, sizeof(u16)*8);
22 memcpy(info->cmap.blue, info->cmap.red, sizeof(u16)*8);
45 dr = (long) pent->co.local.red - prgb->red;
52 co.local.red are entries that were brought in through FBIOGETCMAP which come
53 directly from the info->cmap.red that was listed above. The prgb is the rgb
|
| D | api.rst | 52 bits_per_pixel, grayscale, red, green, blue and transp fields.
115 Pixels are broken into red, green and blue components, and each component
120 information red, green, blue and transp fields.
124 Pixel values are encoded as indices into a colormap that stores red, green and
133 Pixels are broken into red, green and blue components, and each component
137 information red, green, blue and transp fields.
193 struct fb_bitfield red; /* bitfield in fb mem if true color, */
247 - For grayscale formats, applications set the grayscale field to one. The red,
249 drivers. Drivers must fill the red, blue and green offsets to 0 and lengths
253 red, blue, green and transp fields must be set to 0 by applications and
[all …]
|
| D | internals.rst | 67 color (including red, green, and blue intensities) for each possible pixel
73 The pixel value is broken up into red, green, and blue fields.
78 The pixel value is broken up into red, green, and blue fields, each of which
79 are looked up in separate red, green, and blue lookup tables.
85 pseudo color, where the red, green and blue components are always equal to
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-cpcap.txt | 12 * "motorola,cpcap-led-red" (Red Triode)
24 cpcap_led_red: red-led {
25 compatible = "motorola,cpcap-led-red";
26 label = "cpcap:red";
|
| D | leds-netxbig.txt | 45 red-power {
46 label = "netxbig:red:power";
64 red-sata0 {
65 label = "netxbig:red:sata0";
83 red-sata1 {
84 label = "netxbig:red:sata1";
|
| D | leds-bcm6358.txt | 75 label = "red:power";
90 label = "red:broadband";
104 label = "red:wireless";
118 label = "red:phone";
132 label = "red:upgrading";
|
| /Documentation/devicetree/bindings/display/tilcdc/ |
| D | tilcdc.txt | 20 - blue-and-red-wiring: Recognized values "straight" or "crossed".
25 - "crossed" indicates wiring that has blue and red wires
30 RGB888 and XRGB8888 formats. However, depending on wiring, the red
45 but for 24 bit color modes the wiring of blue and red components is
46 crossed and LCD_DATA[0:4] is for Red[3:7] and LCD_DATA[11:15] is
60 blue-and-red-wiring = "crossed";
|
| /Documentation/networking/ |
| D | vrf.rst | 191 …12: red: <NOARP,MASTER,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default …
206 red UP b6:6f:6e:f6:da:73 <NOARP,MASTER,UP,LOWER_UP>
236 $ ip link show vrf red
237 …3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master red state UP mode DEFA…
239 …4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master red state UP mode DEFA…
241 …7: eth5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master red state DOWN mode DEFAULT group defaul…
247 $ ip -br link show vrf red
263 $ ip neigh show vrf red
267 $ ip -6 neigh show vrf red
281 $ ip addr show vrf red
[all …]
|
| /Documentation/devicetree/bindings/iio/temperature/ |
| D | melexis,mlx90632.yaml | 7 title: Melexis MLX90632 and MLX90635 contactless Infra Red temperature sensor
15 There are various applications for the Infra Red contactless temperature
27 Since measured object emissivity effects Infra Red energy emitted,
40 Since measured object emissivity effects Infra Red energy emitted,
|
| /Documentation/devicetree/bindings/iio/health/ |
| D | maxim,max30102.yaml | 29 maxim,red-led-current-microamp:
30 description: RED LED current. Each step is approximately 200 microamps.
70 maxim,red-led-current-microamp = <7000>;
|
| /Documentation/gpu/dp-mst/ |
| D | topology-figure-2.dot | 14 driver -> port4 [color=red];
27 edge [color=red];
37 edge [color=red];
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-colorimetry.rst | 66 For describing the mastering display that uses Red, Green and Blue
69 corresponds to the Red color primary.
74 For describing the mastering display that uses Red, Green and Blue
77 corresponds to Red color primary.
|
| D | pixfmt-bayer.rst | 13 performed on the image. The formats contain green, red and blue components, with
14 alternating lines of red and green, and blue and green pixels in different
|
| /Documentation/devicetree/bindings/mfd/ |
| D | mc13xxx.txt | 32 3 : Red 1
35 6 : Red 2
38 9 : Red 3
46 3 : Red
51 0 : Charger Red
135 label = "system:red:live";
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | drbd-connection-state-overview.dot | 37 node [fontcolor=red]
38 fontcolor=red
78 edge [color=red]
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | rohm,bu27008.yaml | 13 The ROHM BU27008 is a sensor with 5 photodiodes (red, green, blue, clear
14 and IR) with four configurable channels. Red and green being always
|
| D | rohm,bu27010.yaml | 13 The ROHM BU27010 is a sensor with 6 photodiodes (red, green, blue, clear,
14 IR and flickering detection) with five configurable channels. Red, green
|
| /Documentation/core-api/ |
| D | rbtree.rst | 2 Red-black Trees (rbtree) in Linux
9 What are red-black trees, and what are they for?
12 Red-black trees are a type of self-balancing binary search tree, used for
19 Red-black trees are similar to AVL trees, but provide faster real-time bounded
26 There are a number of red-black trees in use in the kernel.
31 red-black tree. Virtual memory areas (VMAs) are tracked with red-black
36 information on the nature and implementation of Red Black Trees, see:
38 Linux Weekly News article on red-black trees
41 Wikipedia entry on red-black trees
42 https://en.wikipedia.org/wiki/Red-black_tree
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | board.rst | 26 led-gpios = <&gpio 15 GPIO_ACTIVE_HIGH>, /* red */
40 struct gpio_desc *red, *green, *blue, *power;
42 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH);
69 "\\_SB.GPI0", 0, ResourceConsumer) { 15 } // red
160 struct gpio_desc *red, *green, *blue, *power;
162 red = gpiod_get_index(dev, "led", 0, GPIOD_OUT_HIGH);
|
| /Documentation/networking/device_drivers/ethernet/dlink/ |
| D | dl2k.rst | 33 . Red Hat v6.2 (update kernel to 2.4.7)
34 . Red Hat v7.0 (update kernel to 2.4.7)
35 . Red Hat v7.1 (kernel 2.4.7)
36 . Red Hat v7.2 (kernel 2.4.7-10)
174 is based on a Red Hat 6.0/7.0 distribution, but it can easily be ported to
177 Red Hat v6.x/v7.x
193 4. Note that for most Linux distributions, Red Hat included, a configuration
|
| /Documentation/admin-guide/ |
| D | vga-softcursor.rst | 9 tricks: you can make your cursor look like a non-blinking red block,
60 To get red non-blinking block, use::
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | boe,bf060y8m-aj0.yaml | 17 Each pixel is divided into red and green dots, or blue and
18 green dots, and two pixels share red or blue dots which are
|
| /Documentation/devicetree/bindings/auxdisplay/ |
| D | holtek,ht16k33.yaml | 20 - adafruit,3108 # 0.56" 4-Digit 7-Segment FeatherWing Display (Red)
21 - adafruit,3130 # 0.54" Quad Alphanumeric FeatherWing Display (Red)
|