This website requires JavaScript.
Explore
Help
Sign In
OrgZephyr
/
zephyr
mirror of
https://github.com/zephyrproject-rtos/zephyr.git
Watch
1
Star
0
Fork
You've already forked zephyr
0
Code
Issues
Releases
Wiki
Activity
9124e310fd
zephyr
/
tests
/
drivers
/
ipm
/
testcase.yaml
5 lines
83 B
YAML
Raw
Normal View
History
Unescape
Escape
tests: samples: convert testcase files to yaml This will prepare test cases and samples with metadata and information that will be consumed by the sanitycheck script which will be changed to parse YAML files instead of ini. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-04-05 11:11:22 +08:00
tests
:
tests: fix test identifiers The seasonal overhaul of test identifiers aligning the terms being used and creating a structure. This is hopefully the last time we do this, plan is to document the identifiers and enforce syntax. The end-goal is to be able to generate a testsuite description from the existing tests and sync it frequently with the testsuite in Testrail. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-12-02 01:29:43 +08:00
drivers.ipc.mailbox
:
drivers/timer: New xtensa timer with tickless support Rewritten Xtensa CCOUNT driver along the lines of all the other new drivers. The new API permits much smaller code. Notably: The Xtensa counter is a 32 bit up-counter with a comparator register. It's in some sense the archetype of this kind of timer as it's the simplest of the bunch (everything else has quirks: NRF is very slow and 24 bit, HPET has a runtime frequency detection, RISC-V is 64 bit...). I should have written this one first. Note also that this includes a blacklist of the xtensa architecture on the tests/driver/ipm test. I'm getting spurious failures there where a k_sem_take() call with a non-zero timeout is being made out of the console output code in interrupt context. This seems to have nothing to do with the timer; I suspect it's because the old timer drivers would (incorrectly!) call z_clock_announce() in non-interrupt context in some contexts (e.g. "expiring really soon"). Apparently this test (or something in the IPM or Xtensa console code) was somehow relying on that on Xtensa. But IPM is a Quark thing and there's no particular reason to run this test there. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2018-10-24 00:08:58 +08:00
arch_exclude
:
posix xtensa
tests: ipm: fix testcase tags Add correct tag to the testcase. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-12-08 23:48:02 +08:00
tags
:
drivers ipc