Searched +full:spi +full:- +full:nor (Results 1 – 25 of 51) sorted by relevance
123
| /Documentation/devicetree/bindings/spi/ |
| D | mediatek,spi-mtk-nor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/mediatek,spi-mtk-nor.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Serial NOR flash controller for MediaTek ARM SoCs 10 - Bayi Cheng <bayi.cheng@mediatek.com> 11 - Chuanhong Guo <gch981213@gmail.com> 14 This spi controller support single, dual, or quad mode transfer for 15 SPI NOR flash. There should be only one spi slave device following 16 generic spi bindings. It's not recommended to use this controller [all …]
|
| D | cdns,xspi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 2 # Copyright 2020-21 Cadence 4 --- 5 $id: http://devicetree.org/schemas/spi/cdns,xspi.yaml# 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Parshuram Thombare <pthombar@cadence.com> 14 The XSPI controller allows SPI protocol communication in 16 read/write access to slaves such as SPI-NOR flash. 21 - cdns,xspi-nor 22 - marvell,cn10-xspi-nor [all …]
|
| D | aspeed,ast2600-fmc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/aspeed,ast2600-fmc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com> 11 - Cédric Le Goater <clg@kaod.org> 15 SPI) of the AST2400, AST2500 and AST2600 SOCs. 18 - $ref: spi-controller.yaml# 23 - aspeed,ast2600-fmc 24 - aspeed,ast2600-spi [all …]
|
| 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# 17 The Meson SPIFC is a controller optimized for communication with SPI 18 NOR memories, without DMA support and a 64-byte unified transmit / 24 - amlogic,meson6-spifc # SPI Flash Controller on Meson6 and compatible SoCs [all …]
|
| D | hpe,gxp-spifi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/hpe,gxp-spifi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: HPE GXP spi controller flash interface 10 - Nick Hawkins <nick.hawkins@hpe.com> 11 - Jean-Marie Verdun <verdun@hpe.com> 14 - $ref: spi-controller.yaml# 18 const: hpe,gxp-spifi 22 - description: cfg registers [all …]
|
| D | cdns,qspi-nor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/cdns,qspi-nor.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Cadence Quad SPI controller 10 - Vaishnav Achath <vaishnav.a@ti.com> 13 - $ref: spi-controller.yaml# 14 - if: 18 const: xlnx,versal-ospi-1.0 21 - power-domains [all …]
|
| D | qcom,spi-qcom-qspi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/qcom,spi-qcom-qspi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Bjorn Andersson <bjorn.andersson@linaro.org> 12 description: The QSPI controller allows SPI protocol communication in single, 14 as NOR flash. 17 - $ref: /schemas/spi/spi-controller.yaml# 22 - enum: 23 - qcom,sc7180-qspi [all …]
|
| D | cdns,qspi-nor-peripheral-props.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/cdns,qspi-nor-peripheral-props.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Peripheral-specific properties for the Cadence QSPI controller. 10 See spi-peripheral-props.yaml for more info. 13 - Vaishnav Achath <vaishnav.a@ti.com> 16 # cdns,qspi-nor.yaml 17 cdns,read-delay: 22 cdns,tshsl-ns: [all …]
|
| D | socionext,f-ospi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/socionext,f-ospi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 memories using the SPI communication interface. 14 - Kunihiko Hayashi <hayashi.kunihiko@socionext.com> 17 - $ref: spi-controller.yaml# 21 const: socionext,f-ospi 29 num-cs: 34 - compatible [all …]
|
| D | nvidia,tegra114-spi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/nvidia,tegra114-spi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: NVIDIA Tegra114 SPI controller 10 - Thierry Reding <thierry.reding@gmail.com> 11 - Jon Hunter <jonathanh@nvidia.com> 16 - const: nvidia,tegra114-spi 17 - items: 18 - enum: [all …]
|
| D | nuvoton,wpcm450-fiu.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/spi/nuvoton,wpcm450-fiu.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jonathan Neuschäfer <j.neuschaefer@gmx.net> 13 - $ref: /schemas/spi/spi-controller.yaml# 17 const: nuvoton,wpcm450-fiu 21 - description: FIU registers 22 - description: Memory-mapped flash contents 24 reg-names: [all …]
|
| D | fsl,spi-fsl-qspi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/fsl,spi-fsl-qspi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Han Xu <han.xu@nxp.com> 13 - $ref: spi-controller.yaml# 18 - enum: 19 - fsl,vf610-qspi 20 - fsl,imx6sx-qspi 21 - fsl,imx7d-qspi [all …]
|
| D | spi-nxp-fspi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/spi-nxp-fspi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Han Xu <han.xu@nxp.com> 11 - Kuldeep Singh <singh.kuldeep87k@gmail.com> 14 - $ref: spi-controller.yaml# 19 - enum: 20 - nxp,imx8dxl-fspi 21 - nxp,imx8mm-fspi [all …]
|
| D | atmel,quadspi.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/spi/atmel,quadspi.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Tudor Ambarus <tudor.ambarus@linaro.org> 13 - $ref: spi-controller.yaml# 18 - atmel,sama5d2-qspi 19 - microchip,sam9x60-qspi 20 - microchip,sama7g5-qspi 21 - microchip,sama7g5-ospi [all …]
|
| D | rockchip-sfc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/spi/rockchip-sfc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Heiko Stuebner <heiko@sntech.de> 11 - Chris Morgan <macromorgan@hotmail.com> 14 - $ref: spi-controller.yaml# 32 - description: Bus Clock 33 - description: Module Clock 35 clock-names: [all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | hisilicon,fmc-spi-nor.txt | 1 HiSilicon SPI-NOR Flash Controller 4 - compatible : Should be "hisilicon,fmc-spi-nor" and one of the following strings: 5 "hisilicon,hi3519-spi-nor" 6 - address-cells : Should be 1. 7 - size-cells : Should be 0. 8 - reg : Offset and length of the register set for the controller device. 9 - reg-names : Must include the following two entries: "control", "memory". 10 - clocks : handle to spi-nor flash controller clock. 13 spi-nor-controller@10000000 { 14 compatible = "hisilicon,hi3519-spi-nor", "hisilicon,fmc-spi-nor"; [all …]
|
| 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 …]
|
| 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 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" 19 - resets : phandle + reset specifier [all …]
|
| D | st-fsm.txt | 1 * ST-Microelectronics SPI FSM Serial (NOR) Flash Controller 4 - compatible : Should be "st,spi-fsm" 5 - reg : Contains register's location and length. 6 - reg-names : Should contain the reg names "spi-fsm" 7 - interrupts : The interrupt number 8 - pinctrl-0 : Standard Pinctrl phandle (see: pinctrl/pinctrl-bindings.txt) 11 - st,syscfg : Phandle to boot-device system configuration registers 12 - st,boot-device-reg : Address of the aforementioned boot-device register(s) 13 - st,boot-device-spi : Expected boot-device value if booted via this device 17 compatible = "st,spi-fsm"; [all …]
|
| D | mtd.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Miquel Raynal <miquel.raynal@bootlin.com> 11 - Richard Weinberger <richard@nod.at> 21 User-defined MTD device name. Can be used to assign user friendly 26 '#address-cells': 29 '#size-cells': 36 - compatible 39 "@[0-9a-f]+$": [all …]
|
| /Documentation/ABI/testing/ |
| 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 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. 22 What: /sys/bus/spi/devices/.../spi-nor/partname 25 Contact: linux-mtd@lists.infradead.org 26 Description: (RO) Part name of the SPI NOR flash. [all …]
|
| /Documentation/driver-api/mtd/ |
| D | spi-nor.rst | 2 SPI NOR framework 6 ----------------------------------- 8 Most SPI NOR flashes comply with the JEDEC JESD216 11 standard set of internal read-only parameter tables. 13 The SPI NOR driver queries the SFDP tables in order to determine the 17 on its SFDP data. All one has to do is to specify the "jedec,spi-nor" 28 ----------------------------- 31 section, after the ``---`` marker. 37 frequency using the Z (put compatible) SPI controller. 41 root@1:~# cat /sys/bus/spi/devices/spi0.0/spi-nor/partname [all …]
|
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 spi-intel 12 spi-nor
|
| /Documentation/devicetree/bindings/arm/ |
| D | microchip,sparx5.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Lars Povlsen <lars.povlsen@microchip.com> 13 The Microchip Sparx5 SoC is a ARMv8-based used in a family of 14 gigabit TSN-capable gigabit switches. 16 The SparX-5 Ethernet switch family provides a rich set of switching 17 features such as advanced TCAM-based VLAN and QoS processing 19 TCAM-based frame processing using versatile content aware processor 27 - description: The Sparx5 pcb125 board is a modular board, [all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas,rpc-if.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/memory-controllers/renesas,rpc-if.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Renesas Reduced Pin Count Interface (RPC-IF) 10 - Sergei Shtylyov <sergei.shtylyov@gmail.com> 13 Renesas RPC-IF allows a SPI flash or HyperFlash connected to the SoC to 16 The flash chip itself should be represented by a subnode of the RPC-IF node. 19 - if it contains "jedec,spi-nor", then SPI is used; 20 - if it contains "cfi-flash", then HyperFlash is used. [all …]
|
123