8345e5ebf0
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>
24 lines
598 B
C
24 lines
598 B
C
/*
|
|
* Copyright (c) 2017 Intel Corporation
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#include <syscall_handler.h>
|
|
#include <pwm.h>
|
|
|
|
Z_SYSCALL_HANDLER(pwm_pin_set_cycles, dev, pwm, period, pulse)
|
|
{
|
|
Z_OOPS(Z_SYSCALL_DRIVER_PWM(dev, pin_set));
|
|
return _impl_pwm_pin_set_cycles((struct device *)dev, pwm, period,
|
|
pulse);
|
|
}
|
|
|
|
Z_SYSCALL_HANDLER(pwm_get_cycles_per_sec, dev, pwm, cycles)
|
|
{
|
|
Z_OOPS(Z_SYSCALL_DRIVER_PWM(dev, get_cycles_per_sec));
|
|
Z_OOPS(Z_SYSCALL_MEMORY_WRITE(cycles, sizeof(u64_t)));
|
|
return _impl_pwm_get_cycles_per_sec((struct device *)dev,
|
|
pwm, (u64_t *)cycles);
|
|
}
|