Home
last modified time | relevance | path

Searched +full:non +full:- +full:flash (Results 1 – 25 of 496) sorted by relevance

12345678910>>...20

/linux/Documentation/ABI/testing/
H A Dsysfs-class-mtd4 Contact: linux-mtd@lists.infradead.org
12 Contact: linux-mtd@lists.infradead.org
16 physical/simulated flash devices, partitions on a flash
17 device, or concatenated flash devices.
22 Contact: linux-mtd@lists.infradead.org
24 These directories provide the corresponding read-only device
30 Contact: linux-mtd@lists.infradead.org
34 read-write device so <minor> will be even.
39 Contact: linux-mtd@lists.infradead.org
42 to the read-only variant of the MTD device (in
[all …]
H A Dsysfs-bus-spi-devices-spi-nor1 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 …]
/linux/drivers/mtd/chips/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "RAM/ROM/Flash chip drivers"
6 tristate "Detect flash chips by Common Flash Interface (CFI) probe"
10 The Common Flash Interface specification was developed by Intel,
11 AMD and other flash manufactures that provides a universal method
12 for probing the capabilities of flash devices. If you wish to
13 support any device that is CFI-compliant, you need to enable this
18 tristate "Detect non-CFI AMD/JEDEC-compatible flash chips"
22 This option enables JEDEC-style probing of flash chips which are not
23 compatible with the Common Flash Interface, but will use the common
[all …]
/linux/drivers/mtd/devices/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "Self-contained MTD device drivers"
12 These devices come in memory configurations from 32M - 1G. If you
41 tristate "DEC MS02-NV NVRAM module support"
44 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
45 backed-up NVRAM module. The module was originally meant as an NFS
52 The module will be called ms02-nv.
59 Sometimes DataFlash chips are packaged inside MMC-format
66 This adds an extra check when data is written to the flash.
77 one-time-programmable (OTP) data. The first half may be written
[all …]
H A Dspear_smi.c2 * SMI (Serial Memory Controller) device driver for Serial NOR Flash on
90 /* flash opcodes */
93 /* Flash Device Ids maintenance section */
95 /* data structure to maintain flash ids from different vendors */
157 * struct spear_smi - Structure for SMI Device
165 * @cmd_complete: queue to wait for command completion of NOR-flash.
167 * @flash: separate structure for each Serial NOR-flash attached to SMI.
178 struct spear_snor_flash *flash[MAX_NUM_FLASH_CHIP]; member
182 * struct spear_snor_flash - Structure for Serial NOR Flash
184 * @bank: Bank number(0, 1, 2, 3) for each NOR-flash.
[all …]
/linux/Documentation/leds/
H A Dleds-class-flash.rst2 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 …]
/linux/drivers/mtd/maps/
H A Dsc520cdp.c1 // SPDX-License-Identifier: GPL-2.0-or-later
2 /* sc520cdp.c -- MTD map driver for AMD SC520 Customer Development Platform
4 * Copyright (C) 2001 Sysgo Real-Time Solutions GmbH
7 * from AMD. It has two banks of 32-bit Flash ROM, each 8 Megabytes in size,
8 * and up to 512 KiB of 8-bit DIL Flash ROM.
22 ** The Embedded Systems BIOS decodes the first FLASH starting at
24 ** the flash at this location causes the A22 address line to be high
26 ** order address line on the raw flash devices themselves!!
27 ** This causes the top HALF of the flash to be accessed first. Beyond
28 ** the physical limits of the flash, the flash chip aliases over (to
[all …]
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
7 bool "Support non-linear mappings of flash chips"
10 paged mappings of flash chips.
13 tristate "Flash device in physical memory map"
16 This provides a 'mapping' driver which allows the NOR Flash and
19 the physical address and size of the flash chips on your
21 with config options or at run-time.
38 hex "Physical start address of flash mapping"
42 This is the physical memory location at which the flash chips
48 hex "Physical length of flash mapping"
[all …]
/linux/Documentation/arch/arm/sa1100/
H A Dassabet.rst2 The Intel Assabet (SA-1110 evaluation) board
13 -------------------
25 -----------------------
39 John Dorsey has produced add-on patches to add support for Assabet and
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/
57 - ftp://ftp.handhelds.org/pub/linux/arm/sa-1100-patches/
59 Look for redboot-assabet*.tgz. Some installation infos are provided in
60 redboot-assabet*.txt.
[all …]
/linux/drivers/mtd/spi-nor/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
17 Many flash memories support erasing small (4096 B) sectors. Depending
20 Changing a small part of the flash's contents is usually faster with
35 flashes at boot-up.
37 Depending on the flash chip this either clears the block protection
41 of your SPI flash. This is only to keep backwards compatibility.
47 power-up or a reset the flash is software write protected by
52 which have non-volatile write protection bits.
55 the flash either the block protection bits are cleared or a
64 SPI flashes will not be changed. If your flash is software write
[all …]
/linux/include/media/
H A Dv4l2-flash-led-class.h1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * V4L2 flash LED sub-device registration helpers.
12 #include <media/v4l2-ctrls.h>
13 #include <media/v4l2-subdev.h>
21 * struct v4l2_flash_ctrl_data - flash control initialization data, filled
22 * basing on the features declared by the LED flash
25 * @cid: contains v4l2 flash control id if the config
34 * struct v4l2_flash_ops - V4L2 flash operations
36 * @external_strobe_set: Setup strobing the flash by hardware pin state
53 * struct v4l2_flash_config - V4L2 Flash sub-device initialization data
[all …]
/linux/Documentation/networking/devlink/
H A Ddevlink-flash.rst1 .. 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 …]
H A Ddevlink-selftests.rst1 .. 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 …]
/linux/Documentation/devicetree/bindings/mtd/
H A Dmtd-physmap.yaml1 # 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
17 - $ref: mtd.yaml#
18 - $ref: /schemas/memory-controllers/mc-peripheral-props.yaml#
23 - items:
[all …]
/linux/drivers/thunderbolt/
H A Ddma_port.c1 // SPDX-License-Identifier: GPL-2.0
48 * struct tb_dma_port - DMA control port
68 u64 route = tb_cfg_get_route(pkg->buffer) & ~BIT_ULL(63); in dma_port_match()
70 if (pkg->frame.eof == TB_CFG_PKG_ERROR) in dma_port_match()
72 if (pkg->frame.eof != req->response_type) in dma_port_match()
74 if (route != tb_cfg_get_route(req->request)) in dma_port_match()
76 if (pkg->frame.size != req->response_size) in dma_port_match()
84 memcpy(req->response, pkg->buffer, req->response_size); in dma_port_copy()
107 return -ENOMEM; in dma_port_read()
109 req->match = dma_port_match; in dma_port_read()
[all …]
/linux/include/linux/mtd/
H A Dhyperbus.h1 /* SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2019 Texas Instruments Incorporated - https://www.ti.com/
28 * struct hyperbus_device - struct representing HyperBus slave device
29 * @map: map_info struct for accessing MMIO HyperBus flash memory
47 * struct hyperbus_ops - struct representing custom HyperBus operations
48 * @read16: read 16 bit of data from flash in a single burst. Used to read
49 * from non default address space, such as ID/CFI space
50 * @write16: write 16 bit of data to flash in a single burst. Used to
51 * send cmd to flash or write single 16 bit word at a time.
52 * @copy_from: copy data from flash memory
[all …]
H A Dubi.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
14 #include <mtd/ubi-user.h>
17 #define UBI_ALL -1
26 * enum ubi_open_mode - UBI volume open mode constants.
28 * UBI_READONLY: read-only mode
29 * UBI_READWRITE: read-write mode
31 * UBI_METAONLY: modify only the volume meta-data,
42 * struct ubi_volume_info - UBI volume description data structure.
50 * @corrupted: non-zero if the volume is corrupted (static volumes only)
51 * @upd_marker: non-zero if the volume has update marker set
[all …]
H A Dxip.h1 /* SPDX-License-Identifier: GPL-2.0-only */
26 * Function that are modifying the flash state away from array mode must
27 * obviously not be running from flash. The __xipram is therefore marking
37 * won't be available when used (flash not in array mode).
41 * return non zero when any hardware interrupt is pending.
64 #include <asm/mtd-xip.h>
70 #warning "your system will therefore be unresponsive when writing or erasing flash"
/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Dbrcm,bcm963xx-imagetag.txt4 Some Broadcom BCM63XX SoC based devices contain additional, non discoverable
5 partitions or non standard bootloader partition sizes. For these a mixed layout
12 - compatible : must be "brcm,bcm963xx-imagetag"
16 flash@1e000000 {
17 compatible = "cfi-flash";
19 bank-width = <2>;
22 compatible = "fixed-partitions";
23 #address-cells = <1>;
24 #size-cells = <1>;
28 read-only;
[all …]
/linux/arch/arm/boot/dts/marvell/
H A Ddove-d2plug.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
20 compatible = "gpio-leds";
21 pinctrl-0 = <&pmx_gpio_0 &pmx_gpio_1 &pmx_gpio_2>;
22 pinctrl-names = "default";
24 led-wlan-ap {
25 label = "wlan-ap";
29 led-wlan-act {
30 label = "wlan-act";
34 led-bluetooth-act {
[all …]
H A Ddove-d3plug.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
20 compatible = "gpio-leds";
21 pinctrl-0 = <&pmx_gpio_0 &pmx_gpio_1 &pmx_gpio_2>;
22 pinctrl-names = "default";
24 led-wlan-act {
25 label = "wlan-act";
29 led-wlan-ap {
30 label = "wlan-ap";
34 led-status {
[all …]
/linux/arch/arm/
H A DKconfig-nommu1 # SPDX-License-Identifier: GPL-2.0
3 # Kconfig for uClinux(non-paged MM) depend configurations
8 bool "Set flash/sdram size and base addr"
22 hex 'FLASH Base Address' if SET_MEM_PARAM
27 hex 'FLASH Size' if SET_MEM_PARAM
37 used instead of the auto-probing which utilizes the register.
45 occupied by read-only memory depending on H/W design.
47 If the region contains read-write memory, say 'n' here.
/linux/Documentation/driver-api/memory-devices/
H A Dti-gpmc.rst1 .. SPDX-License-Identifier: GPL-2.0
12 * Asynchronous, synchronous, and page mode burst NOR flash devices
13 NAND flash
14 * Pseudo-SRAM devices
85 4. read async non-muxed
107 6. read sync non-muxed
131 8. write async non-muxed
157 10. write sync non-muxed
/linux/Documentation/firmware-guide/acpi/dsd/
H A Dleds.rst1 .. SPDX-License-Identifier: GPL-2.0
14 Referring to LEDs in Device tree is documented in [video-interfaces], in
15 "flash-leds" property documentation. In short, LEDs are directly referred to by
20 the same mechanism on ACPI is not possible. A mechanism to refer to non-device
21 ACPI nodes is documented in [data-node-ref].
44 ToUUID("dbb8e3e6-5886-4ba6-8795-1319f52a966b"),
51 ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
54 Package () { "flash-max-microamp", 1000000 },
55 Package () { "flash-timeout-us", 200000 },
56 Package () { "led-max-microamp", 100000 },
[all …]
/linux/fs/ubifs/
H A Dubifs.h1 /* SPDX-License-Identifier: GPL-2.0-only */
5 * Copyright (C) 2006-2008 Nokia Corporation
26 #include <linux/backing-dev.h>
38 #include "ubifs-media.h"
48 #define UBIFS_BLOCKS_PER_PAGE_SHIFT (PAGE_SHIFT - UBIFS_BLOCK_SHIFT)
56 * least 2 LEBs: one for the index head and one for in-the-gaps method (which
62 /* Minimum amount of data UBIFS writes to the flash */
66 * Currently we do not support inode number overlapping and re-using, so this
69 * 64-bit inode numbers, but this means more overhead.
83 /* Maximum possible inode number (only 32-bit inodes are supported now) */
[all …]

12345678910>>...20