Searched full:flash (Results 1 – 25 of 228) sorted by relevance
12345678910
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 6 Flash Control Reference
9 The V4L2 flash controls are intended to provide generic access to flash
10 controller devices. Flash controller devices are typically used in
13 The interface can support both LED and xenon flash devices. As of
14 writing this, there is no xenon flash driver using this interface.
23 Unsynchronised LED flash (software strobe)
26 Unsynchronised LED flash is controlled directly by the host as the
27 sensor. The flash must be enabled by the host before the exposure of the
29 for the timing of the flash.
34 Synchronised LED flash (hardware strobe)
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-flash | 6 Set the brightness of this LED in the flash strobe mode, in
7 microamperes. The file is created only for the flash LED devices
8 that support setting flash brightness.
18 Maximum brightness level for this LED in the flash strobe mode,
26 Hardware timeout for flash, in microseconds. The flash strobe
28 of the strobe. The file is created only for the flash LED
29 devices that support setting flash timeout.
36 Maximum flash timeout for this LED, in microseconds.
43 Flash strobe state. When written with 1 it triggers flash strobe
44 and when written with 0 it turns the flash off.
[all …]
|
| /Documentation/leds/ |
| D | leds-class-flash.rst | 2 Flash LED handling under Linux
5 Some LED devices provide two modes - torch and flash. In the LED subsystem
7 and LED Flash class respectively. The torch mode related features are enabled
8 by default and the flash ones only if a driver declares it by setting
11 In order to enable the support for flash LEDs CONFIG_LEDS_CLASS_FLASH symbol
12 must be defined in the kernel config. A LED Flash class driver must be
15 Following sysfs attributes are exposed for controlling flash LED devices:
16 (see Documentation/ABI/testing/sysfs-class-led-flash)
26 V4L2 flash wrapper for flash LEDs
37 flash device, e.g. an I2C device
[all …]
|
| D | leds-lm3556.rst | 6 1.5 A Synchronous Boost LED Flash Driver w/ High-Side Current Source
16 There are 3 functions in LM3556, Flash, Torch and Indicator.
18 Flash Mode
21 In Flash Mode, the LED current source(LED) provides 16 target current levels
22 from 93.75 mA to 1500 mA.The Flash currents are adjusted via the CURRENT
23 CONTROL REGISTER(0x09).Flash mode is activated by the ENABLE REGISTER(0x0A),
26 LM3556 Flash can be controlled through sys/class/leds/flash/brightness file
31 Flash Example:
35 #echo 0 > sys/class/leds/flash/brightness
39 #echo 1 > sys/class/leds/flash/brightness
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-ktd2692.txt | 1 * Kinetic Technologies - KTD2692 Flash LED Driver
3 KTD2692 is the ideal power solution for high-power flash LEDs.
7 enable/disable the IC, Movie(max 1/3 of Flash current) / Flash mode current,
8 Flash timeout, LVP(low voltage protection).
11 LED current will be ramped up to the flash-mode current level.
25 Required properties for flash LED child nodes:
29 - flash-max-microamp : Flash LED maximum current
31 - flash-max-timeout-us : Flash LED maximum timeout.
33 Optional properties for flash LED child nodes:
44 flash-led {
[all …]
|
| D | leds-aat1290.txt | 1 * Skyworks Solutions, Inc. AAT1290 Current Regulator for Flash LEDs
4 asserted high, enable flash strobe and movie mode (max 1/2 of flash current)
7 of the flash chip. The switch is controlled with pin control.
12 - flen-gpios : Must be device tree identifier of the flash device FL_EN pin.
13 - enset-gpios : Must be device tree identifier of the flash device EN_SET pin.
27 - flash-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
28 Maximum flash LED supply current can be calculated using
30 - flash-max-timeout-us : see Documentation/devicetree/bindings/leds/common.txt
31 Maximum flash timeout can be calculated using following
60 flash-max-microamp = <1012500>;
[all …]
|
| D | ams,as3645a.txt | 3 The AS3645A flash LED controller can drive two LEDs, one high current
4 flash LED and one indicator LED. The high current flash LED can be
22 Required properties of the flash child node (0)
26 flash-timeout-us: Flash timeout in microseconds. The value must be in
28 flash-max-microamp: Maximum flash current in microamperes. Has to be
34 ams,input-max-microamp: Maximum flash controller input current. The
39 Optional properties of the flash child node
74 flash-timeout-us = <150000>;
75 flash-max-microamp = <320000>;
|
| D | leds-lm3601x.txt | 1 * Texas Instruments - lm3601x Single-LED Flash Driver
3 The LM3601X are ultra-small LED flash drivers that
18 Required properties for flash LED child nodes:
20 - flash-max-microamp : Range from 11mA - 1.5A
21 - flash-max-timeout-us : Range from 40ms - 1600ms
44 flash-max-microamp = <1500000>;
45 flash-max-timeout-us = <1600000>;
|
| D | leds-sgm3140.yaml | 14 levels for Flash and Torch modes.
27 flash-gpios:
29 description: A connection to the 'FLASH' pin.
40 - flash-gpios
52 flash-gpios = <&pio 3 24 GPIO_ACTIVE_HIGH>; /* PD24 */
59 flash-max-timeout-us = <250000>;
|
| D | common.yaml | 14 LED and flash LED devices provide the same basic functionality as current
15 regulators, but extended with LED and flash LED specific features like
16 blinking patterns, flash timeout, flash faults and external flash strobe mode.
122 For flash LED controllers with configurable current this property is
123 mandatory for the LEDs in the non-flash modes (e.g. torch or indicator).
148 # Required properties for flash LED child nodes:
149 flash-max-microamp:
151 Maximum flash LED supply current in microamperes. Required for flash LED
154 flash-max-timeout-us:
156 Maximum timeout in microseconds after which the flash LED is turned off.
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | intel,ixp4xx-flash.txt | 1 Flash device on Intel IXP4xx SoC
3 This flash is regular CFI compatible (Intel or AMD extended) flash chips with
7 - compatible : must be "intel,ixp4xx-flash", "cfi-flash";
8 - reg : memory address for the flash chip
9 - bank-width : width in bytes of flash interface, should be <2>
18 flash@50000000 {
19 compatible = "intel,ixp4xx-flash", "cfi-flash";
|
| D | cortina,gemini-flash.txt | 1 Flash device on Cortina Systems Gemini SoC
3 This flash is regular CFI compatible (Intel or AMD extended) flash chips with
7 - compatible : must be "cortina,gemini-flash", "cfi-flash";
8 - reg : memory address for the flash chip
10 - bank-width : width in bytes of flash interface, should be <2>
19 flash@30000000 {
20 compatible = "cortina,gemini-flash", "cfi-flash";
|
| D | arm-versatile.txt | 1 Flash device on ARM Versatile board
3 These flash chips are found in the ARM reference designs like Integrator,
6 They are regular CFI compatible (Intel or AMD extended) flash chips with
11 - compatible : must be "arm,versatile-flash", "cfi-flash";
12 - reg : memory address for the flash chip
13 - bank-width : width in bytes of flash interface.
22 flash@34000000 {
23 compatible = "arm,versatile-flash", "cfi-flash";
|
| D | mtd-physmap.txt | 1 CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
3 Flash chips (Memory Technology Devices) are often used for solid state
7 used, if known, followed by either "cfi-flash", "jedec-flash",
20 mapping of the flash.
24 By defining "no-unaligned-direct-access", the flash will not be
27 physmap-flash drivers as boot loader pass the mtd partition via the old
28 device name physmap-flash.
38 - vendor-id : Contains the flash chip's vendor id (1 byte).
39 - device-id : Contains the flash chip's device id (1 byte).
41 For ROM compatible devices (and ROM fallback from cfi-flash), the following
[all …]
|
| D | partition.txt | 1 Flash partitions in device tree
4 Flash devices can be partitioned into one or more functional ranges (e.g. "boot
8 flash layout set at production time. Some may use on-flash table that describes
13 method is used for a given flash device. To describe the method there should be
14 a subnode of the flash device that is named 'partitions'. It must have a
30 Partitions can be represented by sub-nodes of a flash device. This can be used
31 on platforms which have strong conventions about which portions of a flash are
32 used for what purposes, but which don't use an on-flash partition table such
35 The partition table should be a subnode of the flash node and should be named
40 For backwards compatibility partitions as direct subnodes of the flash device are
[all …]
|
| D | jedec,spi-nor.txt | 1 * SPI NOR flash: ST M25Pxx (and similar) serial flash chips
9 Must also include "jedec,spi-nor" for any SPI NOR flash that can
51 designate quirky versions of flash chips that do not support the
72 - broken-flash-reset : Some flash devices utilize stateful addressing modes
74 carefully by a system. Because these sorts of flash don't
76 systems don't toggle the flash RESET# pin upon system reset
78 cannot reboot properly if the flash is left in the "wrong"
84 flash: m25p80@0 {
|
| D | cypress,hyperflash.txt | 1 Bindings for HyperFlash NOR flash chips compliant with Cypress HyperBus
5 - compatible : "cypress,hyperflash", "cfi-flash" for HyperFlash NOR chips
6 - reg : Address of flash's memory map
10 flash@0 {
11 compatible = "cypress,hyperflash", "cfi-flash";
|
| D | common.txt | 5 friendly names to MTD devices (instead of the flash model or flash
6 controller based name) in order to ease flash device identification
11 flash@0 {
14 /* flash type specific properties */
|
| D | nxp-spifi.txt | 1 * NXP SPI Flash Interface (SPIFI)
3 NXP SPIFI is a specialized SPI interface for serial Flash devices.
4 It supports one Flash device with 1-, 2- and 4-bits width in SPI
6 mode. In memory mode the Flash is accessible from the CPU as
13 - reg-names: Should contain the reg names "spifi" and "flash"
21 The SPI Flash must be a child of the SPIFI node and must have a
38 reg-names = "spifi", "flash";
44 flash@0 {
|
| D | aspeed-smc.txt | 2 * Aspeed SPI Flash Memory Controller
6 can be SPI or NOR type flash. These bindings only describe SPI.
8 The two SPI flash memory controllers in the AST2500 each support two
14 "aspeed,ast2400-spi" for the AST2400 SPI Flash memory Controller
16 "aspeed,ast2500-spi" for the AST2500 SPI flash memory controllers
27 The child nodes are the SPI flash modules which must have a compatible
43 flash@0 {
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | redboot-fis.txt | 1 RedBoot FLASH Image System (FIS) Partitions
4 The FLASH Image System (FIS) directory is a flash description
7 It uses one single flash eraseblock in the flash to store an index of
8 all images in the flash.
10 This block size will vary depending on flash but is typically
16 the FIS directory on this device. On a flash memory with 32KB
22 flash@0 {
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | adp1653.txt | 1 * Analog Devices ADP1653 flash LED driver
11 There are two LED outputs available - flash and indicator. One LED is
12 represented by one child node, nodes need to be named "flash" and "indicator".
17 Required properties of the flash LED child node:
19 - flash-max-microamp : see Documentation/devicetree/bindings/leds/common.txt
20 - flash-timeout-us : see Documentation/devicetree/bindings/leds/common.txt
30 flash {
31 flash-timeout-us = <500000>;
32 flash-max-microamp = <320000>;
|
| /Documentation/networking/devlink/ |
| D | devlink-flash.rst | 6 Devlink Flash
9 The ``devlink-flash`` API allows updating device firmware. It replaces the
10 older ``ethtool-flash`` mechanism, and doesn't require taking any
11 networking locks in the kernel to perform the flash update. Example use::
13 $ devlink dev flash pci/0000:05:00.0 file flash-boot.bin
22 The ``devlink-flash`` command allows optionally specifying a mask indicating
23 how the device should handle subsections of flash components when updating.
51 memory on the board, e.g. flash. Some devices store only basic firmware on
57 disk, or automatically flash a new image from disk. The ``fw_load_policy``
66 Drivers are expected to implement ``devlink-flash`` and ``devlink-info``
[all …]
|
| /Documentation/devicetree/bindings/ata/ |
| D | cavium-compact-flash.txt | 1 * Compact Flash
3 The Cavium Compact Flash device is connected to the Octeon Boot Bus,
5 industry standard compact flash devices.
8 - compatible: "cavium,ebt3000-compact-flash";
24 compact-flash@5,0 {
25 compatible = "cavium,ebt3000-compact-flash";
|
| /Documentation/arm/sa1100/ |
| D | assabet.rst | 52 you need to have RedBoot installed in your flash memory. A known to work
75 To initialize the flash directory::
85 Writing a kernel image into flash
97 To write it to flash::
113 Now the kernel can be retrieved from flash like this::
121 The ramdisk image could be stored into flash as well, but there are better
122 solutions for on-flash filesystems as mentioned below.
128 Using JFFS2 (the Second Journalling Flash File System) is probably the most
129 convenient way to store a writable filesystem into flash. JFFS2 is used in
130 conjunction with the MTD layer which is responsible for low-level flash
[all …]
|
12345678910