Lines Matching +full:sd +full:- +full:gpios

14 Since many disk devices (such as SD cards) are hotpluggable, the disk access
15 API provides IOCTLs to initialize and de-initialize the disk. They are
22 * :c:macro:`DISK_IOCTL_CTRL_DEINIT`: De-initialize the disk. Once this IOCTL
26 Init/deinit IOCTL calls are balanced, so a disk will not de-initialize until
29 It is also possible to force a disk de-initialization by passing a
35 Note that de-initializing a disk is a low level operation- typically the
36 de-initialization and initialization calls should be left to the filesystem
38 de-initialize the disk and can instead call :c:func:`fs_unmount`
40 SD Card support
43 Zephyr has support for some SD card controllers and support for interfacing
44 SD cards via SPI. These drivers use disk driver interface and a file system
45 can access the SD cards via disk access API.
46 Both standard and high-capacity SD cards are supported.
52 SD Memory Card subsystem
55 Zephyr supports SD memory cards via the disk driver API, or via the SDMMC
58 interacts with the :ref:`sd host controller api <sdhc_api>` to communicate
59 with attached SD cards.
62 SD Card support via SPI
65 Example devicetree fragment below shows how to add SD card node to ``spi1``
67 at 24 MHz once the SD card has been initialized:
69 .. code-block:: devicetree
73             cs-gpios = <&porta 27 GPIO_ACTIVE_LOW>;
76 		    compatible = "zephyr,sdhc-spi-slot";
80 			compatible = "zephyr,sdmmc-disk";
81                         disk-name = "SD";
84                     spi-max-frequency = <24000000>;
88 The SD card will be automatically detected and initialized by the
99 MMC in zephyr is implemented using the SD subsystem because the MMC bus
100 shares a lot of similarity with the SD bus. MMC controllers also use the
109 .. code-block:: devicetree
113             compatible = "zephyr,flash-disk";
115             disk-name = "NAND";
116             cache-size = <4096>;
120 The cache size specified in :dtcompatible:`zephyr,flash-disk` node should be