Home
last modified time | relevance | path

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

12345678910>>...20

/linux-5.10/Documentation/ABI/testing/
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 thie MTD device (in
[all …]
/linux-5.10/drivers/mtd/chips/
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-5.10/drivers/mtd/devices/
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 …]
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-5.10/Documentation/leds/
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-5.10/Documentation/networking/devlink/
Dice.rst1 .. SPDX-License-Identifier: GPL-2.0
15 .. list-table:: devlink info versions implemented
18 * - Name
19 - Type
20 - Example
21 - Description
22 * - ``board.id``
23 - fixed
24 - K65390-000
25 - The Product Board Assembly (PBA) identifier of the board.
[all …]
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 …]
/linux-5.10/drivers/mtd/maps/
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 …]
/linux-5.10/Documentation/arm/sa1100/
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-5.10/Documentation/devicetree/bindings/mtd/
Dmtd-physmap.txt1 CFI or JEDEC memory-mapped NOR flash, MTD-RAM (NVRAM...)
3 Flash chips (Memory Technology Devices) are often used for solid state
6 - compatible : should contain the specific model of mtd chip(s)
7 used, if known, followed by either "cfi-flash", "jedec-flash",
8 "mtd-ram" or "mtd-rom".
9 - reg : Address range(s) of the mtd chip(s)
11 non-identical chips can be described in one node.
12 - bank-width : Width (in bytes) of the bank. Equal to the
14 - device-width : (optional) Width of a single mtd chip. If
15 omitted, assumed to be equal to 'bank-width'.
[all …]
Dbrcm,brcmnand.txt3 The Broadcom Set-Top Box NAND controller supports low-level access to raw NAND
4 flash chips. It has a memory-mapped register interface for both control
6 paired with a custom DMA engine (inventively named "Flash DMA") which supports
15 - compatible : May contain an SoC-specific compatibility string (see below)
16 to account for any SoC-specific hardware bits that may be
21 string, like "brcm,brcmnand-v7.0"
23 brcm,brcmnand-v2.1
24 brcm,brcmnand-v2.2
25 brcm,brcmnand-v4.0
26 brcm,brcmnand-v5.0
[all …]
/linux-5.10/include/media/
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-5.10/Documentation/devicetree/bindings/mtd/partitions/
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-5.10/arch/arm/boot/dts/
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 wlan-ap {
25 label = "wlan-ap";
29 wlan-act {
30 label = "wlan-act";
34 bluetooth-act {
[all …]
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 wlan-act {
25 label = "wlan-act";
29 wlan-ap {
30 label = "wlan-ap";
41 compatible = "simple-bus";
[all …]
/linux-5.10/include/linux/mtd/
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 …]
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"
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 …]
/linux-5.10/drivers/thunderbolt/
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-5.10/arch/arm/
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-5.10/drivers/mtd/spi-nor/
Dcore.h1 /* SPDX-License-Identifier: GPL-2.0 */
86 * struct spi_nor_erase_type - Structure to describe a SPI NOR erase type
93 * @idx: Erase Type index as sorted in the Basic Flash Parameter
107 * struct spi_nor_erase_command - Used for non-uniform erases
110 * are run-length encoded.
125 * struct spi_nor_erase_region - Structure to describe a SPI NOR erase region
129 * the last in the SPI NOR flash memory and to indicate
141 #define SNOR_ERASE_TYPE_MASK GENMASK_ULL(SNOR_ERASE_TYPE_MAX - 1, 0)
147 #define SNOR_ERASE_FLAGS_MASK GENMASK_ULL(SNOR_ERASE_FLAGS_MAX - 1, 0)
150 * struct spi_nor_erase_map - Structure to describe the SPI NOR erase map
[all …]
Dxilinx.c1 // SPDX-License-Identifier: GPL-2.0
7 #include <linux/mtd/spi-nor.h>
12 /* Xilinx S3AN Internal Flash */
21 * This code converts an address to the Default Address Mode, that has non
23 * mode supported by Xilinx tools, it can access the whole flash area and
24 * changing over to the Power-of-two mode is irreversible and corrupts the
33 offset = addr % nor->page_size; in s3an_convert_addr()
34 page = addr / nor->page_size; in s3an_convert_addr()
35 page <<= (nor->page_size > 512) ? 10 : 9; in s3an_convert_addr()
45 ret = spi_nor_xread_sr(nor, nor->bouncebuf); in xilinx_nor_setup()
[all …]
/linux-5.10/Documentation/driver-api/memory-devices/
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-5.10/Documentation/devicetree/bindings/leds/
Dcommon.yaml1 # 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 …]
/linux-5.10/drivers/net/wireless/intersil/hostap/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
39 support cards that don't have firmware in flash, such as D-Link
40 DWL-520 rev E and D-Link DWL-650 rev P.
46 bool "Support for non-volatile firmware download"
49 Allow Host AP driver to write firmware images to the non-volatile
50 card memory, i.e. flash memory that survives power cycling.

12345678910>>...20