Home
last modified time | relevance | path

Searched refs:spending (Results 1 – 8 of 8) sorted by relevance

/linux-6.15/drivers/net/wireless/ath/ath5k/
H A Dreset.c284 u32 scal, spending, sclock; in ath5k_hw_set_sleep_clock() local
305 spending = 0x14; in ath5k_hw_set_sleep_clock()
307 spending = 0x18; in ath5k_hw_set_sleep_clock()
308 ath5k_hw_reg_write(ah, spending, AR5K_PHY_SPENDING); in ath5k_hw_set_sleep_clock()
361 spending = 0x14; in ath5k_hw_set_sleep_clock()
363 spending = 0x18; in ath5k_hw_set_sleep_clock()
364 ath5k_hw_reg_write(ah, spending, AR5K_PHY_SPENDING); in ath5k_hw_set_sleep_clock()
/linux-6.15/drivers/gpu/drm/ci/
H A Dgitlab-ci.yml298 # Jobs that need to pass before spending hardware resources on further testing
/linux-6.15/Documentation/driver-api/driver-model/
H A Ddevres.rst31 bunch, but aren't all low level driver developers? After spending a
/linux-6.15/Documentation/admin-guide/mm/
H A Dconcepts.rst68 accesses are slow relatively to CPU speed. To avoid spending precious
/linux-6.15/Documentation/process/
H A D5.Posting.rst162 changelogs is a crucial but often-neglected art; it's worth spending
/linux-6.15/Documentation/mm/
H A Dunevictable-lru.rst38 spending 100% of their time in vmscan for hours or days on end, with the system
/linux-6.15/Documentation/admin-guide/
H A Dverify-bugs-and-bisect-regressions.rst470 spending much effort on, as long as it boots and allows to properly test the
H A Dreporting-issues.rst766 Do not hurry with this step of the reporting process: spending 30 to 60 minutes