OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/flash/CMakeLists.txt

39 lines
1.7 KiB
CMake
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
drivers: flash: Remove usage of zephyr_library_ifdef Phasing out the usage of this cmake macro from the drivers/flash folder. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-05-23 19:22:20 +08:00
zephyr_library()
drivers: Cmake: Add __ZEPHYR_SUPERVISOR__ macro for driver files. Normally a syscall would check the current privilege level and then decide to go to _impl_<syscall> directly or go through a _handler_<syscall>. __ZEPHYR_SUPERVISOR__ is a compiler optimization flag which will make all the system calls from the driver files directly link to the _impl_<syscall>. Thereby reducing the overhead of checking the privileges. In the previous implementation all the source files would be compiled by zephyr_source() rule. This means that zephyr_* is a catchall CMake library for source files that can be built purely with the include paths, defines, and other compiler flags that all zephyr source files uses. This states that adding one extra compiler flag for only one complete directory would fail. This limitation can be overcome by using zephyr_libray* APIs. This creates a library for the required directories and it also supports directory level properties. Hence we use zephyr_library* to create a new library with macro _ZEPHYR_SUPERVISOR_ for the optimization. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-03-28 18:06:12 +08:00
drivers: flash: add a generic spi nor flash driver This driver is inspired from the w25qxxdv SPI NOR flash driver which was already implementing the CFI (Common Flash Interface) for its purpose. To handle other NOR flash a flash id table (as Linux do) which contains the geometry for a few SPI NOR flash based on their JEDEC ID has been introduced. We currently support the following flash: - W25Q80 - W25Q16 - W25Q32 - S25FL216K - MX25UM512 The read and write functions are able to handle more then one page at a time and return the number of bytes read or write. Also because every NOR flash expect to disable the write protection before writing or erasing, the write enable command is now part of the write and erase functions. Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com> Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
2018-11-12 23:36:24 +08:00
zephyr_library_sources_ifdef(CONFIG_SPI_NOR spi_nor.c)
drivers: flash: add Nordic JEDEC QSPI NOR flash driver Most JEDEC NOR flash devices uses not only typical SPI mode (MISO,MOSI,SCK and CS), but also QSPI mode (IO0,IO1,IO2,IO3,SCK and CS). QSPI mode uses more data lines and as a result provide higher throughput. If this were not enough, Nordic chips provide hardware acceleration for read/write/erase functions, what gives significant performance boost. It does a lot of things "behind the scene", i.e when user has written some data to the flash and would like to read them back, it has to wait until the flash is ready by reading WIP bit in Status Register. This driver does it automatically. Signed-off-by: Kamil Lazowski <Kamil.Lazowski@nordicsemi.no>
2019-12-19 20:33:37 +08:00
zephyr_library_sources_ifdef(CONFIG_NORDIC_QSPI_NOR nrf_qspi_nor.c)
drivers: flash: add flash_simulator driver This commit adds a flash driver implementation that writes to RAM and exports statistics through stats.h. It can be used to simulate flash memory for testing purposes. Signed-off-by: Emanuele Di Santo <emdi@nordicsemi.no> Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no> Signed-off-by: Kamil Piszczek <Kamil.Piszczek@nordicsemi.no>
2019-04-18 20:55:30 +08:00
zephyr_library_sources_ifdef(CONFIG_FLASH_SIMULATOR flash_simulator.c)
drivers: flash: Add driver for AT45 compatible SPI flash chips Add a driver that can handle several instances of AT45 family chips, which are enabled by specifying DT nodes for them with the "compatible" property set to "atmel,at45" and other required properties like JEDEC ID, chip capacity, block and page size etc. configured accordingly. The driver is only capable of using "power of 2" binary page sizes in those chips and at initialization configures them to work in that mode (unless it is already done). Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
2020-03-11 00:57:01 +08:00
zephyr_library_sources_ifdef(CONFIG_SPI_FLASH_AT45 spi_flash_at45.c)
drivers: Cmake: Add __ZEPHYR_SUPERVISOR__ macro for driver files. Normally a syscall would check the current privilege level and then decide to go to _impl_<syscall> directly or go through a _handler_<syscall>. __ZEPHYR_SUPERVISOR__ is a compiler optimization flag which will make all the system calls from the driver files directly link to the _impl_<syscall>. Thereby reducing the overhead of checking the privileges. In the previous implementation all the source files would be compiled by zephyr_source() rule. This means that zephyr_* is a catchall CMake library for source files that can be built purely with the include paths, defines, and other compiler flags that all zephyr source files uses. This states that adding one extra compiler flag for only one complete directory would fail. This limitation can be overcome by using zephyr_libray* APIs. This creates a library for the required directories and it also supports directory level properties. Hence we use zephyr_library* to create a new library with macro _ZEPHYR_SUPERVISOR_ for the optimization. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-03-28 18:06:12 +08:00
zephyr_library_sources_ifdef(CONFIG_SOC_FLASH_NRF soc_flash_nrf.c)
zephyr_library_sources_ifdef(CONFIG_SOC_FLASH_MCUX soc_flash_mcux.c)
zephyr_library_sources_ifdef(CONFIG_FLASH_PAGE_LAYOUT flash_page_layout.c)
zephyr_library_sources_ifdef(CONFIG_USERSPACE flash_handlers.c)
zephyr_library_sources_ifdef(CONFIG_SOC_FLASH_SAM0 flash_sam0.c)
drivers: flash: add flash driver support for Atmel SAM E70 This patch adds a flash driver for the Atmel SAM E70 SoC. The driver has been kept simple by considering that the flash is only composed of 8-KiB blocks. Indeed an area at the beginning of the flash might be erased with a smaller granularity, and the other blocks can also be erased with a higher granularity. It also only handles the global read/write protection, not the 128-KiB lock regions. A write error is returned if a region is locked. Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
2018-11-05 04:41:22 +08:00
zephyr_library_sources_ifdef(CONFIG_SOC_FLASH_SAM flash_sam.c)
drivers: Cmake: Add __ZEPHYR_SUPERVISOR__ macro for driver files. Normally a syscall would check the current privilege level and then decide to go to _impl_<syscall> directly or go through a _handler_<syscall>. __ZEPHYR_SUPERVISOR__ is a compiler optimization flag which will make all the system calls from the driver files directly link to the _impl_<syscall>. Thereby reducing the overhead of checking the privileges. In the previous implementation all the source files would be compiled by zephyr_source() rule. This means that zephyr_* is a catchall CMake library for source files that can be built purely with the include paths, defines, and other compiler flags that all zephyr source files uses. This states that adding one extra compiler flag for only one complete directory would fail. This limitation can be overcome by using zephyr_libray* APIs. This creates a library for the required directories and it also supports directory level properties. Hence we use zephyr_library* to create a new library with macro _ZEPHYR_SUPERVISOR_ for the optimization. Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-03-28 18:06:12 +08:00
zephyr_library_sources_ifdef(CONFIG_SOC_FLASH_NIOS2_QSPI soc_flash_nios2_qspi.c)
drivers: flash_gecko: Add flash driver for SiLabs Gecko SoCs Tested with SLWSTK6061A / BRD4250B wireless starter kit. Signed-off-by: Piotr Mienkowski <piotr.mienkowski@gmail.com>
2018-08-07 20:11:45 +08:00
zephyr_library_sources_ifdef(CONFIG_SOC_FLASH_GECKO flash_gecko.c)
driver: flash: add flash driver for the RV32M1 SOC Add driver and device tree for the flash controller for the RV32M1 SOC Signed-off-by: Lyle Zhu <lyle.zhu@nxp.com>
2019-05-22 23:07:50 +08:00
zephyr_library_sources_ifdef(CONFIG_SOC_FLASH_RV32M1 soc_flash_rv32m1.c)
Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no>
2017-10-27 21:43:34 +08:00
drivers: flash: Build STM32 flash support only when selected The current configuration causes the STM32 flash support always to be built, even if an unrelated flash driver, by example the SPI_NOR driver is selected. This behaviour gets especially problematic (build failure) if the flash hardware of the given MCU is not supported (e.g. STM32F2). The suggested change should ensure that STM32 flash support only is built when it actually is selected. Signed-off-by: Marco Peter <marco@peter-net.ch>
2019-12-09 05:06:17 +08:00
if(CONFIG_SOC_FLASH_STM32)
drivers/flash: Rework CMakeLists.txt for stm32 drivers Optimize CMake rules for STM23 series driver build. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2019-02-18 19:20:31 +08:00
zephyr_sources(flash_stm32.c)
drivers: flash: Remove redundant code in STM32 drivers Several STM32 chips have identical chip-specific code that has been duplicated in different source files. Unify the F0x, F1x, and F3x to use a single implementation. Signed-off-by: Andreas Sandberg <andreas@sandberg.pp.se>
2020-05-11 17:51:05 +08:00
zephyr_sources_ifdef(CONFIG_SOC_FLASH_STM32_V1 flash_stm32_v1.c)
drivers/flash: Rework CMakeLists.txt for stm32 drivers Optimize CMake rules for STM23 series driver build. Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2019-02-18 19:20:31 +08:00
zephyr_sources_ifdef(CONFIG_SOC_SERIES_STM32F4X flash_stm32f4x.c)
zephyr_sources_ifdef(CONFIG_SOC_SERIES_STM32F7X flash_stm32f7x.c)
zephyr_sources_ifdef(CONFIG_SOC_SERIES_STM32L4X flash_stm32l4x.c)
drivers/flash: stm32wb: Add driver for stm32wb Add flash driver for stm32wb Signed-off-by: Erwan Gouriou <erwan.gouriou@linaro.org>
2019-03-27 23:52:37 +08:00
zephyr_sources_ifdef(CONFIG_SOC_SERIES_STM32WBX flash_stm32wbx.c)
drivers: flash: Add STM32G0XX flash support Add flash support for STM32G0X SoC series. Signed-off-by: Philippe Retornaz <philippe@shapescale.com Signed-off-by: Francois Ramu <francois.ramu@st.com>
2019-07-05 21:02:21 +08:00
zephyr_sources_ifdef(CONFIG_SOC_SERIES_STM32G0X flash_stm32g0x.c)
drivers: flash: Add STM32G4X flash support Add flash driver support for STM32G4X SoC series. Signed-off-by: Richard Osterloh <richard.osterloh@gmail.com>
2019-09-04 16:43:59 +08:00
zephyr_sources_ifdef(CONFIG_SOC_SERIES_STM32G4X flash_stm32g4x.c)
Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no>
2017-10-27 21:43:34 +08:00
endif()
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 17:46:13 +08:00
zephyr_include_directories_ifdef(
CONFIG_SOC_FLASH_NRF_RADIO_SYNC
${ZEPHYR_BASE}/subsys/bluetooth
${ZEPHYR_BASE}/subsys/bluetooth/controller/ll_sw/nordic
)
flash: make flash shell generic This shell command was tied to bluetooth and the bluetooth shell and also had messages all related to nordic ICs. Make it generic and put it under drivers/flash/ so it can be included by anyone and independently of bluetooth. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-10-19 01:15:46 +08:00
Bluetooth: controller: Prepare to introduce LL split architecture Preparation to introduce the Upper Link Layer (ULL) and Lower Link Layer (LLL) split architecture. - Move SoC dependent HAL to vendor specific folder. - Preparation to split data structures into ULL and LLL types. - Added more role and state conditional compilations. - Added some work-in-progress implementation of advertising extensions, will be used as inspiration in the new split architecture work. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2018-12-17 17:46:13 +08:00
zephyr_library_sources_ifdef(CONFIG_FLASH_SHELL flash_shell.c)
drivers: flash: jesd216: add JESD216 API for use in shared drivers The spi_nor flash interface was designed for flash devices that use a standard SPI interface to devices that are compatible with the Micron M25P80 serial flash, identified in Linux as compatible jedec,spi-nor. The JEDEC Serial Flash Discoverable Parameters standard (JESD216) was designed to allow these devices to be self-describing. As we are increasingly being asked to support flash memories that do not use "standard" erase sizes or commands we need data structures and helper functions to extract information about a flash interface at runtime. For some of these devices the commands hard-coded in the current implementation are simply wrong. Define generic structures that support the SFDP hierarchy and the core Basic Flash Parameters table. The description will also support SPI-NAND and xSPI devices that conform to the JESD216 standards. Add bitfield values and helper functions to extract some information that drivers might need from JESD216 fields. At this time only information that is likely to be used is extracted; more may be added in the future. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2020-05-31 05:01:55 +08:00
zephyr_library_sources_ifdef(CONFIG_FLASH_JESD216 jesd216.c)