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/flash_handlers.c

58 lines
1.7 KiB
C
Raw Normal View History

drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
/*
* Copyright (c) 2017 Intel Corporation
*
* SPDX-License-Identifier: Apache-2.0
*/
#include <syscall_handler.h>
cleanup: include/: move flash.h to drivers/flash.h move flash.h to drivers/flash.h and create a shim for backward-compatibility. No functional changes to the headers. A warning in the shim can be controlled with CONFIG_COMPAT_INCLUDES. Related to #16539 Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-06-26 03:53:50 +08:00
#include <drivers/flash.h>
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_SYSCALL_HANDLER(flash_read, dev, offset, data, len)
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
{
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_OOPS(Z_SYSCALL_DRIVER_FLASH(dev, read));
Z_OOPS(Z_SYSCALL_MEMORY_WRITE(data, len));
all: Update reserved function names Update reserved function names starting with one underscore, replacing them as follows: '_k_' with 'z_' '_K_' with 'Z_' '_handler_' with 'z_handl_' '_Cstart' with 'z_cstart' '_Swap' with 'z_swap' This renaming is done on both global and those static function names in kernel/include and include/. Other static function names in kernel/ are renamed by removing the leading underscore. Other function names not starting with any prefix listed above are renamed starting with a 'z_' or 'Z_' prefix. Function names starting with two or three leading underscores are not automatcally renamed since these names will collide with the variants with two or three leading underscores. Various generator scripts have also been updated as well as perf, linker and usb files. These are drivers/serial/uart_handlers.c include/linker/kobject-text.ld kernel/include/syscall_handler.h scripts/gen_kobject_list.py scripts/gen_syscall_header.py Signed-off-by: Patrik Flykt <patrik.flykt@intel.com>
2019-03-09 05:19:05 +08:00
return z_impl_flash_read((struct device *)dev, offset, (void *)data,
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
len);
}
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_SYSCALL_HANDLER(flash_write, dev, offset, data, len)
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
{
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_OOPS(Z_SYSCALL_DRIVER_FLASH(dev, write));
Z_OOPS(Z_SYSCALL_MEMORY_READ(data, len));
all: Update reserved function names Update reserved function names starting with one underscore, replacing them as follows: '_k_' with 'z_' '_K_' with 'Z_' '_handler_' with 'z_handl_' '_Cstart' with 'z_cstart' '_Swap' with 'z_swap' This renaming is done on both global and those static function names in kernel/include and include/. Other static function names in kernel/ are renamed by removing the leading underscore. Other function names not starting with any prefix listed above are renamed starting with a 'z_' or 'Z_' prefix. Function names starting with two or three leading underscores are not automatcally renamed since these names will collide with the variants with two or three leading underscores. Various generator scripts have also been updated as well as perf, linker and usb files. These are drivers/serial/uart_handlers.c include/linker/kobject-text.ld kernel/include/syscall_handler.h scripts/gen_kobject_list.py scripts/gen_syscall_header.py Signed-off-by: Patrik Flykt <patrik.flykt@intel.com>
2019-03-09 05:19:05 +08:00
return z_impl_flash_write((struct device *)dev, offset,
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
(const void *)data, len);
}
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_SYSCALL_HANDLER(flash_write_protection_set, dev, enable)
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
{
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_OOPS(Z_SYSCALL_DRIVER_FLASH(dev, write_protection));
all: Update reserved function names Update reserved function names starting with one underscore, replacing them as follows: '_k_' with 'z_' '_K_' with 'Z_' '_handler_' with 'z_handl_' '_Cstart' with 'z_cstart' '_Swap' with 'z_swap' This renaming is done on both global and those static function names in kernel/include and include/. Other static function names in kernel/ are renamed by removing the leading underscore. Other function names not starting with any prefix listed above are renamed starting with a 'z_' or 'Z_' prefix. Function names starting with two or three leading underscores are not automatcally renamed since these names will collide with the variants with two or three leading underscores. Various generator scripts have also been updated as well as perf, linker and usb files. These are drivers/serial/uart_handlers.c include/linker/kobject-text.ld kernel/include/syscall_handler.h scripts/gen_kobject_list.py scripts/gen_syscall_header.py Signed-off-by: Patrik Flykt <patrik.flykt@intel.com>
2019-03-09 05:19:05 +08:00
return z_impl_flash_write_protection_set((struct device *)dev, enable);
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
}
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_SYSCALL_HANDLER1_SIMPLE(flash_get_write_block_size, K_OBJ_DRIVER_FLASH,
struct device *);
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
#ifdef CONFIG_FLASH_PAGE_LAYOUT
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_SYSCALL_HANDLER(flash_get_page_info_by_offs, dev, offs, info)
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
{
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_OOPS(Z_SYSCALL_DRIVER_FLASH(dev, page_layout));
Z_OOPS(Z_SYSCALL_MEMORY_WRITE(info, sizeof(struct flash_pages_info)));
all: Update reserved function names Update reserved function names starting with one underscore, replacing them as follows: '_k_' with 'z_' '_K_' with 'Z_' '_handler_' with 'z_handl_' '_Cstart' with 'z_cstart' '_Swap' with 'z_swap' This renaming is done on both global and those static function names in kernel/include and include/. Other static function names in kernel/ are renamed by removing the leading underscore. Other function names not starting with any prefix listed above are renamed starting with a 'z_' or 'Z_' prefix. Function names starting with two or three leading underscores are not automatcally renamed since these names will collide with the variants with two or three leading underscores. Various generator scripts have also been updated as well as perf, linker and usb files. These are drivers/serial/uart_handlers.c include/linker/kobject-text.ld kernel/include/syscall_handler.h scripts/gen_kobject_list.py scripts/gen_syscall_header.py Signed-off-by: Patrik Flykt <patrik.flykt@intel.com>
2019-03-09 05:19:05 +08:00
return z_impl_flash_get_page_info_by_offs((struct device *)dev, offs,
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
(struct flash_pages_info *)info);
}
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_SYSCALL_HANDLER(flash_get_page_info_by_idx, dev, idx, info)
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
{
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_OOPS(Z_SYSCALL_DRIVER_FLASH(dev, page_layout));
Z_OOPS(Z_SYSCALL_MEMORY_WRITE(info, sizeof(struct flash_pages_info)));
all: Update reserved function names Update reserved function names starting with one underscore, replacing them as follows: '_k_' with 'z_' '_K_' with 'Z_' '_handler_' with 'z_handl_' '_Cstart' with 'z_cstart' '_Swap' with 'z_swap' This renaming is done on both global and those static function names in kernel/include and include/. Other static function names in kernel/ are renamed by removing the leading underscore. Other function names not starting with any prefix listed above are renamed starting with a 'z_' or 'Z_' prefix. Function names starting with two or three leading underscores are not automatcally renamed since these names will collide with the variants with two or three leading underscores. Various generator scripts have also been updated as well as perf, linker and usb files. These are drivers/serial/uart_handlers.c include/linker/kobject-text.ld kernel/include/syscall_handler.h scripts/gen_kobject_list.py scripts/gen_syscall_header.py Signed-off-by: Patrik Flykt <patrik.flykt@intel.com>
2019-03-09 05:19:05 +08:00
return z_impl_flash_get_page_info_by_idx((struct device *)dev, idx,
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
(struct flash_pages_info *)info);
}
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_SYSCALL_HANDLER(flash_get_page_count, dev)
drivers: Perform a runtime check if a driver is capable of an operation Driver APIs might not implement all operations, making it possible for a user thread to get the kernel to execute a function at 0x00000000. Perform runtime checks in all the driver handlers, checking if they're capable of performing the requested operation. Fixes #6907. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2018-04-05 04:50:32 +08:00
{
syscalls: remove policy from handler checks The various macros to do checks in system call handlers all implictly would generate a kernel oops if a check failed. This is undesirable for a few reasons: * System call handlers that acquire resources in the handler have no good recourse for cleanup if a check fails. * In some cases we may want to propagate a return value back to the caller instead of just killing the calling thread, even though the base API doesn't do these checks. These macros now all return a value, if nonzero is returned the check failed. K_OOPS() now wraps these calls to generate a kernel oops. At the moment, the policy for all APIs has not changed. They still all oops upon a failed check/ The macros now use the Z_ notation for private APIs. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2018-05-05 06:57:57 +08:00
Z_OOPS(Z_SYSCALL_DRIVER_FLASH(dev, page_layout));
all: Update reserved function names Update reserved function names starting with one underscore, replacing them as follows: '_k_' with 'z_' '_K_' with 'Z_' '_handler_' with 'z_handl_' '_Cstart' with 'z_cstart' '_Swap' with 'z_swap' This renaming is done on both global and those static function names in kernel/include and include/. Other static function names in kernel/ are renamed by removing the leading underscore. Other function names not starting with any prefix listed above are renamed starting with a 'z_' or 'Z_' prefix. Function names starting with two or three leading underscores are not automatcally renamed since these names will collide with the variants with two or three leading underscores. Various generator scripts have also been updated as well as perf, linker and usb files. These are drivers/serial/uart_handlers.c include/linker/kobject-text.ld kernel/include/syscall_handler.h scripts/gen_kobject_list.py scripts/gen_syscall_header.py Signed-off-by: Patrik Flykt <patrik.flykt@intel.com>
2019-03-09 05:19:05 +08:00
return z_impl_flash_get_page_count((struct device *)dev);
drivers: Perform a runtime check if a driver is capable of an operation Driver APIs might not implement all operations, making it possible for a user thread to get the kernel to execute a function at 0x00000000. Perform runtime checks in all the driver handlers, checking if they're capable of performing the requested operation. Fixes #6907. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com>
2018-04-05 04:50:32 +08:00
}
drivers: flash: add system calls The page_layout API returns pointers to kernel memory and is not exposed to user mode. This is fine for flash_get_page_count() and flash_get_page_info APIs since these copy the values, but some redesign work will be needed to get flash_page_foreach() working in user mode since we do not want the callback running in a privileged state. Due to the way that (even unimplemented) system call prototypes are generated, the definition of struct flash_pages_info needed to be moved outside of the #ifdef. Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2017-10-26 03:36:51 +08:00
#endif