wireless: bcmdhd: remove __wl_band_5ghz_a.n/2ghz.n_channel in bandlis.

.t conditional

-suspected to cause dissappearing AP list, resulting in a disconnect, for some.

Change-Id: Id19838f25a3678cb6be149c3f6c8375bed70cea6

commit 0c3939cc8d239f3a3260e2839b22f16e3eae86cb 1 parent c550a6e23f
pershoot authored 2 days ago
net: wireless: bcmdhd: Reload FW in case of constant scan failure

Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>

commit fb8ec3ff66bca9f3574a597afeb2fad7e1f64794 1 parent 0c3939cc8d
Dmitry Shmidt authored 6 days ago pershoot committed 14 hours ago
net: wireless: bcmdhd: Reduce priority for dhd_dpc and watchdog

Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>

commit 347377a344a94d30a1a98acc77cc67f0c0818c28 1 parent fb8ec3ff66
Dmitry Shmidt authored 6 days ago pershoot committed 14 hours ago
ALSA: usb-audio: fixed usb audio subsystem initialization

If USB audio device is already present on bus during
snd_usb_audio_init initialization will fail and kernel
will reboot due to null-pointer dereference.

The snd_usb_audio_init consists of 2 steps:
1) usb_register() - registers USB audio driver
2) switch_dev_register() - initializes the switch_dev sdev structure

If there is no USB audio device present on the bus, the
snd_usb_audio_init will finish with initialized sdev structure.
After that if USB audio device is plugged, the usb_audio_probe
callback will initialize device (during this step we are accessing sdev)

But if USB audio device is already present on bus during
snd_usb_audio_init initialization, usb_audio_probe callback will
be called during usb_register() - when sdev isn't initialized yet.
We are getting reboot due to null-pointer dereference.

Changed order of described steps so sdev is initialized when
calling usb_register.

Change-Id: Id22356157af2b69038506f1138a6da78d8f1e727
Signed-off-by: Ruslan Bilovol <ruslan.bilovol@ti.com>

Conflicts:

	sound/usb/card.c

commit 29222fcc5d5c35fc6b161f9eedde887ea7bdd0bd 1 parent a3613d237c
Ruslan Bilovol authored 15 days ago drod2169 committed 3 days ago
cpufreq: interactive governor: Add a time view concept

CPUFreq governors are always a tradeoff between power vs performance.
For low power UCs we want to have a less reponsive cpufreq governor that
does not respond or react to each load pick.
However when scrolling on the screen or during webbrowsing we need a more
responsive governor that interact or esponse to each load variation.

To detect which kind of application we have, we'll rely on the history of
the load. if the the average over the load history is high that means we
need to be more responsive so we change the governor paramters in that
direction.
if the average over the load history is low thatmeans we are in low power
UCs so we change the governor parameter to be less responsive

Change-Id: Ifd55ac4cfbc1bd9eded4ae603b158054c6169e8c
Signed-off-by: Nicole Chalhoub <n-chalhoub@ti.com>
Signed-off-by: Taras Kondratiuk <taras@ti.com>

commit 270d50d26b717a606ba959c7c4fe654e11bd990f 1 parent 6159f9c2b8
Nicole Chalhoub authored 2 months ago myfluxi committed 11 hours ago
haptic: restore haptic feedback for samsung roms
gokhanmoral authored a day ago

adapted by dorimanx.