Searched refs:line (Results 1 – 4 of 4) sorted by relevance
166 for (int line= 0; line < NHW_GPIOTE_N_INT; line ++) { in nrf_gpiote_eval_interrupt() local170 mask = (st->GPIOTE_ITEN[line] >> i) & 0x1; in nrf_gpiote_eval_interrupt()178 mask = (st->GPIOTE_ITEN[line] & GPIOTE_INTENCLR_PORT_Msk) >> GPIOTE_INTENCLR_PORT_Pos; in nrf_gpiote_eval_interrupt()183 …mask = (st->GPIOTE_ITEN[line] & GPIOTE_INTENCLR0_PORT0NONSECURE_Msk) >> GPIOTE_INTENCLR0_PORT0NONS… in nrf_gpiote_eval_interrupt()187 …mask = (st->GPIOTE_ITEN[line] & GPIOTE_INTENCLR0_PORT0SECURE_Msk) >> GPIOTE_INTENCLR0_PORT0SECURE_… in nrf_gpiote_eval_interrupt()193 hw_irq_ctrl_toggle_level_irq_line_if(&st->gpiote_int_line[line], in nrf_gpiote_eval_interrupt()195 &nhw_gpiote_irq_map[inst][line]); in nrf_gpiote_eval_interrupt()
13 with command line parameters.20 Enabling this and selecting the file is done with command line options.21 When enabled, the model will dump one line in this file per byte, with two columns:32 bytes into the UART peripheral like if they arrived through the Rx line.54 You enable this backend for each instance using command line parameters, by specifying64 terminate the simulation; But you can change this with a command line option, so that it will98 Check the command line options with `-help`.
203 execution to register command line arguments.223 ### Command line interface arguments225 These models register their own command line arguments/options using226 babblesim's command line argument utilities.229 The way to describe the command line arguments follows Babblesim's230 `libUtilv1` command line parsing convention.
124 character and anything after until the end of the line will be ignored.
