| /linux-4.1.27/tools/power/cpupower/debug/i386/ |
| D | dump_psb.c | 24 static long relevant; variable
114 if (relevant != 0) { in decode_psb()
115 if (relevant!= pst->cpuid) in decode_psb()
166 relevant = strtol(optarg, NULL, 16); in main()
|
| /linux-4.1.27/Documentation/virtual/kvm/devices/ |
| D | mpic.txt | 26 to the relevant MSIIR.
37 byte offset of the relevant IVPR from EIVPR0, divided by 32.
|
| /linux-4.1.27/Documentation/devicetree/bindings/spi/ |
| D | spi-sc18is602.txt | 14 The clock-frequency property is relevant and needed only if the chip has an
|
| /linux-4.1.27/drivers/misc/ti-st/ |
| D | Kconfig | 14 are returned to relevant protocol drivers based on their
|
| /linux-4.1.27/ |
| D | REPORTING-BUGS | 46 device driver in the MAINTAINERS file. Search in the file for relevant
77 bugs at once, it's difficult for maintainers to tease apart the relevant
98 relevant to your bug, feel free to exclude it.
126 [8.7.] Other information that might be relevant to the problem
128 think to be relevant):
|
| D | README | 328 relevant mailing-list or to the newsgroup.
|
| D | MAINTAINERS | 27 5. Make a patch available to the relevant maintainer in the list. Use
75 L: Mailing list that is relevant to this area
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | abi.txt | 8 This path is binary emulation relevant aka personality types aka abi.
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | PAS16 | 9 This documentation is relevant for the PAS16 driver (pas2_card.c and
13 relevant docs first.
15 The following information is relevant information from README.OSS
63 The following configuration options are relevant to configuring the PAS16:
|
| D | Introduction | 379 6) By just loading the module and let isapnp do everything relevant
|
| /linux-4.1.27/Documentation/devicetree/bindings/soc/fsl/ |
| D | bman.txt | 80 The following constraints are relevant to the FBPR private memory:
86 via the Reset Configuration Word (RCW) and that are relevant to a specific board
|
| D | qman.txt | 97 The following constraints are relevant to the FQD and PFDR private memory:
103 configured via the Reset Configuration Word (RCW) and that are relevant to a
|
| /linux-4.1.27/Documentation/devicetree/bindings/mtd/ |
| D | gpmc-onenand.txt | 6 All timing relevant properties as well as generic gpmc child properties are
|
| D | gpmc-nor.txt | 6 All timing relevant properties as well as generic GPMC child properties are
|
| D | gpmc-nand.txt | 6 All timing relevant properties as well as generic gpmc child properties are
|
| /linux-4.1.27/scripts/coccinelle/free/ |
| D | ifnullfree.cocci | 52 …ve_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to avoid pas…
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | gpmc-eth.txt | 10 All timing relevant properties as well as generic GPMC child properties are
14 For the properties relevant to the ethernet controller connected to the GPMC
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-class-net-statistics | 7 This value might not be relevant with all MAC layers.
32 network device. This value might only be relevant for interfaces
145 this might only be relevant for devices that support
|
| D | sysfs-bus-rbd | 89 all relevant datastructures accordingly.
|
| D | sysfs-bus-iio | 47 relevant directories. If it effects all of the above
1102 and the relevant _type attributes to establish the data storage
|
| /linux-4.1.27/Documentation/devicetree/bindings/i2c/ |
| D | i2c-opal.txt | 13 the relevant OPAL functions.
|
| D | i2c-mux-pinctrl.txt | 47 Whenever an access is made to a device on a child bus, the relevant pinctrl
|
| /linux-4.1.27/Documentation/devicetree/bindings/input/ |
| D | rotary-encoder.txt | 10 encoder. Only relevant for absolute axis. Defaults to 24 which is a
|
| /linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 11 at the relevant CPU datasheet from Samsung.
95 relevant clocks and peripherals setup before use (ie, bootloader).
|
| D | GPIO.txt | 69 does not implicitly configure the relevant gpio to output. The gpio
152 These calls are now implemented by the relevant gpiolib calls, convert
|
| D | Overview.txt | 277 and then sets the relevant device's platform data. Making
|
| /linux-4.1.27/Documentation/devicetree/bindings/ |
| D | chosen.txt | 28 must be specified in the relevant binding documentation.
|
| D | graph.txt | 119 are required in a relevant parent node:
|
| D | xilinx.txt | 12 extract the device parameters relevant to device drivers and copy them
|
| /linux-4.1.27/Documentation/usb/ |
| D | ohci.txt | 28 work on while the OS is getting around to the relevant IRQ processing.
|
| D | power-management.txt | 134 relevant attribute files are: wakeup, control, and
527 relevant attribute files is usb2_hardware_lpm.
602 Example of the relevant files for port power control. Note, in this example
652 Sysfs files relevant for port power control:
|
| D | URB.txt | 18 - An URB consists of all relevant information to execute any USB transaction
|
| /linux-4.1.27/arch/alpha/lib/ |
| D | ev6-memset.S | 86 mskql $4,$16,$4 # U : clear relevant parts of the quad
263 mskql $4,$16,$4 # U : clear relevant parts of the quad
450 mskql $4,$16,$4 # U : clear relevant parts of the quad
|
| D | ev67-strchr.S | 41 mskqh t4, a0, t4 # U : only want relevant part of first quad
|
| /linux-4.1.27/Documentation/scsi/ |
| D | 53c700.txt | 71 the relevant request_*_region function and place the register base
85 where host is the return from the relevant NCR_700_detect() routine.
|
| D | scsi_mid_low_api.txt | 348 by the relevant gcc compilers. So C99 style structure and array
1367 relevant to LLDs is struct Scsi_Host::host_lock and there is
|
| D | st.txt | 446 a mask to select the relevant bits (the bits 9-16), and the
|
| D | BusLogic.txt | 55 relevant to SCSI operations, and a detailed description of your system's
|
| D | ChangeLog.lpfc | 17 to luns on nodes in NPR or other relevant states (PLOGI,
|
| /linux-4.1.27/Documentation/fb/ |
| D | cmap_xfbdev.txt | 6 *. example of relevant structures in fbdev as used for a 3-bit grayscale cmap
|
| D | sisfb.txt | 84 means 24bit color depth (but 32 bit framebuffer depth, which is not relevant
|
| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | cs42l56.txt | 40 0 = Adapt to Volume Mode. Voltage level determined by the sum of the relevant volume settings.
|
| /linux-4.1.27/Documentation/arm/OMAP/ |
| D | DSS | 53 well. Hence, it is relevant to update the DSS device driver to provide an audio
57 The audio_enable function is intended to prepare the relevant
68 The audio_config function is intended to configure all the relevant audio
280 After this the configuration looks like (only relevant parts shown):
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README.hfc-pci | 7 for a HFC-PCI card is reduced to 1. Of course this is only relevant to
|
| D | README.gigaset | 376 - relevant system log messages (it would help if you activate debug
|
| /linux-4.1.27/arch/arm/mach-vexpress/ |
| D | Kconfig | 51 build a working kernel, you must also enable relevant core
|
| /linux-4.1.27/Documentation/blackfin/ |
| D | bfin-gpio-notes.txt | 27 or the relevant HRM.
|
| /linux-4.1.27/Documentation/networking/ |
| D | netdev-features.txt | 18 There are currently three sets of features relevant to the driver, and
118 On platforms where this is relevant, NETIF_F_HIGHDMA signals that
|
| D | nf_conntrack-sysctl.txt | 38 This option is only relevant when "reliable connection tracking
|
| D | nfc.txt | 96 relevant information such as the supported NFC protocols.
|
| D | timestamping.txt | 109 are only reported for packets that also have the relevant timestamp
225 relevant sequence number in skb_shinfo(skb)->tskey. Because an skbuff
278 relevant metadata structures. The recvmsg call returns the original
|
| D | fib_trie.txt | 6 An end node with data. This has a copy of the relevant key, along
|
| D | vortex.txt | 229 Enable Wake-on-LAN support for the relevant interface. Donald
386 o If it is a PCI device, the relevant output from 'lspci -vx', eg:
|
| D | batman-adv.txt | 109 All interfaces added to batman advanced are not relevant any
|
| D | can.txt | 408 the mapping to the bus-relevant data length code (DLC), see chapter 6.6.
816 data bytes of the first CAN frame contain the mask of relevant bits that
819 mark the relevant content to be compared with the previous received content.
1165 CAN frames anyway. The payload length to the bus-relevant DLC mapping is
|
| D | openvswitch.txt | 31 kernel module to remain relevant, it must be possible for newer
|
| D | stmmac.txt | 283 4.11) This is a summary of the content of some relevant files:
|
| D | scaling.txt | 194 and cache contention) and toggled per CPU by setting the relevant bit
|
| D | packet_mmap.txt | 1037 ii) call sendto() e.g. in blocking mode, iii) wait for status of relevant
|
| D | filter.txt | 62 following relevant structures:
|
| D | bonding.txt | 1548 typically selected by the bonding driver, and is not relevant to the user or
2424 relevant interface(s).
|
| /linux-4.1.27/tools/testing/selftests/rcutorture/doc/ |
| D | initrd.txt | 54 # Export relevant variables
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | videobuf | 240 calls. The relevant helper functions are:
278 <media/videobuf-dma-sg.h>) includes a couple of relevant fields:
343 The final step is to set the size field of the relevant videobuf_buffer
349 Developers who are interested in more information can go into the relevant
|
| D | fimc.txt | 136 You can either grep through the kernel log to find relevant information, i.e.
|
| D | v4l2-framework.txt | 415 controlled through GPIO pins. This distinction is only relevant when setting
1061 merging any relevant data from the old payload into the new payload that
1155 It is expected that once the CCF becomes available on all relevant
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | pcf8591 | 62 try. You have to explicitly instantiate the device at the relevant
|
| D | it87 | 186 * in9 (relevant for IT8603E only)
|
| /linux-4.1.27/Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-dma.txt | 36 they are relevant only from DMA perspective. The QMSS may not choose to
|
| /linux-4.1.27/Documentation/devicetree/bindings/power/ |
| D | rockchip-io-domain.txt | 40 a phandle the relevant regulator. All specified supplies must be able
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | xfs.txt | 138 controls the size of each buffer and so is also relevant to
162 boundaries. This is only relevant to filesystems created
199 block units. These options are only relevant to filesystems
|
| D | ramfs-rootfs-initramfs.txt | 313 3) The GNU project standardizing on tar is approximately as relevant as
|
| D | autofs4-mount-control.txt | 374 number of the mount and field arg2 to the relevant super block magic
|
| D | Locking | 3 prototypes or locking protocols - update this file. And update the relevant
|
| D | proc.txt | 674 The above IRQ vectors are displayed only when relevant. For example,
757 More information relevant to external fragmentation can be found in
|
| D | coda.txt | 855 relevant. It indicates success or the type of failure.
|
| /linux-4.1.27/Documentation/arm/ |
| D | Booting | 7 The following documentation is relevant to 2.4.18-rmk6 and beyond.
50 As an alternative, the boot loader can pass the relevant 'console='
|
| D | Porting | 39 Physical address to place the initial RAM disk. Only relevant if
|
| D | vlocks.txt | 195 grabbing most of this text out of the relevant mail thread and writing
|
| D | README | 51 When sending bug reports, please ensure that they contain all relevant
|
| /linux-4.1.27/Documentation/ |
| D | BUG-HUNTING | 24 give up. Report as much as you have found to the relevant maintainer. See
227 and list the relevant code.
|
| D | SubmitChecklist | 39 8: Has been carefully reviewed with respect to relevant Kconfig
|
| D | rpmsg.txt | 172 relevant inbound messages arrive (i.e. messages which their dst address
289 If/when a relevant rpmsg driver is registered, it will be immediately probed
|
| D | stable_kernel_rules.txt | 100 other developers and by the relevant subsystem maintainer.
|
| D | oops-tracing.txt | 11 If you are unsure send it to the person responsible for the code relevant to
|
| D | cpu-hotplug.txt | 94 of them may be online. When physical hotplug is processed by the relevant
|
| D | initrd.txt | 104 The name is not relevant. More details can be found on the pivot_root(2)
|
| D | SubmittingPatches | 168 bug, summarize the relevant points of the discussion that led to the
704 on bigger patches. Other comments relevant only to the moment or the
|
| D | md.txt | 178 This is the size in bytes for 'chunks' and is only relevant to
|
| D | kernel-docs.txt | 650 Description: Weekly newsletter covering the most relevant
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 5.Posting | 139 changelogs. This message is usually formatted with the relevant
206 maintainer of the relevant code) that the patch is appropriate for
257 relevant people will see your posting on the mailing lists. In particular,
270 - Send a copy to the relevant mailing list, or, if nothing else applies,
|
| D | 7.AdvancedTopics | 128 occasional summary of the tree to the relevant list, and, when the time is
137 When requesting a pull, be sure to give all the relevant information: where
|
| D | 3.Early-stage | 125 the MAINTAINERS file for a relevant place to post. If there is a suitable
128 relevant subsystem and the environment may be more supportive.
|
| D | 2.Process | 154 - Early review. Patches are posted to the relevant mailing list, and
160 inclusion, it should be accepted by a relevant subsystem maintainer -
|
| D | 1.Intro | 135 relevant aspects of the kernel development process; most of these will be
|
| D | 4.Coding | 321 of the solution, the people who worked on the patch, any relevant
|
| /linux-4.1.27/Documentation/devicetree/bindings/video/ |
| D | ti,omap-dss.txt | 45 A shortened example of the DSS description for OMAP4, with non-relevant parts
|
| /linux-4.1.27/Documentation/RCU/ |
| D | NMI-RCU.txt | 11 The relevant pieces of code are listed below, each followed by a
|
| D | stallwarn.txt | 155 If the relevant grace-period kthread has been unable to run prior to
|
| D | RTFP.txt | 29 mechanism to be used in production. Furthermore, the relevant patent
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | provider.txt | 96 For more information on the Async TX API, please look the relevant
259 - These functions all take the buffer or the scatterlist relevant
344 - Not really relevant any more since the introduction of virt-dma
|
| /linux-4.1.27/arch/cris/arch-v32/mm/ |
| D | mmu.S | 37 ; Bus fault handler. Extracts relevant information and calls mm subsystem
|
| /linux-4.1.27/drivers/staging/i2o/ |
| D | Kconfig | 10 be used under different operating systems if the relevant OSM is in
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | boot-options.txt | 218 iommu options only relevant to the AMD GART hardware IOMMU:
243 iommu options only relevant to the software bounce buffering (SWIOTLB) IOMMU
|
| /linux-4.1.27/arch/arm/mm/ |
| D | abort-lv4t.S | 32 add pc, pc, r7, lsr #22 @ Now branch to the relevant processing routine
|
| /linux-4.1.27/Documentation/crypto/ |
| D | asymmetric-keys.txt | 30 a TPM) that might be used to both retain the relevant key and perform
130 transferred the relevant bits to the structure pointed to by sig.
|
| /linux-4.1.27/Documentation/i2c/ |
| D | fault-codes | 110 Returned when slave does not conform to the relevant I2C
|
| /linux-4.1.27/drivers/net/phy/ |
| D | Kconfig | 136 drive the relevant pins.
|
| /linux-4.1.27/Documentation/power/regulator/ |
| D | overview.txt | 132 relevant to non SoC devices and is split into the following four interfaces:-
|
| /linux-4.1.27/Documentation/trace/ |
| D | ftrace-design.txt | 48 be (semi-)relevant.
114 ftrace_graph_entry_stub). If either of those is not set to the relevant stub
|
| /linux-4.1.27/Documentation/locking/ |
| D | mutex-design.txt | 111 - Detects self-recursing locks and prints out all relevant info.
|
| /linux-4.1.27/Documentation/kbuild/ |
| D | kconfig-language.txt | 354 relevant for some architectures but not all.
356 that is defined in a common Kconfig file and selected by the relevant
|
| D | modules.txt | 325 kbuild will add options to "gcc" so the relevant directories
|
| D | makefiles.txt | 1049 but executing "make help" will list all relevant targets.
1249 Each relevant directory contains a file name "Kbuild" which specifies the
|
| /linux-4.1.27/Documentation/spi/ |
| D | spi-summary | 119 Note that the clock mode is relevant as soon as the chipselect goes
246 * visible on the relevant pins ... bootloaders on
412 that you've already provided the relevant DMA addresses.
|
| /linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-bindings.txt | 163 where they are applicable; not all of these properties are relevant or useful
|
| /linux-4.1.27/drivers/video/fbdev/aty/ |
| D | mach64_ct.c | 497 FIXME: is it relevant for us? in aty_init_pll_ct()
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 64 are required in a relevant parent node:
|
| /linux-4.1.27/Documentation/power/ |
| D | devices.txt | 37 using the relevant /sys/devices/.../power/wakeup file (for Ethernet
136 or USB, or device type and device class drivers. They also are relevant to the
433 suspending: I/O can be performed using DMA and IRQs, and the relevant clocks are
618 The support for device power management domains is only relevant to platforms
|
| D | runtime_pm.txt | 61 If the subsystem chosen by applying the above rules doesn't provide the relevant
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | floppy.txt | 119 Sets the FIFO threshold. This is mostly relevant in DMA
|
| D | paride.txt | 66 The high-level drivers function according to the relevant standards.
|
| D | README.DAC960 | 40 by the driver at startup, along with any subsequent system messages relevant to
|
| /linux-4.1.27/Documentation/gpio/ |
| D | driver.txt | 132 - Make sure to assign all relevant members of the struct gpio_chip so that
|
| D | gpio-legacy.txt | 99 to the relevant schematics. In contrast, drivers should only use GPIO
|
| /linux-4.1.27/Documentation/arm64/ |
| D | booting.txt | 8 is relevant to all public releases of the AArch64 Linux kernel.
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | CMIPCI.txt | 141 Additionally there are relevant control switches:
|
| D | timestamping.txt | 69 audio time it wants reported by selecting the relevant settings in
|
| /linux-4.1.27/Documentation/ia64/ |
| D | mca.txt | 46 preformatted with just enough task state to let the relevant handlers
|
| /linux-4.1.27/Documentation/x86/ |
| D | intel_mpx.txt | 54 bounds table (in the user address space) and makes the relevant entry
|
| D | boot.txt | 761 relevant to the boot loader itself, see "special command line options"
|
| /linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | fman.txt | 389 due to a hardware problem), or to advertise that all relevant
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | timekeeping.txt | 26 The purpose of this document is to collect data and information relevant to
28 information relevant to KVM and hardware-based virtualization.
|
| /linux-4.1.27/scripts/ |
| D | spelling.txt | 800 relevent||relevant
|
| /linux-4.1.27/Documentation/serial/ |
| D | driver | 87 by 'port' to the state described by mctrl. The relevant bits
|
| /linux-4.1.27/Documentation/kdump/ |
| D | kdump.txt | 413 of kernel memory for devices that are not relevant for kdump. The same
|
| /linux-4.1.27/arch/m68k/fpsp040/ |
| D | setox.S | 180 | the FMOVEM may not seem relevant since X is normalized,
|
| /linux-4.1.27/Documentation/vm/ |
| D | transhuge.txt | 265 page (like for checking page->mapping or other bits that are relevant
|
| /linux-4.1.27/Documentation/input/ |
| D | atarikbd.txt | 539 relevant SET command.
|
| /linux-4.1.27/drivers/ata/ |
| D | Kconfig | 9 uses pata-platform driver to enable the relevant driver in the
|
| /linux-4.1.27/Documentation/mtd/ |
| D | nand_ecc.txt | 160 end filter out the relevant bits. This is pretty nice as it will bring
|
| /linux-4.1.27/Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 146 information relevant to the data in the IP packet. Each tag begins with
|
| /linux-4.1.27/Documentation/block/ |
| D | biodoc.txt | 385 or filesystem block size alignment restrictions which may not be relevant
502 Only some relevant fields (mainly those which changed or may be referred
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 279 relevant for userspace, say 'Y', and check the headers
481 out which slabs are relevant to a particular load.
|
| /linux-4.1.27/init/ |
| D | Kconfig | 126 Compression speed is only relevant when building a kernel.
127 Decompression speed is relevant at each boot.
|
| /linux-4.1.27/drivers/i2c/busses/ |
| D | Kconfig | 424 Support for CBUS access using I2C API. Mostly relevant for Nokia
|
| /linux-4.1.27/drivers/mfd/ |
| D | Kconfig | 1419 supported via the relevant subsystems. This driver provides
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig.debug | 1095 choose the relevant UART0 base address.
|
| D | Kconfig | 1201 relevant cache maintenance functions and sets a specific bit
|
| /linux-4.1.27/Documentation/security/ |
| D | keys.txt | 11 kernel service can search for relevant keys.
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 923 You are welcome to add any property you find relevant to your board,
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 2507 isn't very relevant.
|
| /linux-4.1.27/arch/m68k/ifpsp060/src/ |
| D | fplsp.S | 6839 # the FMOVEM may not seem relevant since X is normalized, #
|