This reverts commit <a67208e94d945ad890f8dc4734ec5fdb3219cc03>.
This commit prevented xo shutdown as during suspend exit, WSA sensor for
temperature read triggered a slimbus wakeup. Slimbus suspend mechanism
will expect a qmi message after the system has entered suspend. This
will wake the system from suspend. This happens recursively and
system will never enter suspend.
Revert this commit to avoid this issue, till the slimbus suspend
mechanism is fixed.
Change-Id: I4236f4b6272d0bccaf8a2d6f7d5435caf044bd59
Signed-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>
Current handler acknowledges interrupt in both the irq handler
and the irq thread. This clears interrupts that come between the
irq handler and the irq thread. This patch reorganizes irq
acknowledgment to the irq handler and changes the irq thread to
also check for completed requests by comparing request timestamp
and hardware completion timestamp. Upon error or timeout event,
hardware status is dumped to aid irq related fault isolation.
CRs-Fixed: 1044128
Change-Id: I085c2c2ec55106a8fb196f3ef1cfcb42e2b2507c
Signed-off-by: Alan Kwong <akwong@codeaurora.org>
qseecom still need to free ion memory if unload app failed.
The previous xpu violation related to unload app failure is
actually due to race condition between send command, which
is fixed and now it is safe to free ion memory in error cases.
Change-Id: I7a09c753360eb015ece15c48ae1bb34e30479560
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
When continuous splash screen feature is enabled, the display
needs to be kept alive during the kernel boot up. Add proxy vote
for MDSS GDSC to prevent it from being turned off until the display
driver hand off can be executed.
CRs-Fixed: 1037857
Change-Id: Ie111c5d4fb401a04620809b84ba6a7c2e7d1ce88
Signed-off-by: Aravind Venkateswaran <aravindh@codeaurora.org>
Reserve memory for the display framebuffer in HLOS for continuous
splash feature on msmcobalt target. This memory buffer would be
configured by the bootloader and needs to be retained until the
first frame update in kernel.
CRs-Fixed: 1037857
Change-Id: Ifbcc1454a1c85eb0163fed969a0c8ceb21d23245
Signed-off-by: Aravind Venkateswaran <aravindh@codeaurora.org>
Add META10 fourcc format in the header.
10 bit meta format is needed to distinguish from regular
meta format which is 8-bit.
CRs-Fixed: 1041251
Change-Id: I9014831c92a6ba16450f48d7f6eb831e47b5e0ab
Signed-off-by: Rajesh Bondugula <rajeshb@codeaurora.org>
There are several ways that the parallel charger can be enabled, and
disabled. Currently charging is enabled by default, but the hardware has
the option to disable the parallel charger via the CHG_EN pin on the
parallel charger. The parallel charger driver controls when the
parallel charger is enabled via the input suspend bit.
To better understand the state of the parallel charger add two power
supply properties to the parallel power supply:
CHARGING_ENABLED - Reflects whether the parallel charger is
enabled by any source.
PIN_ENABLED - Reflects whether hardware has voted to enable
the parallel charger.
Change-Id: I725245178ab02c5ec39b89998f5c2ca3d494c8ee
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
Hardware disables the parallel charger via the CHG_EN pin. Add a new
property called PIN_ENABLED which reflects the status of the CHG_EN pin.
Change-Id: I79f95b145176b66d6b8cec5a21922ea16c2c8206
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
Add support to read charger and skin temp hot and
too hot temperature threshold values programmed
during initialization.
Change-Id: I46dca1f606b5414bf7a032c18c9684ba2e53cf28
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The final temperature values for PMI die temperature and
charger temperature are in units of millidegC. Update
the slope factor value to avoid losing resolution
accuracy while values are reported in units of millidegC.
Change-Id: Iec4aa730fa97133af0c0fb9d47557738ef6f45a0
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
When clients wants to send QP map to HW video encoder,
they send through override extradata. This change adds
support for the same.
CRs-Fixed: 957844, 1025326
Change-Id: I25f9cc95bd50a37a4280eecb84bf93d2516d3dc2
Signed-off-by: Praneeth Paladugu <ppaladug@codeaurora.org>
Signed-off-by: Amit Shekhar <ashekhar@codeaurora.org>
Currently there are no channel specific properties associated
with the RRADC channels. The existing channel nodes specify
a logical channel number that is used by the client when
requesting the RRADC channel read. This can instead be obtained
from the channel list specified within the driver. Therefore
remove the channel nodes.
Change-Id: I4da81a576b88285cedb0a1c7fd49ccd526d25012
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
A check is needed to ensure the LSB and MSB are coherent
when reading the result registers for the RRADC channels.
The driver performs another round of read request and
compares the result registers to ensure the data read
back is coherent.
Since there are no channel specific properties remove
the dependency to add the channel nodes in the device
tree and instead statically register the channels within
the driver.
Update the scaling functions to report in the units
desired for the final scaled value based on the channel.
The resistance channel reports the units for batt_id
in ohms, the voltage channels such as DCIN, USBIN report
the value in units of microvolts, the current channels
in units of microamps and the temperature channels
such as thermistors are reported in units of millidegC.
Change-Id: I56e6bff28be2cc23f00622d5c37e42564c51a72f
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
Change the default IPC logging messages to help log analysis instead of
having to change log mask levels and having to re-run the test cases.
Currently single log is used to gather all the driver messages. Split
these into dedicated tx/rx payload log, client ioctl/power state log and
generic driver state log.
Also only dump 32 bytes of the tx/rx payload.
Change-Id: I8dee2f8aa0a6882ec1c320669f165e7cb94bb5f1
Signed-off-by: Girish Mahadevan <girishm@codeaurora.org>
Don't modify the ref count variable clk count inside the runtime callbacks.
Doing so could result in a case where the driver might end up calling a put
twice on the runtime object. The resulting imbalance will leave the runtime
state for the device in a bad state.
Change-Id: I34989768811b23762c4afe3e33e229ffa3f1db17
Signed-off-by: Girish Mahadevan <girishm@codeaurora.org>
As part of the resource voting, both the resource_vote and unvote
functions call the toggle_wakeup_interrupt() function which toggles the
state of the wakeup irq unconditionally. This can cause issues in adverse
scenarios. Instead split this out into exclusive enable and disable wakeup
interrupt functions to be called during the resource unvote and vote
respectively. Also don't make resource votes in the wakeup isr, the
wakeup isr injects a pre-determined byte into the tty flip buffer and
doesn't access the core or setup any transactions and hence doesn't need
to vote for resources.
The driver has registered for the noirq system suspend/resume callbacks.
When executing these callbacks, don't rely on the runtime framework to
check the device's current runtime state before deciding whether to allow
system suspend or not as the runtime framework is disabled at this point.
Instead rely on the power state that the driver maintains internally.
Change-Id: I0e5d6b8a8a69efc2d9c65dc1edc85f13cbc94fc3
Signed-off-by: Girish Mahadevan <girishm@codeaurora.org>
Modify the sleep set GPIO bias for UART_3. This will help lower leakage
once the usecase for UART_3 has ended.
Change-Id: I50d918197a4cd0b503dff78e7d4ba89518c1d1c2
Signed-off-by: Girish Mahadevan <girishm@codeaurora.org>
Modify the sleep set GPIO bias for I2C_5. This will help lower leakage once
the usecase for I2C_5 has ended.
Change-Id: I41e9012210ce9a5f4fbeb4236365c0fa2db08625
Signed-off-by: Girish Mahadevan <girishm@codeaurora.org>
Enable display driver xlog debugging feature.
This feature enables MDSS registers dump during
display driver errors, panic during fatal errors and
logging of events in some key functions.
Events are light weighted, logged in an internal
ring buffer and buffer is only dumped during errors.
CRs-Fixed: 1048182
Change-Id: I2da2eba03ef30f3942ba3f8644efab98635002da
Signed-off-by: Ingrid Gallardo <ingridg@codeaurora.org>
There is no need for sync_sched() in _cpu_down as stop_machine()
provides that barrier implicitly. Removing it also helps improve
hot-unplug latency.
The sync_sched/rcu were earlier removed for the same reason by the
commit 9ee349ad6d ("sched: Fix set_cpu_active() in cpu_down()"),
but recently got added as part of commit <6acce3ef84520537> ("sched:
Remove get_online_cpus() usage.").
CRs-Fixed: 1048941
Change-Id: I97763004454d082d3cc2d9d9dbef7da923608600
Signed-off-by: Kaushal Kumar <kaushalk@codeaurora.org>
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
The core and peripheral memory retention bits no longer need to be
set and cleared by the GDSC driver on MSMCOBALT. Instead, the video
and camera client drivers will use the clk_set_flags API to toggle
these bits as needed.
Change-Id: Ia10ff063d8dc7b52a52e0ff22a2b0a46cc171eb5
CRs-Fixed: 1044274
Signed-off-by: Deepak Katragadda <dkatraga@codeaurora.org>
change to use SW AEAD and HMAC algorithms with ARMv8 crypto
extensions by default on msmcobalt, as they have better performances
than algorithms using HW crypto engines.
Change-Id: If68b68374bfabcdef7ecbf245b72b12c4734f811
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
Adding DFPS support for nt35597 dualmipi wqxga video mode panel based on
vertical porch adjustment.
CRs-Fixed: 1047142
Change-Id: Ida3a175d2d1d9d4c2b5bed1e9998dc1af4f626d0
Signed-off-by: Benjamin Chan <bkchan@codeaurora.org>
Adding support for dynamic FPS adjustment in mdss 3.x. Adjustment
is based on front/back porch changes.
CRs-Fixed: 1047142
Change-Id: Ie4ab889a7d64ba8e33675ee22bf7b808d9ba0a3f
Signed-off-by: Benjamin Chan <bkchan@codeaurora.org>
For USB 2.0 there is a requirement to not to flush the
USB endpoints after the pipes are disconnected. Otherwise
this can result into NOC errors. Make a change to modify the
disconnect sequence as below.
1) USB driver first disable the pipes
2) New API is provided from IPA to disable the endpoint.
3) As part of disable, make sure pipes are empty and reset
the pipes.
4) USB resets its BAM and flushes the ep.
5) USB then disconnects both IPA and USB pipes.
Change-Id: I917f025678e6abb03058d5be4ec42d9e6d76835f
CRs-Fixed: 1038623
Acked-by: Chaitanya Pratapa <cpratapa@qti.qualcomm.com>
Acked-by: Mohammed Javid <mjavid@qti.qualcomm.com>
Signed-off-by: Utkarsh Saxena <usaxena@codeaurora.org>
During IPA driver processing context delete, a delete to
the referenced header is being done. The header deletion
will also commit the changes to H/W which includes the
processing context commit. This resulted into committing
an invalid process context as it is still in the processing
context list, but points to deleted header.
The fix is to not commit the changes when deleting the header
but only when deleting the processing context.
Change-Id: I9d3c5eec717da0b072144a1027e4582e73aaa6d9
CRs-fixed: 1044710
Signed-off-by: Ghanim Fodi <gfodi@codeaurora.org>
The array index value when setting/getting the channels
of proxy is incorrect as the channel count begins from two.
Fix by setting the correct index offset.
Change-Id: I3ab9858daf6dcdbce762946cbdebeb96eaad764a
Signed-off-by: Shiv Maliyappanahalli <smaliyap@codeaurora.org>
