Home
last modified time | relevance | path

Searched refs:S3 (Results 1 – 47 of 47) sorted by relevance

/linux-4.4.14/Documentation/fb/
Ds3fb.txt2 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
D00-INDEX49 - info on the fbdev driver for S3 Trio/Virge chips.
/linux-4.4.14/Documentation/video4linux/bttv/
DPROBLEMS5 - The memory of some S3 cards is not recognized right:
16 Some S3 cards even take up 64MB of memory but only report 32MB to the BIOS.
25 with his S3 868 went away when he upgraded to XFree 3.2.
28 - I still only get a black picture with my S3 card!
30 Even with XFree-3.2A some people have problems with their S3 cards
33 bttv with it. bttv seems to work with most S3 cards with Accelerated X.
42 Better linear frame buffer support for S3 cards will probably be in
59 - Some S3 cards and the Matrox Mystique will produce pixel errors with
/linux-4.4.14/scripts/coccinelle/null/
Dderef_null.cocci56 statement S1,S2,S3,S4;
89 else S3
117 statement S1,S2,S3,S4;
149 else S3
177 statement S1,S2,S3,S4;
210 else S3
250 statement S1,S2,S3,S4;
282 else S3
/linux-4.4.14/Documentation/power/
Dtricks.txt1 swsusp/S3 tricks
5 If you want to trick swsusp/S3 into working, you might want to try:
24 S3. Try that first.
Dvideo.txt2 Video issues with S3 resume
6 During S3 resume, hardware needs to be reinitialized. For most
39 There are a few types of systems where video works after S3 resume:
41 (1) systems where video state is preserved over S3.
43 (2) systems where it is possible to call the video BIOS during S3
129 HP Omnibook XE3GC none (1), video is S3 Savage/IX-MV
132 IBM TP T20, model 2647-44G none (1), video is S3 Inc. 86C270-294 Savage/IX-MV, vesafb gets "interes…
D00-INDEX34 - Explains the interaction between Suspend-to-RAM (S3) and CPU hotplug
40 - Goals, implementation, and usage of software suspend (ACPI S3)
Dstates.txt60 ACPI State: S3
Dsuspend-and-cpuhotplug.txt1 Interaction of Suspend code (S3) with the CPU hotplug infrastructure
Dpci.txt183 defines four system sleep states, S1, S2, S3, and S4, and denotes the system
430 be preserved, such as one of the ACPI sleep states S1-S3, the phases are:
498 S1-S3, into the working state (ACPI S0), the phases are:
/linux-4.4.14/Documentation/scsi/
Dcxgb3i.txt1 Chelsio S3 iSCSI Driver for Linux
14 On transmitting, Chelsio S3 h/w computes and inserts the Header and
16 On receiving, Chelsio S3 h/w computes and verifies the Header and
21 S3 h/w can directly place the iSCSI Data-In or Data-Out PDU's
28 On transmitting, S3 h/w accepts the complete PDU (header + data)
34 On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
/linux-4.4.14/drivers/block/drbd/
Ddrbd_state.h44 #define NS3(T1, S1, T2, S2, T3, S3) \ argument
48 val.T2 = (S2); val.T3 = (S3); val; })
55 #define _NS3(D, T1, S1, T2, S2, T3, S3) \ argument
57 __ns.T2 = (S2); __ns.T3 = (S3); __ns; })
/linux-4.4.14/crypto/
Dserpent_generic.c102 #define S3(x0, x1, x2, x3, x4) ({ \ macro
399 S3(r3, r4, r0, r1, r2); store_and_load_keys(r1, r2, r4, r3, 28, 24); in __serpent_setkey()
407 S3(r2, r4, r3, r0, r1); store_and_load_keys(r0, r1, r4, r2, -4, -8); in __serpent_setkey()
416 S3(r1, r4, r2, r3, r0); store_and_load_keys(r3, r0, r4, r1, 14, 10); in __serpent_setkey()
424 S3(r0, r4, r1, r2, r3); store_and_load_keys(r2, r3, r4, r0, -18, -22); in __serpent_setkey()
433 S3(r3, r4, r0, r1, r2); storekeys(r1, r2, r4, r3, 0); in __serpent_setkey()
466 S3(r1, r3, r4, r2, r0); LK(r2, r0, r3, r1, r4, 4); in __serpent_encrypt()
474 S3(r0, r3, r1, r4, r2); LK(r4, r2, r3, r0, r1, 12); in __serpent_encrypt()
482 S3(r2, r3, r0, r1, r4); LK(r1, r4, r3, r2, r0, 20); in __serpent_encrypt()
490 S3(r4, r3, r2, r0, r1); LK(r0, r1, r3, r4, r2, 28); in __serpent_encrypt()
Ddes_generic.c408 static const u32 S3[64] = { variable
600 L ^= S3[0xff & A]; \
/linux-4.4.14/drivers/net/ethernet/chelsio/cxgb4vf/
Dcxgb4vf_main.c1741 #define S3(fmt_spec, s, v) \ in sge_qinfo_show() macro
1748 #define S(s, v) S3("s", s, v) in sge_qinfo_show()
1749 #define T(s, v) S3("u", s, txq[qs].v) in sge_qinfo_show()
1750 #define R(s, v) S3("u", s, rxq[qs].v) in sge_qinfo_show()
1762 S3("d", "Port:", in sge_qinfo_show()
1775 S3("u", "Intr delay:", qtimer_val(adapter, &rxq[qs].rspq)); in sge_qinfo_show()
1776 S3("u", "Intr pktcnt:", in sge_qinfo_show()
1816 #undef S3 in sge_qinfo_show()
1894 #define S3(fmt, s, v) \ in sge_qstats_show() macro
1901 #define S(s, v) S3("s", s, v) in sge_qstats_show()
[all …]
/linux-4.4.14/drivers/net/ethernet/chelsio/cxgb4/
Dcxgb4_debugfs.c2262 #define S3(fmt_spec, s, v) \ in sge_qinfo_show() macro
2269 #define S(s, v) S3("s", s, v) in sge_qinfo_show()
2270 #define T3(fmt_spec, s, v) S3(fmt_spec, s, tx[i].v) in sge_qinfo_show()
2271 #define T(s, v) S3("u", s, tx[i].v) in sge_qinfo_show()
2273 #define R3(fmt_spec, s, v) S3(fmt_spec, s, rx[i].v) in sge_qinfo_show()
2274 #define R(s, v) S3("u", s, rx[i].v) in sge_qinfo_show()
2293 S3("u", "DCB PGID:", in sge_qinfo_show()
2296 S3("u", "DCB PFC:", in sge_qinfo_show()
2305 S3("u", "Intr delay:", qtimer_val(adap, &rx[i].rspq)); in sge_qinfo_show()
2306 S3("u", "Intr pktcnt:", in sge_qinfo_show()
[all …]
/linux-4.4.14/arch/x86/kernel/acpi/
Dwakeup_32.S81 # In case of S3 failure, we'll emerge here. Jump
/linux-4.4.14/Documentation/
Dintel_txt.txt156 - In the case of S3, tboot will also register itself as the resume
160 transfer control back to the kernel's S3 resume vector.
161 In order to preserve system integrity across S3, the kernel
164 the S3 transition) that tboot will calculate a MAC (message
Dsvga.txt148 cards with S3 chipsets and old Cirrus Logic BIOSes) -- mainly extra lines at the
Dkernel-parameters.txt387 on resume from S1/S3 (which is against the ACPI spec,
/linux-4.4.14/arch/x86/crypto/
Dserpent-sse2-i586-asm_32.S210 #define S3(x0, x1, x2, x3, x4) \ macro
534 S3(RB, RD, RE, RC, RA); LK(RC, RA, RD, RB, RE, 4);
542 S3(RA, RD, RB, RE, RC); LK(RE, RC, RD, RA, RB, 12);
550 S3(RC, RD, RA, RB, RE); LK(RB, RE, RD, RC, RA, 20);
558 S3(RE, RD, RC, RA, RB); LK(RA, RB, RD, RE, RC, 28);
Dserpent-sse2-x86_64-asm_64.S655 S(S3, RB, RD, RE, RC, RA); LK2(RC, RA, RD, RB, RE, 4);
663 S(S3, RA, RD, RB, RE, RC); LK2(RE, RC, RD, RA, RB, 12);
671 S(S3, RC, RD, RA, RB, RE); LK2(RB, RE, RD, RC, RA, 20);
679 S(S3, RE, RD, RC, RA, RB); LK2(RA, RB, RD, RE, RC, 28);
Dserpent-avx2-asm_64.S580 S(S3, RB, RD, RE, RC, RA); LK2(RC, RA, RD, RB, RE, 4);
588 S(S3, RA, RD, RB, RE, RC); LK2(RE, RC, RD, RA, RB, 12);
596 S(S3, RC, RD, RA, RB, RE); LK2(RB, RE, RD, RC, RA, 20);
604 S(S3, RE, RD, RC, RA, RB); LK2(RA, RB, RD, RE, RC, 28);
Dserpent-avx-x86_64-asm_64.S588 S(S3, RB, RD, RE, RC, RA); LK2(RC, RA, RD, RB, RE, 4);
596 S(S3, RA, RD, RB, RE, RC); LK2(RE, RC, RD, RA, RB, 12);
604 S(S3, RC, RD, RA, RB, RE); LK2(RB, RE, RD, RC, RA, 20);
612 S(S3, RE, RD, RC, RA, RB); LK2(RA, RB, RD, RE, RC, 28);
/linux-4.4.14/Documentation/isdn/
DREADME.icn33 S3 S2 S1 Base-address
47 S1 S2 S3 S4 Base-Address
DREADME.act200017 S1 S2 S3 S4 Base-port
/linux-4.4.14/drivers/input/gameport/
DKconfig13 S3 SonicVibes, Trident 4DWave, SiS7018, and ALi 5451 gameport
/linux-4.4.14/drivers/gpu/drm/msm/
DNOTES6 + MDP4 - S3 (APQ8060, touchpad), S4-pro (APQ8064, nexus4 & ifc6410)
/linux-4.4.14/arch/cris/arch-v32/kernel/
Dkgdb_asm.S387 ;; S3 (MM_CAUSE) is read-only.
Dkgdb.c322 S0, S1, S2, S3, enumerator
/linux-4.4.14/Documentation/x86/
Dmtrr.txt87 (--) S3: PCI: 968 rev 0, Linear FB @ 0xf8000000
96 (--) S3: videoram: 4096k
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,brcmstb.txt123 For power management (particularly, S2/S3/S5 system suspend), the following SoC
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Dtrivial-devices.txt12 abracon,abb5zes3 AB-RTCMC-32.768kHz-B5ZE-S3: Real Time Clock/Calendar Module with I2C Interface
/linux-4.4.14/drivers/video/fbdev/
DKconfig1443 tristate "S3 Trio/Virge support"
1453 Driver for graphics boards with S3 Trio / S3 Virge chip.
1456 bool "DDC for S3 support"
1461 Say Y here if you want DDC support for your S3 graphics card.
1464 tristate "S3 Savage support"
1472 This driver supports notebooks and computers with S3 Savage PCI/AGP
1485 This enables I2C support for S3 Savage Chipsets. This is used
/linux-4.4.14/kernel/power/
DKconfig8 suspend-to-RAM state (e.g. the ACPI S3 state).
/linux-4.4.14/sound/pci/
DKconfig819 tristate "S3 SonicVibes"
825 Say Y here to include support for soundcards based on the S3
Dsonicvibes.c245 { PCI_VDEVICE(S3, 0xca00), 0, },
/linux-4.4.14/drivers/gpio/
DKconfig534 modes (S3 and higher). The remaining four GPIOs are powered by
536 active during S3. The suspend powered GPIOs can be used to wake the
/linux-4.4.14/Documentation/crypto/
Ddescore-readme.txt270 bits are manipulated in this arrangement most of the time (S7 S5 S3 S1):
/linux-4.4.14/Documentation/input/
Djoystick.txt408 3.15 SoundBlaster 64 and 128 - ES1370 and ES1371, ESS Solo1 and S3 SonicVibes
/linux-4.4.14/drivers/rtc/
DKconfig169 tristate "Abracon AB-RTCMC-32.768kHz-B5ZE-S3"
172 AB-RTCMC-32.768kHz-B5ZE-S3 I2C RTC chip.
/linux-4.4.14/Documentation/laptops/
Dthinkpad-acpi.txt405 key presses until a S3 or S4 ACPI
437 press events until a S3 or S4
/linux-4.4.14/drivers/ide/
DKconfig173 machines ACPI support is required to properly handle ACPI S3 states.
/linux-4.4.14/Documentation/networking/
Darcnet-hardware.txt1710 video card (an S3 GENDAC). I leave the full decoding of those addresses to
2331 MTQ-T1-S3
/linux-4.4.14/
DCREDITS1928 D: XFree86 (S3), DCF77, some kernel hacks and fixes
2202 S: Canada K2H 6S3
DMAINTAINERS9102 S3 SAVAGE FRAMEBUFFER DRIVER
/linux-4.4.14/Documentation/sound/alsa/
DALSA-Configuration.txt1842 Module for S3 SonicVibes PCI sound cards.