| /linux/lib/crypto/arm/ |
| H A D | poly1305-armv4.pl | 493 my ($R0,$R1,$S1,$R2,$S2,$R3,$S3,$R4,$S4) = map("d$_",(0..9));
538 vdup.32 $S3,r4
570 vmlal.u32 $D0,$R2,${S3}[1]
572 vmlal.u32 $D1,$R3,${S3}[1]
573 vmlal.u32 $D2,$R4,${S3}[1]
676 vshl.u32 $S3,$R3,#2
681 vadd.i32 $S3,$S3,$R3
686 vst4.32 {${S2}[0],${R3}[0],${S3}[0],${R4}[0]},[$tbl0]!
687 vst4.32 {${S2}[1],${R3}[1],${S3}[1],${R4}[1]},[$tbl1]!
703 vshl.u32 $S3,$D3#lo,#2
[all …]
|
| /linux/Documentation/fb/ |
| H A D | s3fb.rst | 2 s3fb - fbdev driver for S3 Trio/Virge chips
9 S3 Trio32
10 S3 Trio64 (and variants V+, UV+, V2/DX, V2/GX)
11 S3 Virge (and variants VX, DX, GX and GX2+)
12 S3 Plato/PX (completely untested)
13 S3 Aurora64V+ (completely untested)
40 hardware, i get best results from plain S3 Trio32 card - about 75 MHz). This
43 support is broken on S3 Trio64 V2/DX.
78 * text mode broken on S3 Trio64 V2/DX
|
| /linux/lib/crypto/arm64/ |
| H A D | poly1305-armv8.pl | 265 my ($R0,$R1,$S1,$R2,$S2,$R3,$S3,$R4,$S4) = map("v$_.4s",(0..8));
518 ld1 {$S2,$R3,$S3,$R4},[x15],#64
608 umlal $ACC0,$IN23_2,${S3}[2]
617 umlal $ACC1,$IN23_3,${S3}[2]
628 umlal $ACC2,$IN23_4,${S3}[2]
642 umlal $ACC0,$IN01_2,${S3}[0]
686 umlal $ACC1,$IN01_3,${S3}[0]
699 umlal $ACC2,$IN01_4,${S3}[0]
761 umull2 $ACC0,$IN23_2,${S3}
785 umlal2 $ACC1,$IN23_3,${S3}
[all …]
|
| /linux/scripts/coccinelle/null/ |
| H A D | deref_null.cocci | 57 statement S1,S2,S3,S4;
90 else S3
118 statement S1,S2,S3,S4;
150 else S3
178 statement S1,S2,S3,S4;
211 else S3
251 statement S1,S2,S3,S4;
283 else S3
|
| /linux/Documentation/scsi/ |
| H A D | cxgb3i.rst | 4 Chelsio S3 iSCSI Driver for Linux
18 On transmitting, Chelsio S3 h/w computes and inserts the Header and
20 On receiving, Chelsio S3 h/w computes and verifies the Header and
25 S3 h/w can directly place the iSCSI Data-In or Data-Out PDU's
32 On transmitting, S3 h/w accepts the complete PDU (header + data)
38 On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
|
| /linux/Documentation/power/ |
| H A D | tricks.rst | 2 swsusp/S3 tricks
7 If you want to trick swsusp/S3 into working, you might want to try:
26 S3. Try that first.
|
| H A D | video.rst | 2 Video issues with S3 resume
7 During S3 resume, hardware needs to be reinitialized. For most
40 There are a few types of systems where video works after S3 resume:
42 (1) systems where video state is preserved over S3.
44 (2) systems where it is possible to call the video BIOS during S3
141 HP Omnibook XE3GC none (1), video is S3 Savage/IX-MV
144 IBM TP T20, model 2647-44G none (1), video is S3 Inc. 86C270-294
|
| /linux/drivers/block/drbd/ |
| H A D | drbd_state.h | 45 #define NS3(T1, S1, T2, S2, T3, S3) \ argument
49 val.T2 = (S2); val.T3 = (S3); val; })
56 #define _NS3(D, T1, S1, T2, S2, T3, S3) \ argument
58 __ns.T2 = (S2); __ns.T3 = (S3); __ns; })
|
| /linux/kernel/trace/rv/monitors/sleep/ |
| H A D | sleep.h | 67 S3, enumerator
180 __set_bit(S3, next); in ltl_possible_next_states()
194 __set_bit(S3, next); in ltl_possible_next_states()
202 case S3: in ltl_possible_next_states()
238 __set_bit(S3, next); in ltl_possible_next_states()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-acpi | 7 S3 suspend and S3 resume. This sysfs entry contains the
29 OS write to SLP_TYP upon entry to S3. In
33 hardware entry to S3. In nanoseconds.
35 resume_count: A count of the number of S3 resume cycles
41 platform runtime firmware S3 resume, just prior to
|
| H A D | sysfs-devices-platform-ACPI-TAD | 37 expires, it will immediately wake up the system from the S3
70 (S3 or S4/S5 if supported) if set.
81 it will immediately wake up the system from the S3 sleep state
|
| /linux/drivers/net/ethernet/chelsio/cxgb4/ |
| H A D | cxgb4_debugfs.c | 2669 #define S3(fmt_spec, s, v) \ in sge_qinfo_show() macro
2676 #define S(s, v) S3("s", s, v) in sge_qinfo_show()
2677 #define T3(fmt_spec, s, v) S3(fmt_spec, s, tx[i].v) in sge_qinfo_show()
2678 #define T(s, v) S3("u", s, tx[i].v) in sge_qinfo_show()
2680 #define R3(fmt_spec, s, v) S3(fmt_spec, s, rx[i].v) in sge_qinfo_show()
2681 #define R(s, v) S3("u", s, rx[i].v) in sge_qinfo_show()
2701 S3("u", "DCB PGID:", in sge_qinfo_show()
2704 S3("u", "DCB PFC:", in sge_qinfo_show()
2713 S3("u", "Intr delay:", qtimer_val(adap, &rx[i].rspq)); in sge_qinfo_show()
2714 S3("u", "Intr pktcnt:", s->counter_val[rx[i].rspq.pktcnt_idx]); in sge_qinfo_show()
[all …]
|
| /linux/arch/arm/boot/dts/samsung/ |
| H A D | exynos4412-i9305.dts | 6 model = "Samsung Galaxy S3 (GT-I9305) based on Exynos4412";
|
| H A D | exynos4412-i9300.dts | 13 model = "Samsung Galaxy S3 (GT-I9300) based on Exynos4412";
|
| /linux/drivers/net/ethernet/chelsio/cxgb4vf/ |
| H A D | cxgb4vf_main.c | 2050 #define S3(fmt_spec, s, v) \ in sge_qinfo_show() macro
2057 #define S(s, v) S3("s", s, v) in sge_qinfo_show()
2058 #define T(s, v) S3("u", s, txq[qs].v) in sge_qinfo_show()
2059 #define R(s, v) S3("u", s, rxq[qs].v) in sge_qinfo_show()
2071 S3("d", "Port:", in sge_qinfo_show()
2084 S3("u", "Intr delay:", qtimer_val(adapter, &rxq[qs].rspq)); in sge_qinfo_show()
2085 S3("u", "Intr pktcnt:", in sge_qinfo_show()
2125 #undef S3 in sge_qinfo_show()
2186 #define S3(fmt, s, v) \ in sge_qstats_show() macro
2193 #define S(s, v) S3("s", s, v) in sge_qstats_show()
[all …]
|
| /linux/Documentation/devicetree/bindings/mips/brcm/ |
| H A D | soc.txt | 18 For power management (particularly, S2/S3/S5 system suspend), the following SoC
128 deep sleep states (S3).
|
| /linux/lib/crypto/x86/ |
| H A D | poly1305-x86_64-cryptogams.pl | 2207 my ($R0,$R1,$R2,$R3,$R4, $S1,$S2,$S3,$S4) = map("%zmm$_",(16..24));
2256 vmovdqu `16*6-64`($ctx),%x#$T3 # ... ${S3}
2271 vpermd $T3,$T2,$S3
2277 vmovdqa64 $S3,0xc0(%rsp){%k2}
2309 vpmuludq $T2,$S3,$M0
2324 vpmuludq $T3,$S3,$M1
2336 vpmuludq $T4,$S3,$M2
2413 vpslld \$2,$R3,$S3
2417 vpaddd $R3,$S3,$S3
2473 vpmuludq $H2,$S3,$D0 # d0 = h2*s3
[all …]
|
| /linux/arch/x86/kernel/acpi/ |
| H A D | wakeup_32.S | 82 # In case of S3 failure, we'll emerge here. Jump
|
| /linux/drivers/soc/loongson/ |
| H A D | Kconfig | 26 S2Idle (Suspend To Idle), ACPI S3 (Suspend To RAM), ACPI S4 (Suspend To
|
| /linux/Documentation/arch/x86/ |
| H A D | intel_txt.rst | 172 - In the case of S3, tboot will also register itself as the resume
176 transfer control back to the kernel's S3 resume vector.
177 In order to preserve system integrity across S3, the kernel
180 the S3 transition) that tboot will calculate a MAC (message
|
| /linux/arch/x86/crypto/ |
| H A D | serpent-sse2-i586-asm_32.S | 195 #define S3(x0, x1, x2, x3, x4) \ macro
519 S3(RB, RD, RE, RC, RA); LK(RC, RA, RD, RB, RE, 4);
527 S3(RA, RD, RB, RE, RC); LK(RE, RC, RD, RA, RB, 12);
535 S3(RC, RD, RA, RB, RE); LK(RB, RE, RD, RC, RA, 20);
543 S3(RE, RD, RC, RA, RB); LK(RA, RB, RD, RE, RC, 28);
|
| /linux/drivers/input/gameport/ |
| H A D | Kconfig | 15 S3 SonicVibes, Trident 4DWave, SiS7018, and ALi 5451 gameport
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3399-gru.dtsi | 299 * When we go into S3 ARM Trusted Firmware will transition our PWM regulators
693 * At the moment settings are identical for S0 and S3, but if we later
694 * need to configure things differently for S3 we'll adjust here.
698 &ap_pwroff /* AP will auto-assert this when in S3 */
|
| /linux/tools/power/pm-graph/config/ |
| H A D | suspend.cfg | 2 # Generic S3 (Suspend to Mem) test
|
| H A D | suspend-callgraph.cfg | 2 # Full Callgraph for S3 (Suspend to Mem) test
|