Home
last modified time | relevance | path

Searched full:fast (Results 1 – 25 of 282) sorted by relevance

12345678910>>...12

/Documentation/devicetree/bindings/power/supply/
Dqcom,pm8941-charger.yaml24 - description: charge fast mode
35 - const: chg-fast
43 qcom,fast-charge-current-limit:
49 qcom,fast-charge-low-threshold-voltage:
54 Battery voltage limit in uV above which fast charging may operate; Defaults to 3.2V
57 qcom,fast-charge-high-threshold-voltage:
62 Battery voltage limit in uV below which fast charging may operate; Defaults to 4.2V
63 The fast charger will attempt to charge the battery to this voltage.
66 qcom,fast-charge-safe-voltage:
72 setting this will harmlessly fail. The property 'fast-charge-high-watermark' will
[all …]
Dqcom,pm8916-lbc.yaml40 - description: Fast charging
63 qcom,fast-charge-safe-voltage:
71 qcom,fast-charge-safe-current:
86 - qcom,fast-charge-safe-voltage
87 - qcom,fast-charge-safe-current
125 qcom,fast-charge-safe-current = <900000>;
126 qcom,fast-charge-safe-voltage = <4300000>;
Dmaxim,max14577.yaml39 maxim,fast-charge-uamp:
41 Current in uA for Fast Charge
57 - maxim,fast-charge-uamp
71 maxim,fast-charge-uamp:
80 maxim,fast-charge-uamp:
Dmaxim,max77693.yaml25 Battery constant voltage in uV. The charger will operate in fast
27 Then the charger will switch to fast charge constant voltage mode.
Drichtek,rt5033-charger.yaml31 Current of fast-charge mode. The fast-charge current levels are 700 mA
Drohm,bd99954.yaml35 # c) fast-charge with:
67 # | --trickle-- | -pre- | ---------fast----------- |
81 # Current used at fast charge constant current phase (5 in above chart)
86 # The constant voltage used in fast charging phase (4 in above chart)
/Documentation/devicetree/bindings/cpufreq/
Dnvidia,tegra124-cpufreq.txt11 - cpu_g: Clock mux for the fast CPU cluster.
12 - pll_x: Fast PLL clocksource.
13 - pll_p: Auxiliary PLL used during fast PLL rate changes.
14 - dfll: Fast DFLL clocksource that also automatically scales CPU voltage.
/Documentation/filesystems/
Djournalling.rst135 Fast commits
139 fast commits. In order to use fast commits, you will need to set following
143 fast commit.
145 `journal->j_fc_replay_cb`: Replay function called for replay of fast commit
148 File system is free to perform fast commits as and when it wants as long as it
150 :c:func:`jbd2_fc_begin_commit()`. Once a fast commit is done, the client
153 commit immediately after stopping the fast commit it can do so by calling
154 :c:func:`jbd2_fc_end_commit_fallback()`. This is useful if fast commit operation
158 JBD2 helper functions to manage fast commit buffers. File system can use
160 and wait on IO completion of fast commit buffers.
[all …]
/Documentation/devicetree/bindings/mtd/
Dspear_smi.txt12 - st,smi-fast-mode : Flash supports read in fast mode
26 st,smi-fast-mode;
/Documentation/devicetree/bindings/nios2/
Dnios2.txt30 - altr,fast-tlb-miss-addr: Specifies CPU fast TLB miss exception address
35 - altr,implementation: Nios II core implementation, this should be "fast";
50 altr,implementation = "fast";
58 altr,fast-tlb-miss-addr = <0xc7fff400>;
/Documentation/devicetree/bindings/timer/
Dimg,pistachio-gptimer.txt11 "fast", fast counter clock
26 clock-names = "fast", "slow", "sys";
/Documentation/filesystems/ext4/
Djournal.rst31 In case of ``data=ordered`` mode, Ext4 also supports fast commits which
33 mode works by logging metadata blocks to the journal. In fast commit
35 affected metadata in fast commit space that is shared with JBD2.
36 Once the fast commit area fills in or if fast commit is not possible
38 A full commit invalidates all the fast commits that happened before
39 it and thus it makes the fast commit area empty for further fast
261 - Number of fast commit blocks in the journal.
323 - Journal has fast commit blocks. (JBD2_FEATURE_INCOMPAT_FAST_COMMIT)
634 Fast commits
637 Fast commit area is organized as a log of tag length values. Each TLV has
[all …]
/Documentation/devicetree/bindings/i2c/
Di2c-pxa.yaml47 mrvl,i2c-fast-mode:
49 description: Enable fast mode of i2c controller.
69 mrvl,i2c-fast-mode;
/Documentation/devicetree/bindings/soc/tegra/
Dnvidia,nvec.yaml27 - description: fast clock
33 - const: fast-clk
81 clock-names = "div-clk", "fast-clk";
/Documentation/networking/
Dtcp-thin.rst16 retransmissions effectively through fast retransmit instead of
30 1) If the stream is thin, fast retransmit on the first dupACK.
36 fast retransmissions can not be triggered, and the stream is prone
Dsnmp_counter.rst330 retransmissions into SYN, fast-retransmits, timeout retransmits, etc.
337 TCPFastOpenActiveFail: Fast Open attempts (SYN/data) failed because
365 TCP Fast Open
413 TCP Fast Path
416 packet, one is fast path, another is slow path. The comment in kernel
419 It is split into a fast path and a slow path. The fast path is
430 - Data is sent in both directions. The fast path only supports pure senders
435 Kernel will try to use fast path unless any of the above conditions
441 try to enable fast path immediately when the connection comes into the
443 will disable the fast path at first, and try to enable it after kernel
[all …]
/Documentation/ABI/testing/
Dsysfs-kernel-mm-numa17 systems to migrate pages from fast tiers to slow tiers
18 when the fast tier is under pressure. This migration
/Documentation/virt/kvm/
Dlocking.rst65 Fast page fault:
67 Fast page fault is the fast path which fixes the guest page fault out of
68 the mmu-lock on x86. Currently, the page fault can be fast in one of the
86 On fast page fault path, we will use cmpxchg to atomically set the spte W
107 | On fast page fault path: |
136 to gfn. For indirect sp, we disabled fast page fault for simplicity.
150 In the origin code, the spte can be fast updated (non-atomically) if the
154 But it is not true after fast page fault since the spte can be marked
175 | | on fast page fault path:: |
207 fast page fault path. In order to easily audit the path, we see if TLBs needing
[all …]
/Documentation/locking/
Drt-mutex.rst55 NULL 0 lock is free (fast acquire possible)
58 taskpointer 0 lock is held (fast release possible)
62 The fast atomic compare exchange based acquire and release is only
66 with ->wait_lock is held. To prevent any fast path cmpxchg to the lock,
/Documentation/devicetree/bindings/interrupt-controller/
Dapple,aic.yaml35 from A11, system registers may also be used for "fast" IPIs. Starting from
37 a "local" fast IPI register as opposed to using the "global" fast IPI
/Documentation/devicetree/bindings/mfd/
Dmaxim,max8925.yaml71 fast-charge:
72 description: set charging current in fast mode, configures bits 0-3 in CHG_CNTL1
140 fast-charge = <7>;
/Documentation/driver-api/gpio/
Dboard.rst197 mapped to the device determines if the array qualifies for fast bitmap
201 In order to qualify for fast bitmap processing, the array must meet the
208 Otherwise fast bitmap processing path is not used in order to avoid consecutive
212 If the array applies for fast bitmap processing path, pins which belong to
214 their hardware pin numbers, are excluded from the fast path, both input and
215 output. Moreover, open drain and open source pins are excluded from fast bitmap
/Documentation/scsi/
DBusLogic.rst118 Synchronous Negotiation: Fast
136 and 4 through 15, to Fast speed for target device 1, to Slow speed for
247 BT-946C PCI Fast SCSI-2
248 BT-956C PCI Wide Fast SCSI-2
249 BT-956CD PCI Wide Differential Fast SCSI-2
250 BT-445C VLB Fast SCSI-2
251 BT-747C EISA Fast SCSI-2
252 BT-757C EISA Wide Fast SCSI-2
253 BT-757CD EISA Wide Differential Fast SCSI-2
259 BT-445S VLB Fast SCSI-2
[all …]
/Documentation/arch/arm/pxa/
Dmfp.rst179 0b000 - fast 1mA
180 0b001 - fast 2mA
181 0b002 - fast 3mA
182 0b003 - fast 4mA
184 0b005 - fast 6mA
186 0b007 - fast 10mA
251 * drive strength = fast 3mA (MFP_DS03X)
/Documentation/devicetree/bindings/clock/
Dimx7ulp-scg-clock.yaml20 and and the Fast IRC clock (FIRCLK), clock sources and clock
55 - description: fast internal reference clock

12345678910>>...12