Home
last modified time | relevance | path

Searched refs:S5 (Results 1 – 25 of 25) sorted by relevance

/linux/kernel/trace/rv/monitors/sleep/
H A Dsleep.h69 S5, enumerator
121 __set_bit(S5, mon->states); in ltl_start()
172 __set_bit(S5, next); in ltl_possible_next_states()
210 __set_bit(S5, next); in ltl_possible_next_states()
220 __set_bit(S5, next); in ltl_possible_next_states()
222 case S5: in ltl_possible_next_states()
230 __set_bit(S5, next); in ltl_possible_next_states()
254 __set_bit(S5, next); in ltl_possible_next_states()
/linux/Documentation/ABI/testing/
H A Dsysfs-devices-platform-ACPI-TAD15 BIT(4): Correct status reported for wakeups from S4/S5 if set
17 BIT(6): The AC timer wakes up from S5 if set
19 BIT(8): The DC timer wakes up from S5 if set
38 sleep state (and from S4/S5 too if supported) until its status
70 (S3 or S4/S5 if supported) if set.
82 (and from S4/S5 too if supported) until its status is explicitly
H A Dsysfs-platform-wilco-ec5 Boot on AC is a policy which makes the device boot from S5
47 - In S5, if usb_charge is enabled, then power will be supplied
/linux/arch/arm/boot/dts/qcom/
H A Dqcom-msm8974pro-samsung-klte.dts5 model = "Samsung Galaxy S5";
H A Dqcom-msm8974pro-samsung-kltechn.dts5 model = "Samsung Galaxy S5 China";
/linux/tools/perf/arch/riscv/util/
H A Dunwind-libdw.c43 dwarf_regs[21] = REG(S5); in libdw__arch_set_initial_registers()
/linux/drivers/soc/loongson/
H A DKconfig27 Disk), ACPI S5 (Soft Shutdown) and supports multiple wake-up methods
/linux/arch/x86/crypto/
H A Dserpent-sse2-i586-asm_32.S235 #define S5(x0, x1, x2, x3, x4) \ macro
521 S5(RA, RD, RB, RE, RC); LK(RC, RA, RD, RE, RB, 6);
529 S5(RC, RD, RA, RB, RE); LK(RE, RC, RD, RB, RA, 14);
537 S5(RE, RD, RC, RA, RB); LK(RB, RE, RD, RA, RC, 22);
545 S5(RB, RD, RE, RC, RA); LK(RA, RB, RD, RC, RE, 30);
H A Dserpent-sse2-x86_64-asm_64.S642 S(S5, RA, RD, RB, RE, RC); LK2(RC, RA, RD, RE, RB, 6);
650 S(S5, RC, RD, RA, RB, RE); LK2(RE, RC, RD, RB, RA, 14);
658 S(S5, RE, RD, RC, RA, RB); LK2(RB, RE, RD, RA, RC, 22);
666 S(S5, RB, RD, RE, RC, RA); LK2(RA, RB, RD, RC, RE, 30);
H A Dserpent-avx2-asm_64.S572 S(S5, RA, RD, RB, RE, RC); LK2(RC, RA, RD, RE, RB, 6);
580 S(S5, RC, RD, RA, RB, RE); LK2(RE, RC, RD, RB, RA, 14);
588 S(S5, RE, RD, RC, RA, RB); LK2(RB, RE, RD, RA, RC, 22);
596 S(S5, RB, RD, RE, RC, RA); LK2(RA, RB, RD, RC, RE, 30);
/linux/arch/arm/boot/dts/samsung/
H A Dexynos5422-samsung-k3g.dts3 * Samsung Galaxy S5 (SM-G900H) device-tree source
16 model = "Samsung Galaxy S5 (SM-G900H)";
/linux/Documentation/spi/
H A Dbutterfly.rst69 MISO J403.PE6/DO pin 12/S5,nPAPEROUT
/linux/Documentation/devicetree/bindings/mips/brcm/
H A Dsoc.txt18 For power management (particularly, S2/S3/S5 system suspend), the following SoC
/linux/lib/crypto/
H A Ddes.c437 static const u32 S5[64] = { variable
588 L ^= S5[0xff & (A >> 8)]; A >>= 16; \
/linux/arch/mips/boot/dts/ingenic/
H A Dqi_lb60.dts122 <MATRIX_KEY(0, 3, KEY_F4)>, /* S5 */
/linux/Documentation/devicetree/bindings/arm/bcm/
H A Dbrcm,brcmstb.txt125 For power management (particularly, S2/S3/S5 system suspend), the following SoC
/linux/arch/arm64/boot/dts/qcom/
H A Dsm6125-sony-xperia-seine-pdx201.dts326 * S5 is VDD_MX/WCSS_MX
H A Dsm7325-nothing-spacewar.dts662 * S2, S5, S7, S10 are ARCs:
664 * S5 - mss.lvl,
H A Dsm8250-xiaomi-pipa.dts320 * (S4+S5) - mmcx.lvl,
H A Dsm8350-sony-xperia-sagami.dtsi148 * S5 - mx.lvl
H A Dsm8250-xiaomi-elish-common.dtsi393 * (S4+S5) - mmcx.lvl,
/linux/arch/arm64/boot/dts/freescale/
H A Dimx8mp-toradex-smarc.dtsi996 fsl,pins = <MX8MP_IOMUXC_I2C3_SCL__I2C3_SCL 0x400001c6>, /* SMARC S5 - I2C_CAM0_CK */
1002 fsl,pins = <MX8MP_IOMUXC_I2C3_SCL__GPIO5_IO18 0x400001c6>, /* SMARC S5 - I2C_CAM0_CK */
/linux/arch/sparc/net/
H A Dbpf_jit_comp_64.c52 #define S5(X) ((X) & 0x1f) macro
640 emit(cb_opc | IMMED | WDISP10(off << 2) | RS1(dst) | S5(imm), ctx); in emit_cbcondi()
/linux/arch/arm/boot/dts/ti/omap/
H A Dam335x-mba335x.dts37 label = "S5";
/linux/Documentation/crypto/
H A Ddescore-readme.rst317 bits are manipulated in this arrangement most of the time (S7 S5 S3 S1)::