| /linux/Documentation/devicetree/bindings/power/supply/ |
| A D | qcom,pm8941-charger.yaml | 24 - description: charge fast mode
35 - const: chg-fast
43 qcom,fast-charge-current-limit:
49 qcom,fast-charge-low-threshold-voltage:
57 qcom,fast-charge-high-threshold-voltage:
63 The fast charger will attempt to charge the battery to this voltage.
66 qcom,fast-charge-safe-voltage:
75 qcom,fast-charge-safe-current:
81 setting this will harmlessly fail. The property 'qcom,fast-charge-current-limit'
165 "chg-fast",
[all …]
|
| A D | qcom,pm8916-lbc.yaml | 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>;
|
| A D | maxim,max14577.yaml | 39 maxim,fast-charge-uamp:
57 - maxim,fast-charge-uamp
71 maxim,fast-charge-uamp:
80 maxim,fast-charge-uamp:
|
| A D | rohm,bd99954.yaml | 35 # 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)
|
| /linux/arch/arm/boot/dts/qcom/ |
| A D | qcom-msm8974pro-sony-xperia-shinano-leo.dts | 32 qcom,fast-charge-safe-current = <3000000>;
33 qcom,fast-charge-current-limit = <2150000>;
34 qcom,fast-charge-safe-voltage = <4400000>;
35 qcom,fast-charge-high-threshold-voltage = <4350000>;
|
| A D | qcom-msm8974pro-sony-xperia-shinano-aries.dts | 32 qcom,fast-charge-safe-current = <2100000>;
33 qcom,fast-charge-current-limit = <1800000>;
34 qcom,fast-charge-safe-voltage = <4400000>;
35 qcom,fast-charge-high-threshold-voltage = <4350000>;
|
| A D | qcom-msm8974pro-sony-xperia-shinano-castor.dts | 137 qcom,fast-charge-safe-current = <1500000>;
138 qcom,fast-charge-current-limit = <1500000>;
141 qcom,fast-charge-safe-voltage = <4400000>;
142 qcom,fast-charge-high-threshold-voltage = <4350000>;
143 qcom,fast-charge-low-threshold-voltage = <3400000>;
|
| A D | qcom-msm8974-sony-xperia-rhine-amami.dts | 11 qcom,fast-charge-safe-current = <1300000>;
12 qcom,fast-charge-current-limit = <1300000>;
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| A D | spear_smi.txt | 12 - st,smi-fast-mode : Flash supports read in fast mode
26 st,smi-fast-mode;
|
| /linux/Documentation/devicetree/bindings/nios2/ |
| A D | nios2.txt | 30 - 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>;
|
| /linux/Documentation/devicetree/bindings/timer/ |
| A D | img,pistachio-gptimer.txt | 11 "fast", fast counter clock
26 clock-names = "fast", "slow", "sys";
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| A D | i2c-pxa.yaml | 47 mrvl,i2c-fast-mode:
49 description: Enable fast mode of i2c controller.
69 mrvl,i2c-fast-mode;
|
| /linux/Documentation/filesystems/ |
| A D | journalling.rst | 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.
162 Currently, only Ext4 implements fast commits. For details of its implementation
[all …]
|
| /linux/Documentation/devicetree/bindings/soc/tegra/ |
| A D | nvidia,nvec.yaml | 27 - description: fast clock
33 - const: fast-clk
81 clock-names = "div-clk", "fast-clk";
|
| /linux/fs/afs/ |
| A D | fs_probe.c | 59 struct afs_server *server, bool fast) in afs_schedule_fs_probe() argument
67 atj += fast ? afs_fs_probe_fast_poll_interval : afs_fs_probe_slow_poll_interval; in afs_schedule_fs_probe()
410 struct afs_server *fast, *slow, *server; in afs_fs_probe_dispatcher() local
430 fast = slow = server = NULL; in afs_fs_probe_dispatcher()
435 fast = list_first_entry(&net->fs_probe_fast, struct afs_server, probe_link); in afs_fs_probe_dispatcher()
436 poll_at = fast->probed_at + afs_fs_probe_fast_poll_interval; in afs_fs_probe_dispatcher()
440 fast = NULL; in afs_fs_probe_dispatcher()
455 server = fast ?: slow; in afs_fs_probe_dispatcher()
|
| /linux/Documentation/virt/kvm/ |
| A D | locking.rst | 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
212 atomically update the spte and the race caused by fast page fault can be avoided.
[all …]
|
| /linux/mm/ |
| A D | gup_test.c | 229 bool fast; in pin_longterm_test_start() local
254 fast = !!(args.flags & PIN_LONGTERM_TEST_FLAG_USE_FAST); in pin_longterm_test_start()
256 if (!fast && mmap_read_lock_killable(current->mm)) { in pin_longterm_test_start()
268 if (fast) in pin_longterm_test_start()
283 if (!fast) in pin_longterm_test_start()
|
| /linux/arch/xtensa/kernel/ |
| A D | traps.c | 83 int fast; member
500 int fast = dispatch_init_table[i].fast; in trap_init() local
504 if (fast == 0) in trap_init()
506 if ((fast & USER) != 0) in trap_init()
508 if ((fast & KRNL) != 0) in trap_init()
|
| /linux/Documentation/filesystems/ext4/ |
| A D | journal.rst | 31 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.
681 - Unused bytes in the fast commit area.
684 - Mark the end of a fast commit
707 system. This is what guarantees idempotence of fast commit replay.
[all …]
|
| /linux/arch/arm/boot/dts/aspeed/ |
| A D | aspeed-bmc-qcom-dc-scm-v1.dts | 65 m25p,fast-read;
73 m25p,fast-read;
87 m25p,fast-read;
|
| A D | ast2500-facebook-netbmc-common.dtsi | 52 m25p,fast-read;
58 m25p,fast-read;
|
| A D | aspeed-bmc-opp-vesnin.dts | 84 m25p,fast-read;
91 m25p,fast-read;
104 m25p,fast-read;
|
| /linux/Documentation/devicetree/bindings/cpufreq/ |
| A D | nvidia,tegra124-cpufreq.txt | 11 - cpu_g: Clock mux for the fast CPU cluster.
13 - pll_p: Auxiliary PLL used during fast PLL rate changes.
|
| /linux/Documentation/devicetree/bindings/mfd/ |
| A D | maxim,max8925.yaml | 71 fast-charge:
72 description: set charging current in fast mode, configures bits 0-3 in CHG_CNTL1
140 fast-charge = <7>;
|
| /linux/drivers/pcmcia/ |
| A D | sa11xx_base.h | 96 #define MECR_FAST_SET(mecr, sock, fast) \ argument
97 MECR_SET((mecr), (sock), MECR_FAST_SHIFT, MECR_FAST_MODE_MASK, (fast))
|