Home
last modified time | relevance | path

Searched refs:COR (Results 1 – 8 of 8) sorted by relevance

/openbmc/qemu/tests/qemu-iotests/
H A D216.out8 --- Doing COR ---
13 --- Checking COR result ---
H A D310.out8 --- Doing COR ---
13 --- Checking COR result ---
/openbmc/linux/drivers/net/wireless/ath/wil6210/
H A DKconfig25 COR (Clear-On-Read) or W1C (Write-1-to-Clear) mode.
26 For production code, use COR (say y); is default since
29 registers with debugfs. If COR were used, ISR would
/openbmc/linux/drivers/char/xilinx_hwicap/
H A Dxilinx_hwicap.c132 .COR = 9,
157 .COR = 9,
182 .COR = 9,
207 .COR = 9,
H A Dxilinx_hwicap.h134 u32 COR; member
/openbmc/linux/drivers/iio/adc/
H A Dat91-sama5d2_adc.c172 u16 COR; member
273 .COR = 0x4c,
310 .COR = 0x5c,
796 cur_cor = at91_adc_readl(st, COR); in at91_adc_cor()
799 at91_adc_writel(st, COR, cur_cor | cor); in at91_adc_cor()
801 at91_adc_writel(st, COR, cur_cor & ~cor); in at91_adc_cor()
/openbmc/qemu/docs/specs/
H A Drocker.rst39 * Register are (R) read-only, (R/W) read/write, (W) write-only, or (COR) clear
/openbmc/qemu/qapi/
H A Dblock-core.json4591 # that limits the COR operations in the backing chain (inclusive),