Fix the following issues found in static analysis:
- missing blank lines after declarations
- unnecessary return in a void function
- exporting world writable files is usually an error
- block comments use * on subsequent and trailing lines
- Add DT binding description and vendor prefixe for the
driver.
- Add Linux Foundation copyright markings.
Change-Id: Id2ed9a6d4e31bd2acd3185bf7ef9c78f8a41cf36
Signed-off-by: Himanshu Aggarwal <haggarwa@codeaurora.org>
Signed-off-by: Vevek Venkatesan <vevekv@codeaurora.org>
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
Change-Id: Ie366894e9e89707fa2950a7ffbfe4e93059a19a3
Signed-off-by: Lawrence Liao <lawrence_liao@pixart.com>
(cherry picked from commit dfc4349a8aa02bb0b7b0639ad5368a5c85f6520f)
Git-commit: dfc4349a8aa02bb0b7b0639ad5368a5c85f6520f
Git-repo: https://github.com/PixartOpen/pixart-sensor-db810-linux-driver
[shjain@codeaurora.org: removed below listed files from original
commit as they are not needed and to resolve trivial merge conflicts:
1. arch/arm/boot/dts/qcom/apq8094-dragonboard.dtsi
2. arch/arm/boot/dts/qcom/msm8994-pinctrl.dtsi
3. arch/arm/boot/dts/qcom/msm8994.dtsi
4. drivers/input/misc/Makefile
5. drivers/input/misc/ots_pat9125/Makefile
Remove the unused pieces of algorithm from the reference
driver of Pixart PAT9125 Rotating side button.]
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
Store the process id in the register trace buffer.
This gives a general idea about what process was last
running when the RTB stopped.
Change-Id: Idcbd8db9eb451f2d732c935f00b6c50f9af3c592
Signed-off-by: Se Wang (Patrick) Oh <sewango@codeaurora.org>
To support ADSP SVA on wcd934x, dedicated backend dailink needs
to be created. Add the dailink associating the specific cpu dai
and the MAD codec dai.
CRs-Fixed: 1070327
Change-Id: I4152d81e4e951216a8ecdd93562eb1740dbb962c
Signed-off-by: Walter Yang <yandongy@codeaurora.org>
Stack canary relies on getting early random values. However, the
software random number generator is initialized relatively late in the
boot process making the stack canary very predictable.
Enable the hardware supported random number generator until
the software number generator is enabled later in boot.
Change-Id: I01dc0cc0d0fc734dbf1166d88d97bcc5102788bb
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
Stack canary initialization involves getting a random number.
Getting this random number may involve accessing caches or other
architectural specific features which are not available until
after the architecture is setup. Move the stack canary initialization
later to accommodate this.
Change-Id: I00b564a2c3172229a44339c061fa380c17fe7d8e
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
[ohaugan@codeaurora.org: Fix trivial merge conflict]
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
Update the droop timer settings for OSM on MSMCOBALT.
Change-Id: I9398a81738a778dfae5282ef6809a8c2174bd589
Signed-off-by: Deepak Katragadda <dkatraga@codeaurora.org>
Parse the Detailed Timing Descriptors of both EDID blocks for
resolutions. Check if the resolution is already added in local
data base. Also, add tolerance to fps and pclk variations for
a give resolution so that EDID parser can capture all the
resolutions correctly as published by the sink's EDID.
Change-Id: I113988eb21f82eef022723c421b1c1c9d4dead9f
Signed-off-by: Ajay Singh Parmar <aparmar@codeaurora.org>
The scm APIs need an update for v8. Update accordingly.
Change-Id: Ia848af5bafe2337718fffdd87cd6436eb0133ece
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
The existing support for generating random numbers relied on
a hacked up version of CONFIG_ARCH_RANDOM and was prone to
scheduling while atomic bugs due to needing to take a mutex.
We don't actually need the additional randomness all the time,
the pool just needs to be initialized with some amount of random
data to avoid getting the same result each time. Switch to
this method for initializing the random pool.
Change-Id: I804ec7556cbd18ff2d9869a03069fda1dd519a79
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
[ohaugan@codeaurora.org: Fixed trivial merge conflicts]
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
Currently, the software random number generator is not initialized
until relatively late in the boot process. Software that relies on
random numbers early will not be reliable. Entropy sources are
available early but not early enough for some use cases which means
that moving the software random number generation earlier is not an
option. As an alternate solution, implement the functions associated
with CONFIG_ARCH_RANDOM. These functions currently make a call into
trustzone to get reliable random numbers. The functions are disabled
once the regular random number generator is sufficiently reliable.
Change-Id: If40cfcb96b091fa26a28047c10a902287b26f6c1
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
[ohaugan@codeaurora.org: Dropped Makefile from patch set]
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
When WDSP has crashed, G-link link state is updated with
GLINK_LINK_STATE_DOWN and remote side channels are closed.
Handle the link state down notification from G-link and
close the channels from local side when remote disconnect
channel event occurs.
Change-Id: Id956256fbb3ea6b18a3685a34dcd1f9b16e71e92
Signed-off-by: Vidyakumar Athota <vathota@codeaurora.org>
While flushing debug queues, avoid touching message queues.
Bleeding message queues here can discard FW responses and
forward threads may timeout by not receiving them. This can
cause confusion about timeouts. Hence don't touch message
queues unless you process and send them to forward thread.
CRs-Fixed: 1066658
Change-Id: I7a5a89c32dc4b1284895d01202dcfdd8a90ccda0
Signed-off-by: Praneeth Paladugu <ppaladug@codeaurora.org>
Previously memory retention and preiph control are only set when
device enters/exits idle power collapse mode. The memory retention
and periph setting will remain ON when device is actually in
suspend state, which will cause unnecessary power consumption.
This change updates those setting for both idle power collapse cases
and suspend/resume case. With this change, the memory retention and
periph will be set to OFF in suspend case to optimize power consumption.
Change-Id: I1598dbc97cb9d02b946de5c9803a49d923c7edc1
Signed-off-by: Ping Li <pingli@codeaurora.org>
When VT is enabled, Propagate AV timer timestamp as part of SOF
CRs-fixed: 1039601
Change-Id: Ic6bed924911a6db27e84b10921f6c6b400f1c8fb
Signed-off-by: Nagesh Subba Reddy <nageshsreddy@codeaurora.org>
Signed-off-by: Harsh Shah <harshs@codeaurora.org>
Signed-off-by: Jing Zhou <jzhou70@codeaurora.org>
a540 hardware does not support BCL and LMH after all.
CRs-Fixed: 1075694
Change-Id: I09808145d20ded63b5043cae6510429560cb599e
Signed-off-by: Oleg Perelet <operelet@codeaurora.org>
Backlight set function call should be protected by mutex
as this call could be called from different threads.
CRs-Fixed: 1074738
Change-Id: Ie7f8cee59b90f16f8a844d618a6f903b3e3c2f27
Signed-off-by: Abhijit Kulkarni <kabhijit@codeaurora.org>
Call rdev_get_name() to obtain the name to use in the debug
consumer's regulator_get() call so that the debug consumer finds
the correct regulator when the name differs in the constraints
and desc structs.
Change-Id: Id6a47467cd118c89c8f58d1120381d4c64f8efee
CRs-Fixed: 1075693
Signed-off-by: David Collins <collinsd@codeaurora.org>
Temperature compensation is needed for charger die
temperature. Offset and slope coefficients are applied
based on the FAB ID read from the REVID peripheral.
Change-Id: I8516a8109b8c9316dafbd547635d4c97bd50be0c
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
