deleted>Frq08988 |
Registered User No edit summary |
||
| Line 1: | Line 1: | ||
== Article purpose == | == Article purpose == | ||
This article explains how to configure the [[QUADSPI internal peripheral|'''QUADSPI''' internal peripheral]] when it is assigned to the Linux<sup>®</sup> OS. In that case, it is controlled by the [[MTD overview|MTD framework]]. | This article explains how to configure the [[QUADSPI internal peripheral|'''QUADSPI''' internal peripheral]] when it is assigned to the Linux<sup>®</sup> OS. In that case, it is controlled by the [[MTD overview|MTD framework]]. | ||
| Line 107: | Line 98: | ||
<references /> | <references /> | ||
<noinclude> | |||
{{ArticleBasedOnModel | [[Peripheral or framework device tree configuration model]]}} | |||
[[Category:Device tree configuration]] | |||
[[Category:Mass storage]] | |||
</noinclude> | |||
Revision as of 14:23, 16 September 2019
1. Article purpose[edit source]
This article explains how to configure the QUADSPI internal peripheral when it is assigned to the Linux® OS. In that case, it is controlled by the MTD framework.
The configuration is performed using the device tree mechanism that provides a hardware description of the QUADSPI peripheral, used by the STM32 QUADSPI Linux driver and by the MTD framework.
2. DT bindings documentation[edit source]
The QUADSPI device tree bindings are composed by:
- generic spi NOR Flash memory bindings [1].
- QUADSPI driver bindings [2].
3. DT configuration[edit source]
This hardware description is a combination of the STM32 microprocessor device tree files (.dtsi extension) and board device tree files (.dts extension). See the Device tree for an explanation of the device tree file split.
STM32CubeMX can be used to generate the board device tree. Refer to How to configure the DT using STM32CubeMX for more details.
3.1. DT configuration (STM32 level)[edit source]
The QUADSPI peripheral node is located in stm32mp157c.dtsi[3] file.
qspi: spi@58003000 { Template:Highlight compatible = "st,stm32f469-qspi"; reg = <0x58003000 0x1000>, Template:Highlight <0x70000000 0x10000000>; Template:Highlight reg-names = "qspi", "qspi_mm"; interrupts = <GIC_SPI 92 IRQ_TYPE_LEVEL_HIGH>; Template:Highlight dmas = <&mdma1 22 0x10 0x100A02 0x0 0x0 0x0>, Template:Highlight <&mdma1 22 0x10 0x100A08 0x0 0x0 0x0>; dma-names = "tx", "rx"; clocks = <&rcc QSPI_K>; resets = <&rcc QSPI_R>; status = "disabled"; };
3.2. DT configuration (board level)[edit source]
The QUADSPI peripheral may connect a maximum of 2 spi NOR Flash memories.
Spi NOR Flash memory nodes [1] must be children of the QUADSPI peripheral node.
&qspi { Template:Highlight pinctrl-names = "default", "sleep"; Template:Highlight pinctrl-0 = <&qspi_clk_pins_a &qspi_bk1_pins_a &qspi_bk2_pins_a>; pinctrl-1 = <&qspi_clk_sleep_pins_a &qspi_bk1_sleep_pins_a &qspi_bk2_sleep_pins_a>; reg = <0x58003000 0x1000>, <0x70000000 0x4000000>; Template:Highlight #address-cells = <1>; #size-cells = <0>; status = "okay"; Template:Highlight
flash0: mx66l51235l@0 { compatible = "jdec,spi-nor"; reg = <0>; Template:Highlight spi-rx-bus-width = <4>; Template:Highlight spi-max-frequency = <108000000>; Template:Highlight #address-cells = <1>; #size-cells = <1>; }; };
3.3. DT configuration example[edit source]
The below example shows how to configure the QUADSPI peripheral when 2 spi NOR Flash memories are connected.
&qspi { Template:Highlight pinctrl-names = "default", "sleep"; Template:Highlight pinctrl-0 = <&qspi_clk_pins_a &qspi_bk1_pins_a &qspi_bk2_pins_a>; pinctrl-1 = <&qspi_clk_sleep_pins_a &qspi_bk1_sleep_pins_a &qspi_bk2_sleep_pins_a>; reg = <0x58003000 0x1000>, <0x70000000 0x4000000>; Template:Highlight #address-cells = <1>; #size-cells = <0>; status = "okay";
flash0: mx66l51235l@0 { Template:Highlight compatible = "jdec,spi-nor"; reg = <0>; spi-rx-bus-width = <4>; spi-max-frequency = <108000000>; #address-cells = <1>; #size-cells = <1>; };
flash1: mx66l51235l@1 { Template:Highlight compatible = "jdec,spi-nor"; reg = <1>; spi-rx-bus-width = <4>; spi-max-frequency = <108000000>; #address-cells = <1>; #size-cells = <1>; }; };
4. How to configure the DT using STM32CubeMX[edit source]
The STM32CubeMX tool can be used to configure the STM32MPU device and get the corresponding platform configuration device tree files.
The STM32CubeMX may not support all the properties described in the above DT bindings documentation paragraph. If so, the tool inserts user sections in the generated device tree. These sections can then be edited to add some properties and they are preserved from one generation to another. Refer to STM32CubeMX user manual for further information.
5. References[edit source]
Please refer to the following links for full description: