Dmesg logs are getting flooded with WSA temparature
logs. Change the log level to pr_debug to get rid
of this messages.
Change-Id: Ia4ccca47c5e6e5d56883ff73e1ae4278ff855be3
Signed-off-by: Surendar Karka <skarka@codeaurora.org>
Some alsa API are removed in kernel-4.19 which would cause
codec driver compile failure. Update codec driver to fix it.
Change-Id: Ie358ec1863082166958059c179300b453d2a03ad
Signed-off-by: Meng Wang <mengw@codeaurora.org>
Switch audio drivers to SPDX identifier on msm-4.19.
Change-Id: Ic3f0230a516db251b8d81e8a7e73dbc04d66fe1b
Signed-off-by: Meng Wang <mengw@codeaurora.org>
when wsa881x device is down, reading temperature from driver
returns error. Instead of propagating the error, return the
cached temperature value to the thermal framework to avoid
iterative calls to read the temperature that results in
excessive logging.
Change-Id: I529c83eafec63004c2469bf16a0b53bd5accbdbb
Signed-off-by: Sudheer Papothi <spapothi@codeaurora.org>
Runtime suspend in slimbus driver makes QMI call which takes
wakelock and result in first system suspend to fail. As a result
of first suspend fail, POST_PM_SUSPEND event is dispatched to
thermal core which registered to pm notifier. WSA being one
of registered thermal zone gets query for temperature, and makes
slimbus reads/writes which will result in runtime resume of
slimbus driver to happen. System suspend fails again continuously
in this endless loop as slimbus runtime suspend will make QMI call
again.
Update wsa temp sensor to handle suspend event by registering to
pm notifier and ignore the temperature request from thermal core
at resume. This will avoid slimbus reads/writes during suspend in
progress and allow XO shutdown to happen.
Change-Id: Id13a9701cffb1231ef7d563cbc30756fd71d5868
Signed-off-by: Laxminath Kasam <lkasam@codeaurora.org>
Signed-off-by: Sudheer Papothi <spapothi@codeaurora.org>
