/linux-4.4.14/arch/powerpc/kernel/ |
D | vio.c | 99 size_t desired; member 250 if (excess_freed && (vio_cmo.desired > vio_cmo.reserve.size)) { in vio_cmo_dealloc() 251 tmp = min(excess_freed, (vio_cmo.desired - vio_cmo.reserve.size)); in vio_cmo_dealloc() 405 cmo->desired = cmo->min; in vio_cmo_balance() 416 cmo->desired += (viodev->cmo.desired - VIO_CMO_MIN_ENT); in vio_cmo_balance() 431 if (viodev->cmo.desired <= level) { in vio_cmo_balance() 442 chunk = min(chunk, (viodev->cmo.desired - in vio_cmo_balance() 640 void vio_cmo_set_dev_desired(struct vio_dev *viodev, size_t desired) in vio_cmo_set_dev_desired() argument 650 if (desired < VIO_CMO_MIN_ENT) in vio_cmo_set_dev_desired() 651 desired = VIO_CMO_MIN_ENT; in vio_cmo_set_dev_desired() [all …]
|
/linux-4.4.14/arch/x86/platform/olpc/ |
D | olpc.c | 70 static int __wait_on_ibf(unsigned int line, unsigned int port, int desired) in __wait_on_ibf() argument 75 for (timeo = ec_timeout; state != desired && timeo; timeo--) { in __wait_on_ibf() 80 if ((state == desired) && (ec_timeout > EC_BASE_TIMEOUT) && in __wait_on_ibf() 86 return !(state == desired); in __wait_on_ibf() 90 static int __wait_on_obf(unsigned int line, unsigned int port, int desired) in __wait_on_obf() argument 95 for (timeo = ec_timeout; state != desired && timeo; timeo--) { in __wait_on_obf() 100 if ((state == desired) && (ec_timeout > EC_BASE_TIMEOUT) && in __wait_on_obf() 106 return !(state == desired); in __wait_on_obf()
|
/linux-4.4.14/Documentation/isdn/ |
D | README.hfc-pci | 24 at the hisax module load command line. Supply the load command with the desired 25 IO-address of the desired card. 33 Then the desired card will be the initialised in the desired order.
|
D | README.hysdn | 150 desired output options. As mentioned above the cards log dat is always 159 desired output. The following bits are already assigned:
|
D | INTERFACE | 214 contain the desired command, the field driver is always set to the 320 parm.num = ASCII-String, containing the desired EAZ's/MSN's 346 parm.num = ASCII-String, containing the desired Service-Indicators.
|
/linux-4.4.14/Documentation/thermal/ |
D | power_allocator.txt | 13 2. "desired temperature" trip point: it should be higher than the 64 sustained power that can be dissipated at the desired control 66 the desired maximum temperature. The actual sustained power can vary 104 above "desired temperature" trip point). Conversely, `k_pu` is the 106 (current temperature below "desired temperature" trip point). 131 desired temperature and the current one. When the current temperature 132 is the desired one, then the proportional component is zero and 142 T_set is the desired temperature 155 rises from the switch on temperature to the desired temperature.
|
D | sysfs-api.txt | 333 is when the current temperature is above the "desired 341 is when the current temperature is below the "desired 360 Temperature offset from the desired temperature trip point 364 accumulates error when temperature is above the desired
|
D | intel_powerclamp.txt | 122 intel_powerclamp driver attempts to enforce the desired idle time 131 maintain a desired target temperature, based on integral and
|
/linux-4.4.14/drivers/staging/iio/Documentation/ |
D | sysfs-bus-iio-dds | 10 can control the desired active tuning word by writing Y to the 18 obtain the desired value in Hz. If shared across all frequency 40 control the desired phase Y which is added to the phase 48 the desired value in rad. If shared across all phase registers
|
/linux-4.4.14/arch/powerpc/include/asm/ |
D | vio.h | 107 size_t desired; member 139 extern void vio_cmo_set_dev_desired(struct vio_dev *viodev, size_t desired);
|
/linux-4.4.14/Documentation/devicetree/bindings/clock/ |
D | csr,atlas7-car.txt | 9 The clock consumer should specify the desired clock by having the clock 13 The reset consumer should specify the desired reset by having the reset
|
D | pxa-clock.txt | 7 The clock consumer should specify the desired clock by having the clock
|
D | imx6sl-clock.txt | 8 The clock consumer should specify the desired clock by having the clock
|
D | fujitsu,mb86s70-crg11.txt | 8 The consumer specifies the desired clock pointing to its phandle.
|
D | efm32-clock.txt | 9 The clock consumer should specify the desired clock by having the clock ID in
|
D | clps711x-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | imx7d-clock.txt | 11 The clock consumer should specify the desired clock by having the clock
|
D | imx6ul-clock.txt | 11 The clock consumer should specify the desired clock by having the clock
|
D | lsi,axm5516-clks.txt | 9 The consumer specifies the desired clock by having the clock ID in its "clocks"
|
D | imx6sx-clock.txt | 11 The clock consumer should specify the desired clock by having the clock
|
D | imx1-clock.txt | 8 The clock consumer should specify the desired clock by having the clock
|
D | imx27-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | imx21-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | imx5-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | imx6q-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | imx23-clock.txt | 8 The clock consumer should specify the desired clock by having the clock
|
D | zx296702-clk.txt | 18 The clock consumer should specify the desired clock by having the clock
|
D | prima2-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | imx31-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | vf610-clock.txt | 21 The clock consumer should specify the desired clock by having the clock
|
D | imx28-clock.txt | 8 The clock consumer should specify the desired clock by having the clock
|
D | imx35-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | imx25-clock.txt | 9 The clock consumer should specify the desired clock by having the clock
|
D | mvebu-core-clock.txt | 5 specify the desired clock by having the clock ID in its "clocks" phandle cell.
|
D | mvebu-gated-clock.txt | 5 should specify the desired clock by having the clock ID in its
|
D | sunxi.txt | 99 Clock consumers should specify the desired clocks they use with a
|
/linux-4.4.14/Documentation/laptops/ |
D | toshiba_haps.txt | 28 file to set the desired protection level or sensor sensibility. 37 PTLV - Sets the desired protection level. 71 level, as well as set the desired protection level, the
|
/linux-4.4.14/Documentation/hwmon/ |
D | max31790 | 19 PWM outputs. The desired fan speeds (or PWM duty cycles) are written 35 fan[1-6]_target RW desired fan speed in RPM
|
D | smsc47b397 | 98 The desired configuration registers are accessed in two steps: 101 desired logical device to the DATA PORT. 103 b. Write the address of the desired configuration register within the
|
D | max6650 | 35 fan1_target rw desired fan speed in RPM (closed loop mode only)
|
D | ina2xx | 64 The actual programmed interval may vary from the desired value.
|
D | lm73 | 27 From userspace, the desired resolution can be specified as a function of
|
D | w83792d | 128 Works as expected. You just need to specify desired PWM/DC value (fan speed) 178 thermal_cruise[1-3] - Selects the desired temperature for cruise (degC)
|
D | nct6775 | 142 speed increases (if temperature is higher that desired) or decreases (if 143 temperature is lower than desired), using the following limits and time
|
D | g762 | 24 fan1_target: set desired fan speed. This only makes sense in closed-loop
|
D | w83627ehf | 138 fan speed increases (temp is higher) or decreases if lower than desired.
|
D | sysfs-interface | 64 the desired value must be written, note that strings which are not a number 98 This attribute can be used to change it to the desired value.
|
/linux-4.4.14/fs/f2fs/ |
D | segment.h | 718 long nr_to_write, desired; in nr_pages_to_write() local 726 desired = 4096; in nr_pages_to_write() 728 desired = 3 * max_hw_blocks(sbi); in nr_pages_to_write() 730 desired = MAX_BIO_BLOCKS(sbi); in nr_pages_to_write() 732 wbc->nr_to_write = desired; in nr_pages_to_write() 733 return desired - nr_to_write; in nr_pages_to_write()
|
/linux-4.4.14/include/linux/ |
D | mdio-mux.h | 15 int (*switch_fn) (int cur, int desired, void *data),
|
/linux-4.4.14/Documentation/networking/ |
D | ipv6.txt | 19 IPv6 addresses or operations are desired. 59 This might be used when no IPv6 addresses are desired.
|
D | e100.txt | 63 ethtool -G eth? rx n, where n is the number of desired rx descriptors. 72 ethtool -G eth? tx n, where n is the number of desired tx descriptors.
|
D | scaling.txt | 107 on the desired CPU’s backlog queue and waking up the CPU for processing. 247 rps_sock_flow_table is a global flow table that contains the *desired* CPU 277 are compared. If the desired CPU for the flow (found in the 280 the current CPU is updated to match the desired CPU if one of the 336 ndo_rx_flow_steer driver function to communicate the desired hardware
|
D | nfc.txt | 87 The user must call START_POLL to poll for NFC targets, passing the desired NFC
|
D | ipvs-sysctl.txt | 151 quiescent by setting its weight to 0 and it is desired that
|
D | vrf.txt | 15 precedence over the VRF device rules directing specific traffic as desired.
|
D | l2tp.txt | 150 request. Set attributes according to desired tunnel parameters,
|
D | phy.txt | 228 If the desired PHY doesn't have any errata, quirks, or special
|
/linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
D | brcm,bcm2835-i2c.txt | 10 - clock-frequency : desired I2C bus clock frequency in Hz.
|
D | i2c-sirf.txt | 10 - clock-frequency : Constains desired I2C/HS-I2C bus clock frequency in Hz.
|
D | i2c-meson.txt | 12 - clock-frequency: the desired I2C bus clock frequency in Hz; in
|
D | i2c-vt8500.txt | 12 - clock-frequency : desired I2C bus clock frequency in Hz.
|
D | i2c-uniphier-f.txt | 12 - clock-frequency: desired I2C bus frequency in Hz. The maximum supported
|
D | i2c-digicolor.txt | 12 - clock-frequency: the desired I2C bus clock frequency in Hz; in
|
D | i2c-uniphier.txt | 12 - clock-frequency: desired I2C bus frequency in Hz. The maximum supported
|
D | i2c-lpc2k.txt | 12 - clock-frequency: the desired I2C bus clock frequency in Hz; in
|
D | i2c-rcar.txt | 19 - clock-frequency: desired I2C bus clock frequency in Hz. The absence of this
|
D | i2c-pnx.txt | 15 - clock-frequency: desired I2C bus clock frequency in Hz, Default: 100000 Hz
|
D | i2c-jz4780.txt | 8 - clock-frequency: desired I2C bus clock frequency in Hz.
|
D | i2c-davinci.txt | 12 - clock-frequency : desired I2C bus clock frequency in Hz.
|
D | qcom,i2c-qup.txt | 21 - clock-frequency: Should specify the desired i2c bus clock frequency in Hz,
|
D | i2c-designware.txt | 11 - clock-frequency : desired I2C bus clock frequency in Hz.
|
D | i2c-imx.txt | 13 - clock-frequency : Constains desired I2C/HS-I2C bus clock frequency in Hz.
|
D | i2c-mpc.txt | 22 - clock-frequency : desired I2C bus clock frequency in Hz.
|
/linux-4.4.14/fs/hostfs/ |
D | hostfs_kern.c | 780 static int hostfs_permission(struct inode *ino, int desired) in hostfs_permission() argument 785 if (desired & MAY_NOT_BLOCK) in hostfs_permission() 788 if (desired & MAY_READ) r = 1; in hostfs_permission() 789 if (desired & MAY_WRITE) w = 1; in hostfs_permission() 790 if (desired & MAY_EXEC) x = 1; in hostfs_permission() 802 err = generic_permission(ino, desired); in hostfs_permission()
|
/linux-4.4.14/Documentation/timers/ |
D | timers-howto.txt | 23 the desired delay: 76 is not the desired behavior.
|
D | timekeeping.txt | 88 desired time specification value and calculate the values to poke into 174 a hard-coded loop for providing the desired delay.
|
D | NO_HZ.txt | 227 pin the "rcuo" kthreads to specific CPUs if desired. Otherwise, the
|
/linux-4.4.14/Documentation/devicetree/bindings/clock/ti/ |
D | apll.txt | 8 loop logic for multiplying the input clock to a desired output
|
D | dra7-atl.txt | 6 ATL can maintain a clock averages to some desired frequency based on the bws/aws
|
D | dpll.txt | 8 loop logic for multiplying the input clock to a desired output
|
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
D | pinctrl-sirf.txt | 17 Each of these subnodes represents some desired configuration for a group of pins.
|
D | pinctrl-atlas7.txt | 64 Each of these subnodes represents some desired configuration for a group of pins.
|
D | meson,pinctrl.txt | 27 Child nodes without the "gpio-controller" represent some desired
|
D | lantiq,pinctrl-falcon.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a
|
D | qcom,apq8064-pinctrl.txt | 22 subnodes. Each of these subnodes represents some desired configuration for a
|
D | qcom,msm8660-pinctrl.txt | 22 subnodes. Each of these subnodes represents some desired configuration for a
|
D | qcom,ipq8064-pinctrl.txt | 22 subnodes. Each of these subnodes represents some desired configuration for a
|
D | pinctrl-single.txt | 101 device pinctrl register, and 0x118 contains the desired value of the 111 device pinctrl register, 0x18 is the desired value, and 0xff is the sub mask to
|
D | pinctrl-palmas.txt | 17 subnodes. Each of these subnodes represents some desired configuration for a
|
D | xlnx,zynq-pinctrl.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a
|
D | cnxt,cx92755-pinctrl.txt | 46 A pin group node specifies the desired pin mux for an arbitrary number of
|
D | qcom,msm8974-pinctrl.txt | 22 subnodes. Each of these subnodes represents some desired configuration for a
|
D | lantiq,pinctrl-xway.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a
|
D | ste,nomadik.txt | 15 subnodes. Each of these subnodes represents some desired configuration for a
|
D | img,tz1090-pdc-pinctrl.txt | 13 of subnodes. Each of these subnodes represents some desired configuration for a
|
D | qcom,msm8960-pinctrl.txt | 51 subnodes. Each of these subnodes represents some desired configuration for a
|
D | qcom,apq8084-pinctrl.txt | 51 subnodes. Each of these subnodes represents some desired configuration for a
|
D | qcom,msm8916-pinctrl.txt | 51 subnodes. Each of these subnodes represents some desired configuration for a
|
D | qcom,pmic-mpp.txt | 51 subnodes. Each of these subnodes represents some desired configuration for a
|
D | qcom,pmic-gpio.txt | 50 subnodes. Each of these subnodes represents some desired configuration for a
|
D | fsl,mxs-pinctrl.txt | 17 subnodes. Each of these subnodes represents some desired configuration for
|
D | renesas,pfc-pinctrl.txt | 42 Each pin configuration node represents a desired configuration for a pin, a
|
D | nvidia,tegra20-pinmux.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a
|
D | nvidia,tegra210-pinmux.txt | 14 subnodes. Each of these subnodes represents some desired configuration for a
|
D | img,tz1090-pinctrl.txt | 13 subnodes. Each of these subnodes represents some desired configuration for a
|
D | brcm,bcm11351-pinctrl.txt | 37 A pin group node specifies the desired pin mux and/or pin configuration for an
|
D | samsung-pinctrl.txt | 70 no specific function selection is desired for the pins listed in the child
|
/linux-4.4.14/scripts/coccinelle/locks/ |
D | call_kern.cocci | 3 //# correct one. It may be desired to unlock the lock, or to not call the
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-driver-hid-logitech-lg4ff | 21 If a wheel cannot be switched into the desired mode, -EINVAL
|
D | sysfs-block | 132 desired. 144 throughput is desired. If no optimal I/O size is
|
D | sysfs-devices-power | 17 it to do that as desired.
|
/linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
D | spear_spics.txt | 7 desired by some of the device protocols above spi which expect (multiple)
|
/linux-4.4.14/Documentation/devicetree/bindings/net/ |
D | fsl-tsec-phy.txt | 107 tclk_period = desired clock period nanoseconds 113 FiperFreq1 = desired frequency in Hz
|
/linux-4.4.14/Documentation/filesystems/ |
D | sysfs-pci.txt | 103 do legacy port I/O. The application should open the file, seek to the desired 106 desired, e.g. 0xa0000 for the VGA frame buffer. The application can then
|
D | seq_file.txt | 205 root is desired, it can be used with seq_path_root(). If it turns out that
|
/linux-4.4.14/Documentation/device-mapper/ |
D | zero.txt | 20 desired size of the sparse device. For this example, we'll assume a 10TB
|
D | dm-io.txt | 8 The user must set up an io_region structure to describe the desired location
|
D | cache.txt | 96 contents can be discarded prior to transitioning to the desired
|
/linux-4.4.14/Documentation/devicetree/bindings/dma/ |
D | shdma.txt | 26 be replaced with the desired SoC model, e.g.
|
/linux-4.4.14/drivers/net/phy/ |
D | mdio-mux.c | 97 int (*switch_fn)(int cur, int desired, void *data), in mdio_mux_init() argument
|
/linux-4.4.14/arch/m68k/ifpsp060/ |
D | ilsp.doc | 70 below in "68060ILSP Entry Points" that corresponds to the desired 134 to record that such an event occurred if desired.
|
D | iskeleton.S | 61 | can do any clean-up desired. The stack frame is the
|
D | fplsp.doc | 71 below in "68060FPLSP entry points" that corresponds to the desired
|
D | TEST.DOC | 149 is desired:
|
/linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
D | palmas-pmic.txt | 35 the rail from desired external control. If there is no argument then
|
/linux-4.4.14/arch/frv/kernel/ |
D | sleep.S | 127 # On entry: gr7 holds desired hsr0 sleep value 128 # gr8 holds desired psr sleep value
|
/linux-4.4.14/drivers/staging/most/Documentation/ |
D | driver_usage.txt | 32 modules can arbitrarily be combined to meet the needs of the desired 132 When transmitting isochronous AVP data the desired packet size needs to be
|
/linux-4.4.14/Documentation/devicetree/bindings/iio/frequency/ |
D | adf4350.txt | 17 the desired frequency on probe.
|
/linux-4.4.14/drivers/mmc/host/ |
D | mmci.c | 314 static void mmci_set_clkreg(struct mmci_host *host, unsigned int desired) in mmci_set_clkreg() argument 322 if (desired) { in mmci_set_clkreg() 325 } else if (desired >= host->mclk) { in mmci_set_clkreg() 337 clk = DIV_ROUND_UP(host->mclk, desired) - 2; in mmci_set_clkreg() 346 clk = host->mclk / (2 * desired) - 1; in mmci_set_clkreg()
|
/linux-4.4.14/Documentation/dmaengine/ |
D | client.txt | 24 controller only and even in some cases a specific channel is desired. 43 return 'true' when the desired DMA channel is found.
|
/linux-4.4.14/Documentation/leds/ |
D | ledtrig-transient.txt | 127 echo 1 > state - stores desired transient state LED_FULL to be 129 echo 0 > state - stores desired transient state LED_OFF to be
|
/linux-4.4.14/Documentation/ioctl/ |
D | cdrom.txt | 449 cdrom_multisession structure containing desired 863 type specifies the information desired, one of 867 physical.layer_num desired layer, indexed from 0 868 copyright.layer_num desired layer, indexed from 0
|
/linux-4.4.14/Documentation/fmc/ |
D | fmc-chardev.txt | 16 desired address and read or write a register.
|
D | FMC-and-SDB.txt | 45 match the specific mezzanine and the desired application. Thus, you may
|
/linux-4.4.14/Documentation/fb/ |
D | deferred_io.txt | 29 For some types of nonvolatile high latency displays, the desired image is
|
D | pxafb.txt | 111 c. modify 'var' with desired parameters:
|
D | api.txt | 243 to the desired frame buffer depth. Values up to 8 will usually map to 294 To select a format, applications set the grayscale field to the desired FOURCC.
|
D | vesafb.txt | 65 lilo.conf file and rerun LILO. Then you can type in the desired
|
D | sisfb.txt | 74 The desired display mode can be specified using the keyword "mode" with
|
D | intel810.txt | 88 select desired pixel depth
|
/linux-4.4.14/Documentation/cpu-freq/ |
D | pcc-cpufreq.txt | 109 desired frequency for a logical processor. The output buffer is currently 111 OSPM if the desired frequency was achieved or not.
|
/linux-4.4.14/Documentation/ABI/stable/ |
D | firewire-cdev | 82 be used as follows: addr = NULL, length = the desired buffer
|
/linux-4.4.14/drivers/ssb/ |
D | Kconfig | 99 This might only be desired for production kernels on
|
/linux-4.4.14/Documentation/usb/ |
D | usbmon.txt | 48 2. Find which bus connects to the desired device 79 4. Perform the desired operation on the USB bus 100 If it is desired to recognize one from the other in a program, look at the
|
D | CREDITS | 5 difficult to maintain, add yourself with a patch if desired.
|
D | URB.txt | 109 the desired transfer length, the completion handler, and its context.
|
D | gadget_serial.txt | 126 desired.
|
/linux-4.4.14/Documentation/infiniband/ |
D | ipoib.txt | 14 different P_Key, write the desired P_Key into the main interface's
|
/linux-4.4.14/arch/m68k/fpsp040/ |
D | binstr.S | 7 | Input: 64-bit binary integer in d2:d3, desired length (LEN) in
|
D | bindec.S | 68 | The mantissa is scaled to the desired number of
|
/linux-4.4.14/Documentation/ |
D | intel_txt.txt | 150 platform in the desired sleep state. 155 into the desired sleep state.
|
D | remoteproc.txt | 163 handlers. If rpmsg/virtio functionality is also desired, then the ->kick handler 300 rpmsg virtio devices this way, if desired).
|
D | vfio.txt | 85 group associated with the desired device. This can be done using 100 previously opened container file. If desired and if the IOMMU driver 158 unprivileged operation is desired (note that /dev/vfio/vfio provides
|
D | xillybus.txt | 68 It's however common that the desired data communication doesn't fit any well- 177 the attached memory is done by seeking to the desired address, and calling
|
D | Changes | 113 well as the desired DocBook stylesheets.
|
D | pinctrl.txt | 780 gpiolib driver and the affected GPIO range, pin offset and desired direction 825 still applying desired pin config properties. GPIO functionality is thus 963 This will give the desired effect without any bogus interaction with the 1311 nominally always get your pinctrl handle and select the desired pinctrl
|
D | rpmsg.txt | 45 desired to limit userland to specific rpmsg channels (see definition below)
|
D | initrd.txt | 85 disk with the desired initrd content, cd to that directory, and run (as an
|
/linux-4.4.14/drivers/clk/ |
D | Kconfig | 117 divider to best approximate the desired output.
|
/linux-4.4.14/Documentation/RCU/ |
D | arrayRCU.txt | 112 to the desired IPC object is placed in "out", with NULL indicating
|
/linux-4.4.14/Documentation/frv/ |
D | gdbstub.txt | 122 desired location which the GDB stub then traps the exception for.
|
D | features.txt | 94 move the SDRAM to desired address, (2) moves the kernel image down to the
|
/linux-4.4.14/drivers/media/i2c/ |
D | ov2659.c | 911 unsigned int desired = pdata->link_frequency; in ov2659_pll_calc_params() local 926 delta = actual - desired; in ov2659_pll_calc_params()
|
/linux-4.4.14/Documentation/locking/ |
D | locktorture.txt | 8 kernel to be tested, if desired. The tests periodically output status
|
/linux-4.4.14/Documentation/video4linux/cx2341x/ |
D | fw-decoder-api.txt | 54 desired speed.
|
/linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
D | as3722.txt | 53 nodes contains different subnodes to represents some desired
|
/linux-4.4.14/kernel/time/ |
D | Kconfig | 109 desired range of dynticks CPUs.
|
/linux-4.4.14/Documentation/video4linux/ |
D | vivid.txt | 152 vid_cap_nr: give the desired videoX start number for each video capture device. 163 vid_out_nr: give the desired videoX start number for each video output device. 166 vbi_cap_nr: give the desired vbiX start number for each vbi capture device. 169 vbi_out_nr: give the desired vbiX start number for each vbi output device. 172 radio_rx_nr: give the desired radioX start number for each radio receiver device. 175 radio_tx_nr: give the desired radioX start number for each radio transmitter 178 sdr_cap_nr: give the desired swradioX start number for each SDR capture device.
|
/linux-4.4.14/Documentation/x86/ |
D | pat.txt | 121 combine areas of IO memory desired to remain uncacheable with areas where
|
/linux-4.4.14/drivers/input/ |
D | Kconfig | 184 systems where such behaviour is desired without userspace
|
/linux-4.4.14/Documentation/power/regulator/ |
D | consumer.txt | 192 the supply voltage over I2C to achieve a desired output clock rate
|
/linux-4.4.14/arch/arm/nwfpe/ |
D | softfloat-specialize | 43 defined here if desired. It is currently not possible for such a trap to
|
/linux-4.4.14/Documentation/security/ |
D | keys-request-key.txt | 84 (3) request_key() sees that A doesn't have the desired key yet, so it creates
|
D | credentials.txt | 109 is granted or denied permission to act in the desired manner on the 209 be searched for the desired key. Each process may subscribe to a number
|
D | Smack.txt | 236 label. The values are set by writing the desired labels, separated 266 The values are set by writing the desired labels, separated 423 different labels is desired. One example is the familiar spy model of
|
/linux-4.4.14/Documentation/sound/oss/ |
D | PAS16 | 156 functionality. If Soundblaster functionality is not desired, the
|
D | Introduction | 400 the desired device - for example a soundblaster does not directly provide
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | ppc-pv.txt | 71 desired location. The first parameter indicates the effective address when the
|
/linux-4.4.14/Documentation/blockdev/ |
D | zram.txt | 75 must be initially set to desired concurrency level before ZRAM device
|
/linux-4.4.14/arch/cris/arch-v10/ |
D | README.mm | 238 used just like alloc_area_pmd to check which page table entry is desired,
|
/linux-4.4.14/Documentation/misc-devices/mei/ |
D | mei.txt | 55 MEI_CONNECT_CLIENT_IOCTL, which passes the desired UUID.
|
/linux-4.4.14/tools/perf/Documentation/ |
D | perf-script.txt | 54 desired, they can be specified using separate 'perf script record'
|
/linux-4.4.14/Documentation/trace/ |
D | tracepoint-analysis.txt | 107 Similarly, one could execute a shell and exit it as desired to get a report
|
/linux-4.4.14/drivers/media/usb/pwc/ |
D | philips.txt | 54 Specifies the desired framerate. Is an integer in the range of 4-30.
|
/linux-4.4.14/Documentation/powerpc/ |
D | firmware-assisted-dump.txt | 79 network, nas, san, iscsi, etc. as desired.
|
D | cxlflash.txt | 216 the virtual LUN to a desired size. To avoid having to perform this
|
/linux-4.4.14/Documentation/sound/alsa/soc/ |
D | DPCM.txt | 232 DAI0 so that the DAI is running at desired configuration regardless of the FE
|
/linux-4.4.14/arch/tile/ |
D | Kconfig | 304 Select the desired split between kernel and user memory.
|
/linux-4.4.14/arch/unicore32/kernel/ |
D | entry.S | 278 @ set desired INTR state, then call main handler
|
/linux-4.4.14/Documentation/cgroups/ |
D | cgroups.txt | 93 desired. 264 desired collection of cgroups then that group is reused, otherwise a new
|
/linux-4.4.14/Documentation/gpio/ |
D | consumer.txt | 306 matches the desired group of GPIOs, those GPIOs can be set by simply using
|
/linux-4.4.14/Documentation/sysctl/ |
D | kernel.txt | 418 These three toggles allows to specify desired id for next allocated IPC 425 1) kernel doesn't guarantee, that new object will have desired id. So,
|
/linux-4.4.14/Documentation/input/ |
D | multi-touch-protocol.txt | 162 A set of ABS_MT events with the desired properties is defined. The events
|
/linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
D | thermal.txt | 172 Type: unsigned thermal zone can dissipate at the desired
|
/linux-4.4.14/Documentation/cdrom/ |
D | cdrom-standard.tex | 401 the desired direction of movement: 407 error. Note that if the tray is already in the desired position, no 413 drive allows this. The value of $lock$ controls the desired locking
|
/linux-4.4.14/Documentation/kdump/ |
D | kdump.txt | 230 as a dump-capture kernel if desired.
|
/linux-4.4.14/Documentation/vm/ |
D | hugetlbpage.txt | 227 without first moving to a cpuset that contains all of the desired nodes.
|
/linux-4.4.14/firmware/keyspan_pda/ |
D | keyspan_pda.S | 437 ;; 05 is set desired interrupt bitmap. TODO
|
/linux-4.4.14/Documentation/serial/ |
D | moxa-smartio | 397 to the device name you desired. "msmknod" creates the device names
|
/linux-4.4.14/Documentation/s390/ |
D | s390dbf.txt | 436 Debug areas can be flushed with piping the number of the desired
|