Searched full:concerned (Results 1 – 25 of 178) sorted by relevance
12345678
320 * @se: Pointer to the concerned serial engine.335 * @se: Pointer to the concerned serial engine.352 * @se: Pointer to the concerned serial engine.373 * @se: Pointer to the concerned serial engine.386 * @se: Pointer to the concerned serial engine.398 * @se: Pointer to the concerned serial engine.411 * @se: Pointer to the concerned serial engine.424 * @se: Pointer to the concerned serial engine.451 * @se: Pointer to the concerned serial engine.470 * @se: Pointer to the concerned serial engine.
78 * of driver also supports operations (eg. initialize the concerned serial248 * @se: Pointer to the concerned serial engine.344 * @se: Pointer to the concerned serial engine.420 * @se: Pointer to the concerned serial engine496 * @se: Pointer to the concerned serial engine.534 * @se: Pointer to the concerned serial engine.559 * @se: Pointer to the concerned serial engine.601 * @se: Pointer to the concerned serial engine.668 * @se: Pointer to the concerned serial engine.691 * @se: Pointer to the concerned serial engine.[all …]
95 * @slot: Slot concerned.105 * @slot: Slot concerned.113 * @slot: Slot concerned.
225 * @rbuf: Ringbuffer concerned.249 * @rbuf: Ringbuffer concerned.263 * @rbuf: Ring buffer concerned.271 * @rbuf: Ringbuffer concerned.
9 layout is as follows: while SCSI Core is concerned with10 SAM/SPC issues, and a SAS LLDD+sequencer is concerned with11 phy/OOB/link management, the SAS layer is concerned with:24 A SAS LLDD is a PCI device driver. It is concerned with
18 * between these as far as Linux is concerned, but let's keep things
141 * between these as far as Linux is concerned, but let's keep things
936 * @slot: Slot concerned.966 * @slot: Slot concerned.986 * @slot: Slot concerned.1338 * @file: File concerned.1424 * @file: File concerned.1706 * @inode: Inode concerned.1707 * @file: File concerned.1767 * @inode: Inode concerned.1768 * @file: File concerned.1805 * @file: File concerned.
21 is concerned is _this_ particular version of the license (ie v2, not
45 If you're unsure, concerned about stability and don't want to pass
52 * concerned. The only real difference in hardware is that the icache in cpu_probe()
16 Packet Layer is concerned, the link layer was being performed by a lower
10 * Tegra-based devices sold on the market are concerned). Such devices can only
18 SPI-NAND devices are concerned by this description.
111 sound although they're sharing the AC97 bus. Concerned drivers
72 * concerned. The rest of the kernel trusts that in mm_pkey_alloc()
44 concerned, it should not matter whether or not the driver is built as a
86 * concerned. The rest of the kernel trusts that in mm_pkey_alloc()
70 * is concerned). in acpi_parking_protocol_cpu_boot()
100 * only thing that we're concerned about is the number in ccu_phase_set_phase()
41 * tlb as far as the linux tables are concerned, flush it too.
112 * is concerned. No registers are touched. We avoid
100 recurring timers to migrate elsewhere. If you are concerned185 timers to migrate elsewhere. If you are concerned with multiple
947 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_thfilter()996 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_imr1filter()1039 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_frxfilter()1077 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_frrfilter()1115 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_axfilter()1153 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_arfilter()1202 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_axtable()1306 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_artable()
89 * valid as far as the hardware is concerned. The rest of the kernel in mm_pkey_alloc()