Searched full:pattern (Results 1 – 25 of 112) sorted by relevance
12345
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-trigger-pattern | 1 What: /sys/class/leds/<led>/pattern
5 Specify a software pattern for the LED, that supports altering
9 The pattern is given by a series of tuples, of brightness and
13 Documentation/devicetree/bindings/leds/leds-trigger-pattern.txt
19 Specify a hardware pattern for the LED, for LED hardware that
22 software pattern.
33 Specify a pattern repeat number. -1 means repeat indefinitely,
|
| D | sysfs-class-led-driver-sc27xx | 5 Specify a hardware pattern for the SC27XX LED. For the SC27XX
7 hardware pattern, which is used to configure the rise time,
11 for the high stage. To be compatible with the hardware pattern
21 Thus the format of the hardware pattern values should be:
|
| D | configfs-usb-gadget-sourcesink | 7 pattern - 0 (all zeros), 1 (mod63), 2 (none)
|
| D | sysfs-class-power-wilco | 9 typical battery usage pattern.
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-trigger-pattern.txt | 1 * Pattern format for LED pattern trigger
3 The pattern is given by a series of tuples, of brightness and duration (ms).
6 new value, and writing malformed pattern deactivates any active one.
13 The gradual dimming format of the software pattern values should be:
17 echo 0 1000 255 2000 > pattern
37 echo 0 1000 0 0 255 2000 255 0 > pattern
|
| D | common.txt | 56 "pattern" - LED alters the brightness for the specified duration with one
57 software timer (requires "led-pattern" property)
59 - led-pattern : Array of integers with default pattern for certain triggers.
63 - pattern : the pattern is given by a series of tuples, of
66 Documentation/devicetree/bindings/leds/leds-trigger-pattern.txt
|
| /Documentation/leds/ |
| D | leds-lp55xx.rst | 63 This pattern data is saved as a file in the user-land or
70 To load and run the pattern, the programming sequence is following.
74 (3) Write pattern data into selected area
90 For example, run blinking pattern in engine #1 of LP5521::
98 For example, run blinking pattern in engine #3 of LP55231
100 Two LEDs are configured as pattern output channels::
134 To run programmed pattern, 'run_engine' attribute should be enabled.
136 The pattern sequence of LP8501 is similar to LP5523.
138 However pattern data is specific.
179 ( Predefined pattern data )
[all …]
|
| D | leds-lm3556.rst | 77 Indicator pattern can be set through sys/class/leds/indicator/pattern file,
80 According to N-lank, Pulse time and N Period values, different pattern wiill
86 Indicator pattern example:
88 pattern 0::
90 #echo 0 > sys/class/leds/indicator/pattern
94 pattern 3::
96 #echo 3 > sys/class/leds/indicator/pattern
|
| D | leds-lp3944.rst | 26 The DIM modes are used to set _blink_ patterns for leds, the pattern is
34 Setting a led in DIM0 or DIM1 mode makes it blink according to the pattern.
|
| D | leds-lp5562.rst | 49 For example, run blinking green channel pattern::
58 To run a blinking white pattern::
|
| /Documentation/media/uapi/v4l/ |
| D | ext-ctrls-image-source.rst | 48 Test pattern red colour component.
51 Test pattern green (next to red) colour component.
54 Test pattern blue colour component.
57 Test pattern green (next to blue) colour component.
|
| /Documentation/devicetree/bindings/media/xilinx/ |
| D | video.txt | 29 - xlnx,cfa-pattern: When the video format is set to Mono/Sensor, this property
30 describes the sensor's color filter array pattern. Supported values are
31 "bggr", "gbrg", "grbg", "rggb" and "mono". If not specified, the pattern
|
| /Documentation/devicetree/bindings/mtd/ |
| D | fsl-upm-nand.txt | 6 - fsl,upm-addr-offset : UPM pattern offset for the address latch.
7 - fsl,upm-cmd-offset : UPM pattern offset for the command latch.
11 UPM pattern (0x1), after writing a data byte (0x2) or after
|
| /Documentation/devicetree/bindings/net/ |
| D | ethernet-phy.yaml | 21 pattern: "^ethernet-phy(@[a-f0-9]+)?$"
28 pattern: "^ethernet-phy(@[a-f0-9]+)?$"
36 - pattern: "^ethernet-phy-id[a-f0-9]{4}\\.[a-f0-9]{4}$"
47 - pattern: "^ethernet-phy-id[a-f0-9]{4}\\.[a-f0-9]{4}$"
|
| /Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.txt | 27 cycles to transmit before sending an SGPIO pattern
29 cycles to transmit after sending an SGPIO pattern
|
| /Documentation/devicetree/bindings/soundwire/ |
| D | soundwire-controller.yaml | 19 pattern: "^soundwire(@.*)?$"
33 pattern: "^sdw[0-9a-f]{1}[0-9a-f]{4}[0-9a-f]{4}[0-9a-f]{2}$"
|
| /Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 208 the check. This is done by way of the Dekker memory barrier pattern
209 (scenario 10 of [lwn-mb]_). As the Dekker pattern requires two variables,
211 them into the pattern gives::
225 the Dekker pattern has been extended to disable interrupts before setting
227 pedantically implement the memory barrier pattern, guaranteeing the
255 two-variable Dekker memory barrier pattern, then it's clear that
267 local_irq_disable() + smp_mb() pattern described above; the ON bit
|
| /Documentation/RCU/ |
| D | rcuref.txt | 121 A clear advantage of the RCU-based pattern in listing C over the one
149 As additional examples in the kernel, the pattern in listing C is used by
150 reference counting of struct pid, while the pattern in listing B is used by
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-hcd.yaml | 14 pattern: "^usb(@.*)?"
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | watchdog.yaml | 19 pattern: "^watchdog(@.*|-[0-9a-f])?$"
|
| /Documentation/driver-api/driver-model/ |
| D | design-patterns.rst | 22 pattern. It usually has this form::
102 The design pattern is the same for an hrtimer or something similar that will
|
| /Documentation/devicetree/bindings/dma/ |
| D | dma-controller.yaml | 18 pattern: "^dma-controller(@.*)?$"
|
| D | dma-router.yaml | 23 pattern: "^dma-router(@.*)?$"
|
| /Documentation/devicetree/bindings/gpio/ |
| D | pl061-gpio.yaml | 24 pattern: "^gpio@[0-9a-f]+$"
|
| /Documentation/devicetree/bindings/rtc/ |
| D | rtc.yaml | 18 pattern: "^rtc(@.*|-[0-9a-f])*$"
|
12345