Searched +full:on +full:- +full:flash (Results 1 – 25 of 189) sorted by relevance
12345678
| /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 …]
|
| D | sysfs-bus-spi-devices-spi-nor | 1 What: /sys/bus/spi/devices/.../spi-nor/jedec_id
4 Contact: linux-mtd@lists.infradead.org
5 Description: (RO) The JEDEC ID of the SPI NOR flash as reported by the
6 flash device.
8 The attribute is not present if the flash doesn't support
10 non-JEDEC compliant flashes.
12 What: /sys/bus/spi/devices/.../spi-nor/manufacturer
15 Contact: linux-mtd@lists.infradead.org
16 Description: (RO) Manufacturer of the SPI NOR flash.
18 The attribute is not present if the flash device isn't
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | redboot-fis.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/redboot-fis.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: RedBoot FLASH Image System (FIS) Partitions
9 description: The FLASH Image System (FIS) directory is a flash description
11 It uses one single flash eraseblock in the flash to store an index of
12 all images in the flash.
13 This block size will vary depending on flash but is typically
17 - Linus Walleij <linus.walleij@linaro.org>
[all …]
|
| D | tplink,safeloader-partitions.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mtd/partitions/tplink,safeloader-partitions.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TP-Link SafeLoader partitions
10 TP-Link home routers store various data on flash (e.g. bootloader,
11 flash layout, firmware, product info, configuration, calibration
12 data). That requires flash partitioning.
14 Flash space layout of TP-Link devices is stored on flash itself using
15 a custom ASCII-based format. That format was first found in TP-Link
[all …]
|
| /Documentation/networking/devlink/ |
| D | devlink-flash.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
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.
26 .. list-table:: List of overwrite mask bits
29 * - Name
[all …]
|
| D | devlink-selftests.rst | 1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
7 The ``devlink-selftests`` API allows executing selftests on the device.
11 The ``devlink-selftests`` command should be run with a mask indicating
18 .. list-table:: List of tests
21 * - Name
22 - Description
23 * - ``DEVLINK_SELFTEST_FLASH``
24 - Devices may have the firmware on non-volatile memory on the board, e.g.
25 flash. This particular test helps to run a flash selftest on the device.
29 -------------
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-flash.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _flash-controls:
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.
17 .. _flash-controls-use-cases:
23 Unsynchronised LED flash (software strobe)
24 ------------------------------------------
[all …]
|
| /Documentation/arch/arm/sa1100/ |
| D | assabet.rst | 2 The Intel Assabet (SA-1110 evaluation) board
13 -------------------
25 -----------------------
27 A couple of bootloaders able to boot Linux on Assabet are available:
39 John Dorsey has produced add-on patches to add support for Assabet and
44 RedBoot is a bootloader developed by Red Hat based on the eCos RTOS
51 Brief examples on how to boot Linux with RedBoot are shown below. But first
52 you need to have RedBoot installed in your flash memory. A known to work
55 - ftp://ftp.netwinder.org/users/n/nico/
56 - ftp://ftp.arm.linux.org.uk/pub/linux/arm/people/nico/
[all …]
|
| /Documentation/filesystems/ |
| D | ubifs-authentication.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 read contents of the filesystem on a single point in time. A classic example
18 on the device without the filesystem decryption key.
24 binary to perform a malicious action when executed [DMC-CBC-ATTACK]. Since
28 Other full disk encryption systems like dm-crypt cover all filesystem metadata,
31 time. For dm-crypt and other filesystems that build upon the Linux block IO
32 layer, the dm-integrity or dm-verity subsystems [DM-INTEGRITY, DM-VERITY]
34 These can also be combined with dm-crypt [CRYPTSETUP2].
44 ----------------
46 On Linux, the MTD (Memory Technology Devices) subsystem provides a uniform
[all …]
|
| D | ubifs.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 UBIFS file-system stands for UBI File System. UBI stands for "Unsorted
11 Block Images". UBIFS is a flash file system, which means it is designed
12 to work with flash devices. It is important to understand, that UBIFS
13 is completely different to any traditional file-system in Linux, like
14 Ext2, XFS, JFS, etc. UBIFS represents a separate class of file-systems
16 file-system of this class is JFFS2.
21 1 MTD devices represent flash devices and they consist of eraseblocks of
24 2 MTD devices support 3 main operations - read from some offset within an
26 eraseblock. Block devices support 2 main operations - read a whole
[all …]
|
| /Documentation/driver-api/mtd/ |
| D | spi-nor.rst | 5 How to propose a new flash addition
6 -----------------------------------
9 Serial Flash Discoverable Parameter (SFDP) standard. SFDP describes
10 the functional and feature capabilities of serial flash devices in a
11 standard set of internal read-only parameter tables.
14 flash's parameters and settings. If the flash defines the SFDP tables
15 it's likely that you won't need a flash entry at all, and instead
16 rely on the generic flash driver which probes the flash solely based
17 on its SFDP data. All one has to do is to specify the "jedec,spi-nor"
20 There are cases however where you need to define an explicit flash
[all …]
|
| D | spi-intel.rst | 2 Upgrading BIOS using spi-intel
5 Many Intel CPUs like Baytrail and Braswell include SPI serial flash host
7 Since contents of the SPI serial flash is crucial for machine to function,
9 avoid accidental (or on purpose) overwrite of the content.
11 Not all manufacturers protect the SPI serial flash, mainly because it
14 The spi-intel driver makes it possible to read and write the SPI serial
15 flash, if certain protection bits are not set and locked. If it finds
16 any of them set, the whole MTD device is made read-only to prevent
17 partial overwrites. By default the driver exposes SPI serial flash
18 contents as read-only but it can be changed from kernel command line,
[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
6 those modes are supported by LED class (see Documentation/leds/leds-class.rst)
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)
18 - flash_brightness
[all …]
|
| D | leds-lm3556.rst | 6 1.5 A Synchronous Boost LED Flash Driver w/ High-Side Current Source
10 - Daniel Jeong
12 Contact:Daniel Jeong(daniel.jeong-at-ti.com, gshark.jeong-at-gmail.com)
15 -----------
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
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | qcom,spmi-flash-led.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/qcom,spmi-flash-led.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Flash LED device inside Qualcomm Technologies, Inc. PMICs
10 - Fenglin Wu <quic_fenglinw@quicinc.com>
13 Flash LED controller is present inside some Qualcomm Technologies, Inc. PMICs.
14 The flash LED module can have different number of LED channels supported
18 will be split symmetrically on each channel and they will be enabled and
24 - enum:
[all …]
|
| D | common.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacek Anaszewski <jacek.anaszewski@gmail.com>
11 - Pavel Machek <pavel@ucw.cz>
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.
25 led-sources:
30 $ref: /schemas/types.yaml#/definitions/uint32-array
[all …]
|
| D | kinetic,ktd2692.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: KTD2692 Flash LED Driver from Kinetic Technologies
10 - Markuss Broks <markuss.broks@gmail.com>
13 KTD2692 is the ideal power solution for high-power flash LEDs.
14 It uses ExpressWire single-wire programming for maximum flexibility.
16 The ExpressWire interface through CTRL pin can control LED on/off and
17 enable/disable the IC, Movie(max 1/3 of Flash current) / Flash mode current,
18 Flash timeout, LVP(low voltage protection).
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | mtd-physmap.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mtd/mtd-physmap.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
10 - Rob Herring <robh@kernel.org>
13 Flash chips (Memory Technology Devices) are often used for solid state
14 file systems on embedded devices.
17 - $ref: mtd.yaml#
18 - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml#
[all …]
|
| D | davinci-nand.txt | 7 Davinci DM646x - https://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf
8 Kestone - https://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf
12 - compatible: "ti,davinci-nand"
13 "ti,keystone-nand"
15 - reg: Contains 2 offset/length values:
16 - offset and length for the access window.
17 - offset and length for accessing the AEMIF
20 - ti,davinci-chipselect: number of chipselect. Indicates on the
23 Can be in the range [0-3].
27 - ti,davinci-mask-ale: mask for ALE. Needed for executing address
[all …]
|
| D | lpc32xx-slc.txt | 4 - compatible: "nxp,lpc3220-slc"
5 - reg: Address and size of the controller
6 - nand-on-flash-bbt: Use bad block table on flash
7 - gpios: GPIO specification for NAND write protect
11 - nxp,wdr-clks: Delay before Ready signal is tested on write (W_RDY)
12 - nxp,rdr-clks: Delay before Ready signal is tested on read (R_RDY)
15 - nxp,wwidth: Write pulse width (W_WIDTH)
16 - nxp,whold: Write hold time (W_HOLD)
17 - nxp,wsetup: Write setup time (W_SETUP)
18 - nxp,rwidth: Read pulse width (R_WIDTH)
[all …]
|
| 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
10 - compatible : Should be "nxp,lpc1773-spifi"
11 - reg : the first contains the register location and length,
13 - reg-names: Should contain the reg names "spifi" and "flash"
14 - interrupts : Should contain the interrupt for the device
15 - clocks : The clocks needed by the SPIFI controller
16 - clock-names : Should contain the clock names "spifi" and "reg"
[all …]
|
| /Documentation/devicetree/bindings/spi/ |
| D | amlogic,meson6-spifc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/spi/amlogic,meson6-spifc.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Amlogic Meson SPI Flash Controller
11 - Neil Armstrong <neil.armstrong@linaro.org>
14 - $ref: spi-controller.yaml#
18 NOR memories, without DMA support and a 64-byte unified transmit /
24 - amlogic,meson6-spifc # SPI Flash Controller on Meson6 and compatible SoCs
25 - amlogic,meson-gxbb-spifc # SPI Flash Controller on GXBB and compatible SoCs
[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";
12 - reg: The base address of the CF chip select banks. Depending on
15 - cavium,bus-width: The width of the connection to the CF devices. Valid
18 - cavium,true-ide: Optional, if present the CF connection is in True IDE mode.
20 - cavium,dma-engine-handle: Optional, a phandle for the DMA Engine connected
24 compact-flash@5,0 {
25 compatible = "cavium,ebt3000-compact-flash";
[all …]
|
| /Documentation/gpu/amdgpu/ |
| D | flashing.rst | 6 ----
10 used for the flash process.
12 The IFWI flash process is:
14 1. Ensure the IFWI image is intended for the dGPU on the system.
16 3. "Read" from the `psp_vbflash` sysfs file to initiate the flash process.
17 4. Poll the `psp_vbflash_status` sysfs file to determine when the flash process completes.
19 USB-C PD F/W
20 ------------
21 On GPUs that support flashing an updated USB-C PD firmware image, the process
25 …irmware payload stored in `/lib/firmware/amdgpu` to the sysfs file will initiate the flash process.
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | fsl,ifc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/fsl/fsl,ifc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: FSL/NXP Integrated Flash Controller
10 - Shawn Guo <shawnguo@kernel.org>
13 NXP's integrated flash controller (IFC) is an advanced version of the
16 external memory types, such as NAND flash (SLC and MLC), NOR flash, EPROM,
17 SRAM and other memories where address and data are shared on a bus.
21 pattern: "^memory-controller@[0-9a-f]+$"
[all …]
|
12345678