| /linux-4.4.14/drivers/net/wireless/b43/ |
| D | leds.c | 161 enum b43_led_behaviour behaviour, in b43_map_led() argument
169 switch (behaviour) { in b43_map_led()
208 behaviour); in b43_map_led()
215 enum b43_led_behaviour *behaviour, in b43_led_get_sprominfo() argument
231 *behaviour = B43_LED_ACTIVITY; in b43_led_get_sprominfo()
234 *behaviour = B43_LED_RADIO_ALL; in b43_led_get_sprominfo()
237 *behaviour = B43_LED_RADIO_B; in b43_led_get_sprominfo()
239 *behaviour = B43_LED_ASSOC; in b43_led_get_sprominfo()
242 *behaviour = B43_LED_RADIO_A; in b43_led_get_sprominfo()
245 *behaviour = B43_LED_OFF; in b43_led_get_sprominfo()
[all …]
|
| /linux-4.4.14/drivers/net/wireless/b43legacy/ |
| D | leds.c | 130 enum b43legacy_led_behaviour behaviour, in b43legacy_map_led() argument
138 switch (behaviour) { in b43legacy_map_led()
184 behaviour); in b43legacy_map_led()
194 enum b43legacy_led_behaviour behaviour; in b43legacy_leds_init() local
209 behaviour = B43legacy_LED_ACTIVITY; in b43legacy_leds_init()
212 behaviour = B43legacy_LED_RADIO_ALL; in b43legacy_leds_init()
215 behaviour = B43legacy_LED_RADIO_B; in b43legacy_leds_init()
217 behaviour = B43legacy_LED_ASSOC; in b43legacy_leds_init()
220 behaviour = B43legacy_LED_RADIO_A; in b43legacy_leds_init()
223 behaviour = B43legacy_LED_OFF; in b43legacy_leds_init()
[all …]
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | ESS | 6 (and you chip is pnp capable) the default behaviour is 2.0 behaviour which
|
| D | ultrasound | 23 as the old behaviour. If set to 1, no DMA is needed for downloading samples,
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-flakey.txt | 5 unreliable behaviour periodically. It's been found useful in simulating
9 <up interval> seconds, then exhibits unreliable behaviour for <down
|
| D | cache.txt | 199 Without this argument, the default behaviour is to write
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | ABI.txt | 12 then default to the previous behaviour if it is missing. If a binding
29 behaviour when a newly added property is missing.
|
| D | xilinx.txt | 8 synthesised with different options that change the behaviour.
|
| /linux-4.4.14/Documentation/arm/ |
| D | mem_alignment | 22 Please note that randomly changing the behaviour without good thought is
23 real bad - it changes the behaviour of all unaligned instructions in user
|
| /linux-4.4.14/Documentation/usb/ |
| D | functionfs.txt | 4 unique behaviour. It may be added to an USB configuration only after
57 parameter's value is just a one-element list, then the behaviour
|
| D | usb-serial.txt | 437 supported by the driver. The protocol was analyzed from the behaviour
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | xfs.txt | 22 default behaviour.
30 The default behaviour is for dynamic end-of-file
35 the dynamic behaviour.
46 The default behaviour is determined by the on-disk feature
47 bit indicating that attr2 behaviour is active. If either
126 (in bytes) will be returned instead. Otherwise the behaviour
|
| D | mandatory-locking.txt | 86 Generally I have tried to make the most sense out of the behaviour exhibited
102 paranoid HP-UX behaviour.
|
| D | ntfs.txt | 144 Otherwise the default behaviour is to abort mount if
148 in directory listings. Otherwise the default behaviour
159 namespace. Otherwise the default behaviour is to treat
173 is consistent with the behaviour of traditional Unix
|
| D | ext4.txt | 594 behaviour. Note that this will also start
596 behaviour may change in the future as it is
|
| D | hpfs.txt | 238 Changed behaviour on HPFS386: It is now possible to operate on HPFS386 in
|
| D | ext2.txt | 164 behaviour on a per-file basis. There are flags for secure deletion,
|
| D | spufs.txt | 36 supported operations and the deviations from the behaviour in the
|
| D | Locking | 241 "sync". These are quite different operations and the behaviour may differ
|
| D | xfs-delayed-logging-design.txt | 785 behaviour, allocation or freeing that don't already exist.
|
| D | proc.txt | 1871 specific program (given the program doesn't reveal itself by its behaviour).
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra30-actmon.txt | 3 The activity monitor block collects statistics about the behaviour of other
|
| /linux-4.4.14/Documentation/ |
| D | nommu-mmap.txt | 12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
16 The behaviour is similar between the MMU and no-MMU cases, but not identical;
31 the no-MMU case doesn't support these, behaviour is identical to
285 fragmentation, and as such, is left configurable. The default behaviour is to
288 behaviour can either be disabled completely, or bumped up to a higher page
291 Page trimming behaviour is configurable via the sysctl `vm.nr_trim_pages'.
|
| D | mailbox.txt | 49 * This is the handler for data received from remote. The behaviour is purely
|
| D | dynamic-debug-howto.txt | 38 The behaviour of pr_debug()/dev_dbg()s are controlled via writing to a
57 You can view the currently configured behaviour of all the debug
|
| D | unicode.txt | 46 U+F0FF, emulating the previous behaviour. In practice, this range
|
| D | lzo.txt | 59 were copied may change the meaning and behaviour of the next instruction. In
|
| D | binfmt_misc.txt | 121 cause unexpected behaviour and can be a security hazard.
|
| D | printk-formats.txt | 64 users. The behaviour of %pK depends on the kptr_restrict sysctl - see
|
| D | unaligned-memory-access.txt | 4 Linux runs on a wide variety of architectures which have varying behaviour
|
| D | svga.txt | 207 happens and how do the configuration switches affect the behaviour of the bug.
|
| D | adding-syscalls.txt | 85 zero value gives the previous behaviour, then this allows both directions of
|
| D | edac.txt | 661 To return to the default behaviour of matching any, you can do:
|
| D | kernel-parameters.txt | 408 behaviour to be specified. Bit 0 enables warnings,
2299 To turn off this behaviour, set the value to '0'.
2320 If you want to enable the kernel legacy behaviour of
2520 behaviour
2668 panic= [KNL] Kernel behaviour on panic: delay <timeout>
|
| D | kmemcheck.txt | 369 441 * queued once. Changing the restart behaviour to
|
| D | SubmittingPatches | 158 its behaviour.
|
| D | memory-barriers.txt | 539 isn't, and this behaviour can be observed on certain real CPUs (such as the DEC
|
| /linux-4.4.14/arch/unicore32/mm/ |
| D | Kconfig | 5 # optimiser behaviour.
|
| /linux-4.4.14/drivers/memstick/core/ |
| D | Kconfig | 12 normal behaviour is to remove them at suspend and
|
| /linux-4.4.14/Documentation/acpi/ |
| D | video_extension.txt | 103 directly. This behaviour can be controlled through the brightness_switch_enabled
105 disable this behaviour once a GUI environment starts up and wants to have full
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-rt-group.txt | 13 2.2 Default behaviour
105 2.2 Default behaviour
112 it. By setting runtime to -1 you'd get the old behaviour back.
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | jz4780-dma.txt | 18 can be configured to have special behaviour for NAND/BCH when using
|
| /linux-4.4.14/Documentation/thermal/ |
| D | cpu-cooling-api.txt | 92 - In running time the 'execution' behaviour (instruction types, memory
101 f(run) here represents the described execution behaviour and its
105 The detailed behaviour for f(run) could be modelled on-line. However,
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | abituguru-datasheet | 219 Alarm behaviour for the selected sensor. A 1 enables the described behaviour.
293 Alarm behaviour for the selected sensor. A 1 enables the described behaviour.
|
| D | lm85 | 189 the behaviour of fans. Write 1 to let fans spinning at
|
| /linux-4.4.14/Documentation/networking/ |
| D | x25.txt | 29 format and behaviour of the protocol. If time permits this option will also
|
| D | cdc_mbim.txt | 16 behaviour for NCM 1.0 backwards compatible MBIM functions (an
276 behaviour is triggered by adding a VLAN link for the magic VLAN ID
|
| D | netdev-features.txt | 130 stack. Driver should not change behaviour based on them.
|
| D | batman-adv.txt | 87 Other files allow to change batman's behaviour to better fit your
|
| D | ip-sysctl.txt | 909 This is the behaviour network many administrators will expect from
1098 balancing, does this behaviour cause problems.
1354 The functional behaviour for certain settings is different
1368 2 Overrule forwarding behaviour. Accept Router Advertisements
1454 Configure interface-specific Host/Router behaviour.
1465 By default, Host behaviour is assumed. This means:
1476 If local forwarding is enabled, Router behaviour is assumed.
|
| D | dccp.txt | 145 the behaviour of the other, passive side: this variable also sets
|
| D | pktgen.txt | 154 pgset "flag [name]" Set a flag to determine behaviour. Current flags
|
| D | e1000e.txt | 64 The default behaviour of the driver previously assumed a static
|
| D | vortex.txt | 249 switch back to 10baseT. This behaviour could not be prevented with a
|
| D | can.txt | 213 networking behaviour for CAN applications. Due to some requests from
544 disabled by default. This default behaviour may be changed on
741 contain the following flag definitions which influence the behaviour:
|
| D | e1000.txt | 96 The default behaviour of the driver previously assumed a static
|
| D | z8530drv.txt | 318 to emulate the old behaviour. The cost of using these programs is
|
| D | ppp_generic.txt | 57 program to control aspects of the channel's behaviour. This
|
| D | cs89x0.txt | 247 with device probing. To avoid this behaviour, add one
|
| /linux-4.4.14/lib/ |
| D | Kconfig.kmemcheck | 32 This option controls the default behaviour of kmemcheck when the
|
| D | Kconfig.kgdb | 113 This integer controls the behaviour of kdb when the kernel gets a
|
| D | Kconfig.debug | 879 This is to ensure no erroneous behaviour occurs which could result in
|
| /linux-4.4.14/Documentation/block/ |
| D | deadline-iosched.txt | 43 a value of 1 yields first-come first-served behaviour). Increasing fifo_batch
|
| D | biodoc.txt | 559 The behaviour of the various sector counts are almost the same as before,
|
| /linux-4.4.14/Documentation/i2c/ |
| D | slave-interface | 43 behaviour and setup.
154 It is good behaviour to always ACK the address phase, so the master knows if a
|
| /linux-4.4.14/arch/metag/mm/ |
| D | Kconfig | 49 allocation behaviour.
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 31 sleep and how it resumes. The default behaviour of the Linux code
|
| D | GPIO.txt | 73 has been set to input. It is currently unknown what the behaviour is
|
| D | Overview.txt | 195 The SDIO behaviour of this driver has not been fully tested. There is no
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | dscr.txt | 83 this same behaviour as well.
|
| D | pmu-ebb.txt | 99 This behaviour occurs because the EBB event is pinned and exclusive. When the
|
| D | transactional_memory.txt | 7 This file aims to sum up how it is supported by Linux and what behaviour you
|
| /linux-4.4.14/drivers/macintosh/ |
| D | Kconfig | 98 behaviour of the old CONFIG_BLK_DEV_IDE_PMAC_BLINK, select this
204 better fan behaviour by default, and some manual control.
|
| /linux-4.4.14/drivers/char/ |
| D | Kconfig | 209 alter the behaviour of the hardware reset circuitry attached to the
293 /proc/driver/rtc and its behaviour is set by various ioctls on
319 /proc/driver/rtc and its behaviour is set by various ioctls on
339 behaviour is set by various ioctls on /dev/rtc. If you enable the
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | lis3lv02d | 44 but interrupt behaviour is not guaranteed to work reliably. In test mode, the
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | governors.txt | 197 behaviour in that it gracefully increases and decreases the CPU speed
199 CPU. This behaviour more suitable in a battery powered environment.
|
| /linux-4.4.14/arch/arm/kernel/ |
| D | entry-header.S | 143 @ ensure bit 0 is cleared in the PC, otherwise behaviour is
|
| /linux-4.4.14/arch/x86/math-emu/ |
| D | README | 38 in the detailed behaviour of the emulator and a real 80486.
40 wm-FPU-emu does not implement all of the behaviour of the 80486 FPU,
140 exception. For this case, the emulator cannot emulate the behaviour of
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 99 its behaviour. If free space on filesystem where the log lives
490 behaviour. If pages are properly placed then the scan delay increases,
556 Controls the kernel's behaviour when an oops or BUG is encountered.
579 The default Linux behaviour on an NMI of either memory or unknown is
595 0: only WARN(), default behaviour.
|
| D | fs.txt | 230 0 - (default) - traditional behaviour. Any process which has changed
|
| D | vm.txt | 509 This value adjusts the excess page trimming behaviour of power-of-2 aligned
|
| /linux-4.4.14/arch/cris/ |
| D | Kconfig | 328 This setting will also affect the behaviour of other activity LEDs
340 This setting will also affect the behaviour of other activity LEDs
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | usage-model.txt | 230 doesn't materially change the behaviour of either of these functions.
364 as platform devices too? For Linux DT support, the generic behaviour
394 board support code can always override the default behaviour.
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | fimc.txt | 81 undefined behaviour.
|
| D | soc-camera.txt | 106 VIDIOC_S_CROP and VIDIOC_S_FMT behaviour
|
| /linux-4.4.14/Documentation/vm/ |
| D | slub.txt | 295 of slabs' behaviour, because its output can be plotted using the
315 to compare slabs' behaviour "prior to" and "after" some code modification.
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | kconfig-language.txt | 133 "---help---" and "help" do not differ in behaviour, "---help---" is
139 which can modify the behaviour of the menu entry and its config
155 also means that the behaviour when mixing it with normal defaults is
|
| D | kconfig.txt | 91 to somehow debug the behaviour of the kconfig parser/frontends.
|
| D | makefiles.txt | 292 Note: Flags with the same behaviour were previously named:
1178 To enable this behaviour for custom commands kbuild requires
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig.debug | 137 default compiler behaviour, and should be used unless you have a
|
| D | Kconfig | 2716 behaviour before the details have been finalised, this option should
|
| /linux-4.4.14/arch/sh/mm/ |
| D | Kconfig | 121 allocation behaviour.
|
| /linux-4.4.14/drivers/input/ |
| D | Kconfig | 184 systems where such behaviour is desired without userspace
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.txt | 29 - write: Can simply go, all defined behaviour is taken care of by the framework,
|
| /linux-4.4.14/Documentation/input/ |
| D | ff.txt | 29 To stop this annoying behaviour, move you joystick to its limits. Anyway, you
|
| D | elantech.txt | 302 EF013 and EF019 have a special behaviour (due to a bug in the firmware?), and
|
| /linux-4.4.14/arch/arm/mm/ |
| D | Kconfig | 5 # optimiser behaviour.
1014 memory with differing types results in unpredictable behaviour,
1023 behaviour. Therefore, we offer this as an option.
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | cgroups.txt | 42 specialized behaviour.
92 specific subsystems such as cpusets to provide additional behaviour as
467 specify subsystems manually; the legacy behaviour of mounting all
|
| D | memory.txt | 21 The memory controller isolates the memory behaviour of a group of tasks
|
| /linux-4.4.14/Documentation/arm64/ |
| D | arm-acpi.txt | 67 responsibility for hardware behaviour cannot solely be the domain of the
72 hardware vendors to take responsibility for power management behaviour without
|
| /linux-4.4.14/drivers/thermal/ |
| D | Kconfig | 172 threshold behaviour for simulation purpose.
|
| /linux-4.4.14/drivers/usb/gadget/ |
| D | Kconfig | 121 for a bursty VFS behaviour. For instance there may be CPU wake up
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | ioctl-number.txt | 45 error rather than some unexpected behaviour.
|
| /linux-4.4.14/Documentation/kdump/ |
| D | kdump.txt | 480 to achieve the same behaviour.
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | Audiophile-Usb.txt | 152 the same behaviour as when the parameter is omitted (see paragraph "Default
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 43 timing and energy related properties, that underline the HW behaviour
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ncr53c8xx.txt | 286 QUEUE FULL status for a SCSI command. This behaviour is managed by the
1165 while spinning up, it rejects Tagged commands. This behaviour is
1166 conforms to 6.8.2 of SCSI-2 specifications. The current behaviour of
|
| D | tmscsim.txt | 381 it's consistent with the BIOS' behaviour. Old DC390 drivers ignored the
|
| D | sym53c8xx_2.txt | 257 QUEUE FULL status for a SCSI command. This behaviour is managed by the
|
| /linux-4.4.14/arch/s390/ |
| D | Kconfig | 416 The default behaviour is identical to appending numa=plain to
|
| /linux-4.4.14/drivers/staging/lustre/ |
| D | sysfs-fs-lustre | 272 Controls statfs(2) behaviour in the face of down servers.
|
| /linux-4.4.14/firmware/ |
| D | WHENCE | 266 Debug loader claims the following behaviour:
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 710 out of it with an assembler program, but due to pipeline behaviour etc
|
| /linux-4.4.14/Documentation/laptops/ |
| D | laptop-mode.txt | 177 Note that the behaviour of dirty_background_ratio is quite different
|
| D | thinkpad-acpi.txt | 202 by the mask. Some models do not support the mask at all. The behaviour
299 differently (and that behaviour changes with firmware
|
| /linux-4.4.14/net/netfilter/ |
| D | Kconfig | 736 change their behaviour.
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 43 The default watchdog behaviour (which you get if you say N here) is
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 1103 instruction to behave as a DSB, ensuring the correct behaviour of
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | api.txt | 554 their traditional behaviour) will cause KVM_RUN to return with -EINTR.
|