Lines Matching refs:disk
9 The disk access API provides access to storage devices.
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
18 * :c:macro:`DISK_IOCTL_CTRL_INIT`: Initialize the disk. Must be called before
19 additional I/O operations can be run on the disk device. Equivalent to
22 * :c:macro:`DISK_IOCTL_CTRL_DEINIT`: De-initialize the disk. Once this IOCTL
24 the disk can be used for addition I/O operations.
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
32 each disk driver may handle differently, but it will always return
35 Note that de-initializing a disk is a low level operation- typically the
38 de-initialize the disk and can instead call :c:func:`fs_unmount`
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.
55 Zephyr supports SD memory cards via the disk driver API, or via the SDMMC
56 subsystem. This subsystem can be used transparently via the disk driver API,
80 compatible = "zephyr,sdmmc-disk";
81 disk-name = "SD";
113 compatible = "zephyr,flash-disk";
115 disk-name = "NAND";
120 The cache size specified in :dtcompatible:`zephyr,flash-disk` node should be
123 NVMe disk support