| /linux/include/media/ |
| H A D | dvb_ca_en50221.h | 95 * @slot: Slot concerned.
105 * @slot: Slot concerned.
113 * @slot: Slot concerned.
|
| H A D | dvb_ringbuffer.h | 225 * @rbuf: Ringbuffer concerned.
249 * @rbuf: Ringbuffer concerned.
263 * @rbuf: Ring buffer concerned.
271 * @rbuf: Ringbuffer concerned.
|
| /linux/Documentation/scsi/ |
| H A D | libsas.rst | 9 layout is as follows: while SCSI Core is concerned with
10 SAM/SPC issues, and a SAS LLDD+sequencer is concerned with
11 phy/OOB/link management, the SAS layer is concerned with:
24 A SAS LLDD is a PCI device driver. It is concerned with
|
| /linux/drivers/media/dvb-core/ |
| H A D | dvb_ca_en50221.c | 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.
|
| /linux/drivers/media/pci/ddbridge/ |
| H A D | Kconfig | 45 If you're unsure, concerned about stability and don't want to pass
|
| /linux/LICENSES/exceptions/ |
| H A D | Linux-syscall-note | 21 is concerned is _this_ particular version of the license (ie v2, not
|
| /linux/arch/sh/kernel/cpu/sh2a/ |
| H A D | probe.c | 52 * concerned. The only real difference in hardware is that the icache in cpu_probe()
|
| /linux/Documentation/networking/ |
| H A D | x25.rst | 16 Packet Layer is concerned, the link layer was being performed by a lower
|
| /linux/include/linux/firmware/ |
| H A D | trusted_foundations.h | 10 * Tegra-based devices sold on the market are concerned). Such devices can only
|
| /linux/sound/ |
| H A D | Kconfig | 111 sound although they're sharing the AC97 bus. Concerned drivers
|
| /linux/Documentation/power/ |
| H A D | drivers-testing.rst | 44 concerned, it should not matter whether or not the driver is built as a
|
| /linux/arch/arm64/kernel/ |
| H A D | acpi_parking_protocol.c | 70 * is concerned). in acpi_parking_protocol_cpu_boot()
|
| /linux/drivers/clk/sunxi-ng/ |
| H A D | ccu_phase.c | 100 * only thing that we're concerned about is the number in ccu_phase_set_phase()
|
| /linux/arch/arm/include/asm/ |
| H A D | mmu_context.h | 112 * is concerned. No registers are touched. We avoid
|
| /linux/arch/powerpc/mm/book3s32/ |
| H A D | tlb.c | 41 * tlb as far as the linux tables are concerned, flush it too.
|
| /linux/sound/soc/codecs/ |
| H A D | peb2466.c | 950 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_thfilter()
999 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_imr1filter()
1042 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_frxfilter()
1080 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_frrfilter()
1118 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_axfilter()
1156 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_arfilter()
1205 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_axtable()
1309 * - @0 1 byte: Chan mask (bit set means related channel is concerned) in peb2466_fw_parse_artable()
|
| /linux/drivers/net/ethernet/freescale/enetc/ |
| H A D | enetc_ierb.c | 15 * concerned with partitioning the FIFO, because the default values configure
|
| /linux/Documentation/filesystems/ |
| H A D | idmappings.rst | 136 The kernel is mostly concerned with kernel ids. They are used when performing
142 Note that we are only concerned with idmappings as the kernel stores them not
156 going to be concerned with how idmappings are created nor how they are used
344 itself. So we're concerned with what happens when e.g. ``vfs_mkdir()`` is
|
| /linux/Documentation/admin-guide/laptops/ |
| H A D | disk-shock-protection.rst | 90 IDE) configurations are concerned, there can only be two devices
|
| /linux/arch/powerpc/include/asm/ |
| H A D | uninorth.h | 75 * As far as AGP "features" are concerned, it looks like fast write may
|
| /linux/drivers/usb/dwc3/ |
| H A D | dwc3-qcom-legacy.c | 241 * @qcom: Pointer to the concerned usb core.
293 * @qcom: Pointer to the concerned usb core.
|
| /linux/drivers/clk/sunxi/ |
| H A D | clk-mod0.c | 256 * only thing that we're concerned about is the number in mmc_set_phase()
|
| /linux/drivers/clk/ti/ |
| H A D | clk-3xxx.c | 73 * target IDLEST bits. For our purposes, we are concerned with the
|
| /linux/Documentation/process/ |
| H A D | 3.Early-stage.rst | 52 more concerned about system stability, long-term maintenance, and finding
|
| /linux/Documentation/block/ |
| H A D | data-integrity.rst | 108 the kernel) is concerned, the integrity metadata is opaque information
|