Home
last modified time | relevance | path

Searched refs:consume (Results 1 – 72 of 72) sorted by relevance

/linux-4.4.14/sound/firewire/tascam/
Dtascam-transaction.c65 int i, len, consume; in fill_message() local
73 consume = snd_rawmidi_transmit_peek(substream, msg, 3); in fill_message()
74 if (consume == 0) in fill_message()
80 for (i = 0; i < consume; ++i) { in fill_message()
89 consume = i + 1; in fill_message()
92 } else if (consume == 3) { in fill_message()
99 len = consume; in fill_message()
121 if (consume < len - 1) in fill_message()
123 consume = len - 1; in fill_message()
130 if (consume < len) in fill_message()
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/nvmem/
Dqfprom.txt27 Are device nodes which consume nvmem data cells.
Drockchip-efuse.txt30 Are device nodes which consume nvmem data cells.
Dnvmem.txt63 Are device nodes which consume nvmem data cells/providers.
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dhi3620-clock.txt18 to specify the clock which they consume.
Dmarvell,pxa910.txt19 to specify the clock which they consume.
Dhix5hd2-clock.txt13 to specify the clock which they consume.
Dexynos5440-clock.txt16 to specify the clock which they consume.
Dmarvell,pxa168.txt19 to specify the clock which they consume.
Dmarvell,mmp2.txt19 to specify the clock which they consume.
Dmarvell,pxa1928.txt19 phandle and this identifier to specify the clock which they consume.
Dexynos5250-clock.txt17 to specify the clock which they consume.
Dmaxim,max77686.txt19 to specify the clock which they consume. Following indices are allowed:
Dmaxim,max77802.txt18 to specify the clock which they consume. Following indices are allowed:
Dexynos4415-clock.txt20 to specify the clock which they consume.
Damlogic,meson8b-clkc.txt18 to specify the clock which they consume. All available clocks are defined as
Dexynos5420-clock.txt18 to specify the clock which they consume.
Dhi6220-clock.txt49 to specify the clock which they consume.
Dexynos4-clock.txt19 to specify the clock which they consume.
Dexynos3250-clock.txt21 to specify the clock which they consume.
Dsamsung,s3c2412-clock.txt15 to specify the clock which they consume. Some of the clocks are available only
Dsamsung,s3c2410-clock.txt18 to specify the clock which they consume. Some of the clocks are available only
Drockchip,rk3288-cru.txt21 to specify the clock which they consume. All available clocks are defined as
Dsamsung,s3c2443-clock.txt18 to specify the clock which they consume. Some of the clocks are available only
Drockchip,rk3188-cru.txt22 to specify the clock which they consume. All available clocks are defined as
Drockchip,rk3368-cru.txt21 to specify the clock which they consume. All available clocks are defined as
Dsamsung,s3c64xx-clock.txt19 to specify the clock which they consume. Some of the clocks are available only
Dexynos7-clock.txt9 this identifier to specify the clock which they consume. All
Dclk-exynos-audss.txt36 clock which they consume. Some of the clocks are available only on a particular
Dexynos5260-clock.txt9 this identifier to specify the clock which they consume. All
Dexynos5433-clock.txt168 to specify the clock which they consume.
/linux-4.4.14/Documentation/scheduler/
Dsched-bwc.txt11 each given "period" (microseconds), a group is allowed to consume only up to
18 above at each period boundary. As threads consume this bandwidth it is
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dqcom,spmi-pmic.txt14 each. A function can consume one or more of these fixed-size register regions.
Ds2mps11.txt41 the clock which they consume.
/linux-4.4.14/Documentation/RCU/
Drcuref.txt7 those unusual cases where percpu-ref would consume too much memory,
/linux-4.4.14/Documentation/
Dio-mapping.txt5 as it would consume too much of the kernel address space.
Dlzo.txt73 They just have to "refill" this credit if they consume extra bytes. This is
Dworkqueue.txt124 not expected to hog a CPU and consume many cycles. That means
347 * Unless work items are expected to consume a huge amount of CPU
Dpinctrl.txt446 consume 2, 4 or 8 pins respectively, so either { A1, B1 } are taken or
/linux-4.4.14/Documentation/thermal/
Dpower_allocator.txt203 maximum power that an actor can consume.
211 Calculate a cooling device state that would make the device consume at
/linux-4.4.14/drivers/spi/
Dspi-tegra114.c379 unsigned consume = tspi->curr_dma_words * tspi->bytes_per_word; in tegra_spi_copy_client_txbuf_to_spi_txbuf() local
384 for (i = 0; consume && (i < tspi->bytes_per_word); in tegra_spi_copy_client_txbuf_to_spi_txbuf()
385 i++, consume--) in tegra_spi_copy_client_txbuf_to_spi_txbuf()
Dspi-tegra20-slink.c389 unsigned consume = tspi->curr_dma_words * tspi->bytes_per_word; in tegra_slink_copy_client_txbuf_to_spi_txbuf() local
393 for (i = 0; consume && (i < tspi->bytes_per_word); in tegra_slink_copy_client_txbuf_to_spi_txbuf()
394 i++, consume--) in tegra_slink_copy_client_txbuf_to_spi_txbuf()
/linux-4.4.14/Documentation/ia64/
Derr_inject.txt54 #On cpu4, inject and consume total 0x10 errors, interval 5 seconds
59 #On cpu15, inject and consume total 0x10 errors, interval 5 seconds
830 /* Create a shm segment which will be used to inject/consume errors on.*/
909 /* consume the error for "inject only"*/
/linux-4.4.14/Documentation/cpu-freq/
Dboost.txt43 will consume more power than without the boosting, which may be
/linux-4.4.14/Documentation/networking/caif/
DLinux-CAIF.txt68 - Clients must implement CAIF layer to consume/produce
/linux-4.4.14/Documentation/device-mapper/
Dswitch.txt45 consume far too much memory.
Dstatistics.txt209 space must also be escaped, otherwise the shell will consume them):
/linux-4.4.14/sound/soc/blackfin/
DKconfig152 this mode will consume much more memory for DMA.
/linux-4.4.14/Documentation/vm/
Dhwpoison.txt16 * When the current CPU tries to consume corruption the currently
/linux-4.4.14/Documentation/filesystems/
Dlogfs.txt145 not consume any extra space, so the compression gains are lost space
Dext2.txt112 Because this can consume a considerable amount of space for large
Drelay.txt324 there is no consumer or if the consumer can't consume sub-buffers fast
/linux-4.4.14/net/sctp/
Dsm_statefuns.c2979 goto consume; in sctp_sf_eat_data_6_2()
3046 consume: in sctp_sf_eat_data_6_2()
3096 goto consume; in sctp_sf_eat_data_fast_4_4()
3122 consume: in sctp_sf_eat_data_fast_4_4()
/linux-4.4.14/Documentation/driver-model/
Dporting.txt387 consume. To do this, a bus must implement the 'hotplug' method in
/linux-4.4.14/Documentation/locking/
Dlockdep-design.txt249 spinlock_t will consume 8192 lock classes -unless- each spinlock
/linux-4.4.14/Documentation/nvdimm/
Dnvdimm.txt428 nd_blk device driver to consume.
745 finding and idle BTT and assigning it to consume a PMEM or BLK namespace.
/linux-4.4.14/Documentation/DocBook/
Dnetworking.xml.db103 API-consume-skb
/linux-4.4.14/kernel/
Dsignal.c332 bool consume = task->jobctl & JOBCTL_STOP_CONSUME; in task_participate_group_stop() local
338 if (!consume) in task_participate_group_stop()
/linux-4.4.14/Documentation/powerpc/
Dpci_iov_resource_on_powernv.txt300 space will consume (numVFs * n) segments. That means there aren't as many
/linux-4.4.14/net/mac80211/
Drx.c3418 struct sk_buff *skb, bool consume) in ieee80211_prepare_and_rx_handle() argument
3428 if (!consume) { in ieee80211_prepare_and_rx_handle()
/linux-4.4.14/mm/
DKconfig98 # consume vast quantities of .bss, so be careful.
/linux-4.4.14/Documentation/trace/
Dring-buffer-design.txt82 cannot preempt/interrupt a writer, but it may read/consume from the
Dftrace.txt442 read, but it will only display (and consume) the data specific
/linux-4.4.14/Documentation/sysctl/
Dvm.txt379 programs, particularly malloc debuggers, may consume lots of them,
Dkernel.txt786 process can consume, via setrlimit(2). Unfortunately, shared memory
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic7xxx.seq65 * automatically consume the entries.
Daic79xx.seq169 * Since this status did not consume a FIFO, we have to
/linux-4.4.14/Documentation/networking/
Dip-sysctl.txt434 may consume significant resources. Cf. tcp_max_orphans.
/linux-4.4.14/Documentation/sound/oss/
DREADME.OSS735 more cards than you really need since they just consume memory. Also
/linux-4.4.14/drivers/video/fbdev/
DKconfig2232 buffer device, while it does consume precious memory. The main use
/linux-4.4.14/arch/x86/
DKconfig505 consume less power than most of the x86 derivatives.
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt966 If you are short on IPs and don't want to consume two per UML, then