Add SOC_REPORTING_READY property which indicates when the SOC
reporting is ready from FG driver. This can be read by healthd
daemon during its start.
Change-Id: I415e322e99bacd61c4e9ac921643d87d3eec4b3e
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Add SOC_REORTING_READY property to indicate if the SOC is ready
to be reported.
Change-Id: I53ac153ba9f7ae81bb0657b17e0e798fd3fe4f48
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Abort any read() operation to unlock the channel mutex.
On channel remote-disconnect notification, the local side should close
the channel.
However, open()/close()/read()/write() operations locks the channel mutex.
The glink rx-abort notification happens only after the remote-disconnect
notification, not as originally expected.
Change-Id: I77f8e6de6f1b5c447a3516380c51db9c7129d2f3
Signed-off-by: Amir Samuelov <amirs@codeaurora.org>
This patch enables allocation of 5MB for new diag client
of memshare.
CRs-Fixed: 1100632
Change-Id: Iab69062336966e61683117a17974f46cd8f513aa
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
Remove the additional unbalanced unlock being called for the
link training mutex. This fixes random crashes seen while
running Display Port connection/disconnection tests.
Change-Id: I2fce80cec72e3bd8b1561fd46fa1a1520cddd294
Signed-off-by: Aravind Venkateswaran <aravindh@codeaurora.org>
If the calculated link rate based on sink's capabilities exceeds
the maximum supported link rate, do not error out. Instead, cap
the link rate at the maximum supported rate. This fixes instability
issues seen when connecting to sinks at 4K resolution.
Change-Id: I214bb19385f855af61da628fdf1cf7efc5dd08d6
Signed-off-by: Aravind Venkateswaran <aravindh@codeaurora.org>
Add support for PHY compliance tests by parsing requests
from the reference sink and generating the requested
PHY test patterns from DP PHY.
CRs-Fixed: 1076516
Change-Id: I290ec786bbe5c45873265ea74290eefcd3d16cb1
Signed-off-by: Tatenda Chipeperekwa <tatendac@codeaurora.org>
When device enters suspend, the suspend framework disables CPU hotplug
functionality. During the suspend, any attempt from KTM to hotplug CPU
will return error and in this case, KTM wont clear the cpus_offlined
mask. In this case, the device framework assumes the core is still
online. Next time the device resumes from suspend the core
online attempt will be nacked by KTM. Thus the core will be offlined and
subsequent attempts to bring the core online using device framework will
fail.
Update KTM error handling to remove the CPUs from the cpus_offlined
mask, when device offline APIs return error. Thus KTM wont block suspend
framework from bringing the core online. Also, update KTM not to
evaluate new request to offline or online a core when the device is in
suspend entry or exit. The re-evaluation will be triggered when the
device exits suspend.
Change-Id: I334fd782a2c5d604cafb94f44832d9c700891ba2
Signed-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>
