| /freebsd/sys/contrib/device-tree/Bindings/mtd/partitions/ |
| H A 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
14 - compatible : (required) must be "redboot-fis"
15 - fis-index-block : (required) a index to the eraseblock containing
16 the FIS directory on this device. On a flash memory with 32KB
18 second eraseblock at 0x00008000 and so on.
22 flash@0 {
[all …]
|
| H A 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 …]
|
| H A 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 …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mtd/ |
| H A D | brcm,brcmnand.txt | 3 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
5 registers and for its data input/output buffer. On some SoCs, this controller is
6 paired with a custom DMA engine (inventively named "Flash DMA") which supports
10 available on a variety of Broadcom SoCs, including some BCM3xxx, BCM63xx, and
15 - compatible : May contain an SoC-specific compatibility string (see below)
16 to account for any SoC-specific hardware bits that may be
17 added on top of the base core controller.
21 string, like "brcm,brcmnand-v7.0"
23 brcm,brcmnand-v2.1
[all …]
|
| H A 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
4 file systems on embedded devices.
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
[all …]
|
| H A 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 …]
|
| H A D | gpmi-nand.txt | 1 * Freescale General-Purpose Media Interface (GPMI)
4 NAND flash chips.
7 - compatible : should be "fsl,<chip>-gpmi-nand", chip can be:
13 - reg : should contain registers location and length for gpmi and bch.
14 - reg-names: Should contain the reg names "gpmi-nand" and "bch"
15 - interrupts : BCH interrupt number.
16 - interrupt-names : Should be "bch".
17 - dmas: DMA specifier, consisting of a phandle to DMA controller node
19 Refer to dma.txt and fsl-mxs-dma.txt for details.
20 - dma-names: Must be "rx-tx".
[all …]
|
| H A 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
4 specific big-endian or mixed-endian memory access pattern.
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>
11 For the rest of the properties, see mtd-physmap.txt.
13 The device tree may optionally contain sub-nodes describing partitions of the
18 flash@50000000 {
19 compatible = "intel,ixp4xx-flash", "cfi-flash";
[all …]
|
| H A 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
9 - syscon : must be a phandle to the system controller
10 - bank-width : width in bytes of flash interface, should be <2>
12 For the rest of the properties, see mtd-physmap.yaml.
14 The device tree may optionally contain sub-nodes describing partitions of the
19 flash@30000000 {
20 compatible = "cortina,gemini-flash", "cfi-flash";
[all …]
|
| H A 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.
15 For the rest of the properties, see mtd-physmap.txt.
17 The device tree may optionally contain sub-nodes describing partitions of the
22 flash@34000000 {
23 compatible = "arm,versatile-flash", "cfi-flash";
[all …]
|
| H A 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
17 When a single partition is represented with a DT node (it depends on a used
20 hierarchical (multi-level) layouts and should be used if there is some
27 Deprecated: partitions defined in flash node
30 For backwards compatibility partitions as direct subnodes of the flash device are
|
| H A D | brcm,brcmnand.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Brian Norris <computersforpeace@gmail.com>
11 - Kamal Dasu <kdasu.kdev@gmail.com>
12 - William Zhang <william.zhang@broadcom.com>
15 The Broadcom Set-Top Box NAND controller supports low-level access to raw NAND
16 flash chips. It has a memory-mapped register interface for both control
17 registers and for its data input/output buffer. On some SoCs, this controller
18 is paired with a custom DMA engine (inventively named "Flash DMA") which
[all …]
|
| H A 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 …]
|
| H A D | jedec,spi-nor.txt | 1 * SPI NOR flash: ST M25Pxx (and similar) serial flash chips
4 - #address-cells, #size-cells : Must be present if the device has sub-nodes
6 - compatible : May include a device-specific string consisting of the
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
53 m25p05-nonjedec
54 m25p10-nonjedec
55 m25p20-nonjedec
56 m25p40-nonjedec
57 m25p80-nonjedec
[all …]
|
| H A D | jedec,spi-nor.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/mtd/jedec,spi-nor.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: SPI NOR flash ST M25Pxx (and similar) serial flash chips
10 - Rob Herring <robh@kernel.org>
13 - $ref: mtd.yaml#
14 - $ref: /schemas/spi/spi-peripheral-props.yaml#
19 - items:
20 - pattern: "^((((micron|spansion|st),)?\
[all …]
|
| H A 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 …]
|
| /freebsd/sys/contrib/device-tree/Bindings/leds/ |
| H A 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 …]
|
| H A D | leds-ktd2692.txt | 1 * Kinetic Technologies - KTD2692 Flash LED Driver
3 KTD2692 is the ideal power solution for high-power flash LEDs.
4 It uses ExpressWire single-wire programming for maximum flexibility.
6 The ExpressWire interface through CTRL pin can control LED on/off and
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.
14 - compatible : Should be "kinetic,ktd2692".
15 - ctrl-gpios : Specifier of the GPIO connected to CTRL pin.
16 - aux-gpios : Specifier of the GPIO connected to AUX pin.
[all …]
|
| H A 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-flas
[all...] |
| H A 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 …]
|
| /freebsd/sys/dev/bhnd/cores/chipc/ |
| H A D | chipc.h | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause
4 * Copyright (c) 2015-2016 Landon Fuller <landon@landonf.org>
26 * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
42 * Supported ChipCommon flash types.
45 CHIPC_FLASH_NONE = 0, /**< No flash, or a type unrecognized
47 CHIPC_PFLASH_CFI = 1, /**< CFI-compatible parallel flash */
48 CHIPC_SFLASH_ST = 2, /**< ST serial flash */
49 CHIPC_SFLASH_AT = 3, /**< Atmel serial flash */
50 CHIPC_QSFLASH_ST = 4, /**< ST quad-SPI flash */
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/memory-controllers/fsl/ |
| H A 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 …]
|
| H A D | ifc.txt | 1 Integrated Flash Controller
4 - name : Should be ifc
5 - compatible : should contain "fsl,ifc". The version of the integrated
6 flash controller can be found in the IFC_REV register at
9 - #address-cells : Should be either two or three. The first cell is the
12 - #size-cells : Either one or two, depending on how large each chipselect
14 - reg : Offset and length of the register set for the device
15 - interrupts: IFC may have one or two interrupts. If two interrupt
21 - little-endian : If this property is absent, the big-endian mode will
24 - ranges : Each range corresponds to a single chipselect, and covers
[all …]
|
| /freebsd/sys/powerpc/mpc85xx/ |
| H A D | lbc.h | 1 /*-
2 * SPDX-License-Identifier: BSD-2-Clause
4 * Copyright (c) 2006-2008, Juniper Networks, Inc.
23 * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
32 /* Maximum number of devices on Local Bus */
36 #define LBC85XX_BR(n) (0x0 + (8 * n)) /* Base register 0-7 */
37 #define LBC85XX_OR(n) (0x4 + (8 * n)) /* Options register 0-7 */
55 #define LBC85XX_FMR 0x0e0 /* Flash mode register */
56 #define LBC85XX_FIR 0x0e4 /* Flash instruction register */
57 #define LBC85XX_FCR 0x0e8 /* Flash command register */
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/spi/ |
| H A 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 …]
|