Home
last modified time | relevance | path

Searched full:we (Results 1 – 25 of 2743) sorted by relevance

12345678910>>...110

/Zephyr-latest/samples/subsys/pm/latency/
Dsample.yaml14 - "<inf> app: Sleeping for 1.1 seconds, we should enter RUNTIME_IDLE"
16 - "<inf> app: Sleeping for 1.2 seconds, we should enter SUSPEND_TO_IDLE"
18 - "<inf> app: Sleeping for 1.3 seconds, we should enter STANDBY"
21 - "<inf> app: Sleeping for 1.1 seconds, we should enter RUNTIME_IDLE"
23 - "<inf> app: Sleeping for 1.2 seconds, we should enter SUSPEND_TO_IDLE"
25 - "<inf> app: Sleeping for 1.3 seconds, we should enter SUSPEND_TO_IDLE"
30 - "<inf> app: Sleeping for 1.1 seconds, we should enter RUNTIME_IDLE"
32 - "<inf> app: Sleeping for 1.2 seconds, we should enter RUNTIME_IDLE"
34 - "<inf> app: Sleeping for 1.3 seconds, we should enter RUNTIME_IDLE"
39 - "<inf> app: Sleeping for 1.1 seconds, we should stay ACTIVE"
[all …]
/Zephyr-latest/samples/subsys/pm/latency/src/
Dmain.c41 LOG_INF("Sleeping for 1.1 seconds, we should enter RUNTIME_IDLE"); in main()
43 LOG_INF("Sleeping for 1.2 seconds, we should enter SUSPEND_TO_IDLE"); in main()
45 LOG_INF("Sleeping for 1.3 seconds, we should enter STANDBY"); in main()
53 LOG_INF("Sleeping for 1.1 seconds, we should enter RUNTIME_IDLE"); in main()
55 LOG_INF("Sleeping for 1.2 seconds, we should enter SUSPEND_TO_IDLE"); in main()
57 LOG_INF("Sleeping for 1.3 seconds, we should enter SUSPEND_TO_IDLE"); in main()
65 LOG_INF("Sleeping for 1.1 seconds, we should enter RUNTIME_IDLE"); in main()
67 LOG_INF("Sleeping for 1.2 seconds, we should enter RUNTIME_IDLE"); in main()
69 LOG_INF("Sleeping for 1.3 seconds, we should enter RUNTIME_IDLE"); in main()
77 LOG_INF("Sleeping for 1.1 seconds, we should stay ACTIVE"); in main()
[all …]
/Zephyr-latest/samples/drivers/i2c/rtio_loopback/src/
Dmain.c38 * We will be using 3 submission queue events (SQEs); i2c write, i2c read,
46 * actions submitted to the RTIO context. In this sample, we are using an I2C
47 * controller device, so we use the I2C specific helper to define the RTIO IODEV.
52 * For async write read operation we will be waiting for a callback from RTIO.
53 * We will wait on this sem which we will give from the callback.
58 * We register a simple I2C target which we will be targeting using RTIO. We
199 * We allocate one of the 3 submission queue events (SQEs) as defined by in sample_rtio_write_read()
213 * transaction. We configure this by setting the RTIO_SQE_TRANSACTION. in sample_rtio_write_read()
218 * We then allocate an SQE and configure it to read in sample_rtio_write_read()
229 * Since we are working with I2C messages, we need to specify the I2C in sample_rtio_write_read()
[all …]
/Zephyr-latest/cmake/linker/arcmwdt/
Dlinker_flags.cmake20 # - We have full MWDT libc support and we link MWDT libc - this is default
21 # behavior and we don't need to do something for that.
22 # - We use minimal libc provided by Zephyr itself. In that case we must not
23 # link MWDT libc, but we still need to link libmw
/Zephyr-latest/arch/nios2/core/
Dexception.S31 * If the External (EIC) controller is in use, then we will never get here on
68 /* Figure out whether we are here because of an interrupt or an
78 /* We stashed estatus in et earlier */
83 /* If we get here, this is an interrupt */
85 /* Grab a reference to _kernel in r10 so we can determine the
91 /* Stash a copy of thread's sp in r12 so that we can put it on the IRQ
106 * function parameter since we put it in r4
135 /* We put the thread stack pointer on top of the IRQ stack before
136 * we switched stacks. Restore it to go back to thread stack
142 * out of the context switch we need this info to restore
[all …]
/Zephyr-latest/include/zephyr/arch/x86/
Dmemmap.h12 * The "source" of the memory map refers to where we got the data to fill in
27 * For simplicity, we maintain a fixed-sized array of memory regions.
29 * We don't only track available RAM -- we track unavailable regions, too:
30 * sometimes we'll be given a map with overlapping regions. We have to be
59 * We keep track of kernel memory areas (text, data, etc.) in a table for
/Zephyr-latest/share/zephyr-package/cmake/
DZephyrConfigVersion.cmake10 # Version 0.0.0 indicates that we should just return, in order to obtain our path.
18 # We are just a candidate, meaning we have been included from other installed module.
56 # We are the Zephyr to be used
65 # We are included, so we need to ensure that the version of the top-level
71 # When Zephyr base is set and we are checked as an included file
72 # (IS_INCLUDED=True), then we are unable to retrieve the version of the
101 # Do we share common index, if so, this is the correct version to check.
111 # Only do this if we are an installed CMake Config package and checking for workspace candidates.
120 # We are the best candidate, so let's check our own version.
128 # As this code is processed inside registered packages, we simply test if
[all …]
/Zephyr-latest/tests/subsys/rtio/rtio_i2c/include/
Dblocking_emul.hpp10 * We need to override fff's function signature away from a standard function pointer.
11 * By using std::function<> we're able to leverage capture variables since additional storage must
12 * be allocated for them. In the tests, we will include asserts in the lambda functions. This
14 * test function. If we use plain function pointers, we have to move the expected value outside
/Zephyr-latest/tests/bsim/bluetooth/host/gatt/settings/src/
Dclient.c30 /* subscribe to the SC indication, so we don't have to ATT read to in client_round_0()
36 /* We should normally wait until we are bonded to write the CCC / CF in client_round_0()
37 * characteristics, but here we bond after the fact on purpose, to in client_round_0()
56 /* server should remember we are change-aware */ in client_round_1()
72 /* We are change-unaware. wait until the Service Changed indication is in client_round_2()
78 /* We sleep just enough so that the server's `delayed store` work item in client_round_2()
79 * is executed. We still trigger a disconnect, even though the server in client_round_2()
97 /* server should remember we are change-aware */ in client_round_3()
102 * In the next round, we will be change-unaware, so the first ATT read in client_round_3()
103 * will fail, but the second one will succeed and we will be marked as in client_round_3()
Dserver.c71 * NVS. We still have to wait for the delayed work to be run. in server_round_2()
138 * peer has disconnected. In round 2 we also make sure we receive the Service
142 * writes the change-awareness before we get disconnected. Basically, this
146 * Round 3 -> 4: same as (1->2), except this time we won't get the SC indication
147 * (as we have unsubscribed from it). We should instead get the
152 * This is a non-regression test to make sure we didn't break the previous
155 * Round 5 -> 6: tests DFU corner case: in this case, we are on the first boot
157 * reason, we decide to reboot before the delayed store work item has had the
159 * makes sure that we are indeed change-unaware.
169 /* Use the same public address for all instances of the central. If we in server_procedure()
/Zephyr-latest/samples/subsys/fs/fs_sample/boards/
Dnrf52840dk_nrf52840_ram_disk_region.overlay8 * of RAM there is. We need some for the Disk, so we need to
17 * nrf52840 SoC; because we are not able to just
18 * change the size, what we have to do is to remove
51 * disk using a phandle; note that we reference the
52 * region by label we have defined it above.
/Zephyr-latest/arch/x86/core/intel64/
Duserspace.S15 * to the user page table, and only then 'iret'. We jump to this instead
74 * moment we have no free registers or stack to save it to. This
75 * eventually gets put on the stack before we re-enable interrupts
81 /* We need to switch to the trampoline stack so that we can
101 /* We're now on the privilege mode stack; push the old user stack
126 * We save caller-saved registers so we can restore to original values
127 * when we call 'sysretq' at the end.
142 * we had to put in r10 instead of RCX
159 * RDI, RSI, RDX, R8, R9, R10, XMM* after we have serviced the system
160 * call. We saved them earlier, restore their original values when
[all …]
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/openisa/hal/RV32M1/
Dll_irqs.h13 * LPTMR1 -> INTMUX_CH2. We expect it to be the only IRQ source for this channel
14 * We'll use the INTMUX ISR for channel 2 instead of LPTMR1 ISR
20 * radio -> INTMUX_CH3. We expect it to be the only IRQ source for this channel
21 * We'll use the INTMUX ISR for channel 3 instead of radio ISR
/Zephyr-latest/cmake/linker/
Dlinker_libraries_native.cmake5 # When doing native builds, then we default to host libraries.
6 # No reason for loading linker libraries properties in this case, however we do
10 # Empty on purpose as we default to host libraries selected by the linker.
15 # Although library properties are empty per default, then we still define link
/Zephyr-latest/cmake/compiler/arcmwdt/
Dtarget.cmake28 # (check_c_compiler_flag function which we wrap with target_cc_option in extensions.cmake)
29 # we rely on default MWDT header locations and don't manually specify headers directories.
40 # We can't rely on these functions presence if we don't use MWDT libc.
41 # NOTE: the option name '-fno-builtin' is misleading a bit - we still can
42 # manually call __builtin_** functions even if we specify it.
/Zephyr-latest/doc/develop/test/twister/
Dtwister_blackbox.rst42 Such a test provides us with all the outputs we typically expect of a Twister run thanks to
44 We can easily set up all flags that we expect from a Twister call via ``args`` variable [#f2]_ .
45 We can check the standard output or stderr in ``out`` and ``err`` variables.
47 Beside the standard outputs, we can also investigate the file outputs, normally placed in
48 ``twister-out`` directories. Most of the time, we will use the ``out_path`` fixture in conjunction
97 Sometimes we want to test something that requires prior Twister use. ``--test-only``
99 Twister call. How should we approach that?
101 If we just call the ``importlib`` 's ``exec_module`` two times, we will experience log
102 duplication. ``twister.log`` will duplicate every line (triplicate if we call it three times, etc.)
126 .. [#f2] We advise you to keep the first section of ``args`` definition intact in almost all
/Zephyr-latest/arch/xtensa/include/
Dxtensa_asm2_s.h199 * (PTEVADDR base, the one mapping 0x00000000) so that we can
200 * use this to obtain the virtual address of the PTE page we are
205 * miss if we are to use l32r to load the PTEVADDR base.
207 * not in TLB, we will need to handle the TLB miss which
208 * we are trying to avoid here.
231 * is problematic when we are in the middle of dealing with another
232 * exception or handling an interrupt. So we need to put the PTE page
250 * 1. We need to find the virtual address of the PTE page
252 * register ADDR_REG. To do this, we first need to find
260 * we divide the address obtained in step (a) by
[all …]
/Zephyr-latest/arch/arm64/core/
Dfpu.c101 /* search all CPUs for the owner we want */ in flush_owned_fpu()
108 /* we found it live on CPU i */ in flush_owned_fpu()
120 * we would be stuck here. in flush_owned_fpu()
123 * CPU, then we preemptively flush any live context in flush_owned_fpu()
124 * on this CPU as well since we're likely to in flush_owned_fpu()
156 * FPU access is disabled and we're trapped while in exception context.
158 * just to let the corresponding STR instructions execute, we simply
166 * We know there is no saved FPU context to check nor any in simulate_str_q_insn()
181 * We're looking for STR (immediate, SIMD&FP) of the form: in simulate_str_q_insn()
200 /* did we do something? */ in simulate_str_q_insn()
[all …]
/Zephyr-latest/boards/native/nrf_bsim/
Dipc_backend.c8 * Here we define the shared memory buffers for the RPMSG IPC back-end in simulation.
10 * In this simulated target, we just define them at build time to have the size defined
14 * when the network core is built with the IPC service, we cannot produce an executable
15 * with the network core image alone, as we would lack this buffer during linking.
/Zephyr-latest/tests/kernel/device/src/
Dmmio.c38 /* fake API pointer, we don't use it at all for this suite */
47 * We show that we can make mapping calls and that the address returned by
51 * We also perform some checks depending on configuration:
56 * point to the same address. We show that no extra memory is used in
79 * The best we can check with 'regs' is that it's nonzero, as if in ZTEST()
81 * place it at. We don't otherwise look at `regs`; other tests will in ZTEST()
141 * We show that we can make mapping calls and that the address returned by
145 * We show that this works for a device instance that has two named regions,
148 * We also perform some checks depending on configuration:
153 * point to the same address. We show that no extra memory is used in
[all …]
/Zephyr-latest/samples/userspace/prod_consumer/src/
Dapp_b.c28 * we ensure all this gets linked into the continuous region denoted by
59 /* pretend we're doing something complicated and useful in processor_thread()
81 /* Much like how we are reusing the main thread as this application's in app_b_entry()
82 * processor thread, we will re-use the default memory domain as the in app_b_entry()
106 /* We are about to drop to user mode and become the monitor thread. in app_b_entry()
107 * Grant ourselves access to the kernel objects we need for in app_b_entry()
110 * In this case, we need access to both shared queue objects. We in app_b_entry()
/Zephyr-latest/cmake/modules/
Dwest.cmake7 # west is an optional dependency. We need to run west using the same
8 # Python interpreter as everything else, though, so we play some extra
12 # it's defined, we assume west is installed. We do these checks here
20 # If realpaths differ from the variables we're using, add extra
57 # WEST_PYTHON is undefined and we couldn't import west. That's
62 # We can import west from PYTHON_EXECUTABLE and have its version.
79 # Print information about the west module we're relying on. This
/Zephyr-latest/samples/net/mdns_responder/
Doverlay-vlan.conf3 # We have one non-vlan interface and two VLAN interfaces
30 # Each interface needs at least 2 context. So if we have three
31 # interfaces we need minimum 6 context but allocate more so that
32 # we do not run out of them.
/Zephyr-latest/arch/arc/core/
Dregular_irq.S36 1. We return from IRQ handler to a cooperative thread
59 | STATUS32 value, we explicitly save it here for later usage, read-on
70 thread's stack right on top of pre-switch contents so that's what we have:
96 So how do we return in such a complex scenario.
98 First we restore callee-saved regs with help of _load_callee_saved_regs().
99 Now we're back to PRE-CONTEXT-SWITCH STACK (see above).
103 we're still in interrupt handling mode and the only way to return to normal
104 execution mode is to execute "rtie" instruction. And here we need to deal
118 an interrupt, but remember we're returning to the thread which was
121 will happen. So if we do nothing special we'll end-up with that:
[all …]
/Zephyr-latest/arch/arc/
DCMakeLists.txt18 # For ARCv2 the default register is usually not specified - so we need to specify it
19 # For ARCv3 the register is fixed to r30, so we don't need to specify it
22 # If thread local storage isn't used - we can safely schedule thread pointer register
34 # Instruct MWDT assembler not to warn when we load only lower half (32bit) of symbol
35 # instead of full 64bit address in ASM code. It is valid as we don't support Zephyr

12345678910>>...110