Media is too big
VIEW IN TELEGRAM
Pgr gayming sorry I just play playing pgr I'm new
Using halcyon vulkan 1.3 and my kernel
Using halcyon vulkan 1.3 and my kernel
Juan | #KanaDev_IS | #AntiHorny |
NexusKernel!-KSUN-YUKI_22+bolt +pgo +lto +polly +pstl.zip
Idk Its boot on my device
Forwarded from GitHub
🔨 3 new commits to kernel_common-5.10:android12-5.10:
7671b6c: thermal: auto-suppress Kasumi/Iyashi while a charger is online
Some Transsion userspace battery managers read the post-Kasumi
dampened thermal_zone temperature and refuse to start charging until
that reading falls inside a vendor-specific band. Because Kasumi
intentionally lags the real temperature, the band check spins and
the device throws "won't charge until normal temps" warnings on a
battery that is otherwise healthy. Iyashi can trigger the same
class of surprise for any userspace that watches cooling-device
cur_state.
Add a small charger-aware guard that registers a power_supply
notifier and OR-reduces ONLINE across MAINS / USB-family / WIRELESS
psys via a debounced (HZ/4) refresh worker. On a 0->1 transition
the guard latches a suppression flag inside both subsystems; on
1->0 it clears it.
Layering is deliberately additive:
- /sys/kernel/{kasumi,iyashi}/enabled keeps its declared meaning.
The guard never writes to it.
- An orthogonal kasumi_charger_suppressed / iyashi_charger_suppressed
flag is added. Effective active state is
(enabled && !charger_suppressed). For Kasumi this is one extra
READ_ONCE on the dampen fast path; for Iyashi the existing
iyashi_active_key static branch is driven by a new
iyashi_recompute_active() helper that ANDs both inputs.
- The new flag is exposed read-only at
/sys/kernel/{kasumi,iyashi}/charger_suppressed for observability.
- Both subsystems' safety self-tests temporarily clear the
suppression flag so a device that boots already plugged in
cannot fail the init-time math check.
Gated by CONFIG_THERMAL_CHARGER_GUARD (default y, depends on
POWER_SUPPLY and (KASUMI || IYASHI)). No new EXPORT_SYMBOL; no KMI
breaks; no removal of existing tunables or sysfs nodes.
Signed-off-by: アンドレイ <xtensei.is.not.in.the.sudoers.file@protonmail.com> by XTENSEI
413062a: Enable Hikari, Kasumi, Iyashi and Charger Guard by default
Already setted as default to y but i want it in gki_defconfig just to be safe so why do you care?
Signed-off-by: アンドレイ <xtensei.is.not.in.the.sudoers.file@protonmail.com> by アンドレイ
451278a: Merge branch 'XTENSEI:android12-5.10' into android12-5.10 by Juanstews
7671b6c: thermal: auto-suppress Kasumi/Iyashi while a charger is online
Some Transsion userspace battery managers read the post-Kasumi
dampened thermal_zone temperature and refuse to start charging until
that reading falls inside a vendor-specific band. Because Kasumi
intentionally lags the real temperature, the band check spins and
the device throws "won't charge until normal temps" warnings on a
battery that is otherwise healthy. Iyashi can trigger the same
class of surprise for any userspace that watches cooling-device
cur_state.
Add a small charger-aware guard that registers a power_supply
notifier and OR-reduces ONLINE across MAINS / USB-family / WIRELESS
psys via a debounced (HZ/4) refresh worker. On a 0->1 transition
the guard latches a suppression flag inside both subsystems; on
1->0 it clears it.
Layering is deliberately additive:
- /sys/kernel/{kasumi,iyashi}/enabled keeps its declared meaning.
The guard never writes to it.
- An orthogonal kasumi_charger_suppressed / iyashi_charger_suppressed
flag is added. Effective active state is
(enabled && !charger_suppressed). For Kasumi this is one extra
READ_ONCE on the dampen fast path; for Iyashi the existing
iyashi_active_key static branch is driven by a new
iyashi_recompute_active() helper that ANDs both inputs.
- The new flag is exposed read-only at
/sys/kernel/{kasumi,iyashi}/charger_suppressed for observability.
- Both subsystems' safety self-tests temporarily clear the
suppression flag so a device that boots already plugged in
cannot fail the init-time math check.
Gated by CONFIG_THERMAL_CHARGER_GUARD (default y, depends on
POWER_SUPPLY and (KASUMI || IYASHI)). No new EXPORT_SYMBOL; no KMI
breaks; no removal of existing tunables or sysfs nodes.
Signed-off-by: アンドレイ <xtensei.is.not.in.the.sudoers.file@protonmail.com> by XTENSEI
413062a: Enable Hikari, Kasumi, Iyashi and Charger Guard by default
Already setted as default to y but i want it in gki_defconfig just to be safe so why do you care?
Signed-off-by: アンドレイ <xtensei.is.not.in.the.sudoers.file@protonmail.com> by アンドレイ
451278a: Merge branch 'XTENSEI:android12-5.10' into android12-5.10 by Juanstews