Clang warns:
../drivers/staging/qcacld-3.0/core/cds/src/cds_regdomain.c:284:43: warning: suspicious concatenation of string literals in an array initialization; did you mean to separate the elements with a comma? [-Wstring-concatenation]
{CTRY_TURKS_AND_CAICOS, FCC3_WORLD, "TC" "TURKS AND CAICOS"},
^
,
../drivers/staging/qcacld-3.0/core/cds/src/cds_regdomain.c:284:38: note: place parentheses around the string literal to silence warning
{CTRY_TURKS_AND_CAICOS, FCC3_WORLD, "TC" "TURKS AND CAICOS"},
^
../drivers/staging/qcacld-3.0/core/cds/src/cds_regdomain.c:296:45: warning: suspicious concatenation of string literals in an array initialization; did you mean to separate the elements with a comma? [-Wstring-concatenation]
{CTRY_WALLIS_AND_FUTUNA, ETSI1_WORLD, "WF" "WALLIS"},
^
,
../drivers/staging/qcacld-3.0/core/cds/src/cds_regdomain.c:296:40: note: place parentheses around the string literal to silence warning
{CTRY_WALLIS_AND_FUTUNA, ETSI1_WORLD, "WF" "WALLIS"},
^
Change-Id: I35bc21e7946f03fc36fb912f46f742ec23cb8d99
qcom_rx_wakelock is one of the major culprit to increased power consumption.
Although its total wakelock time is quite low, it's catched very frequently
and prevents the system from entering suspend repeatedly.
Original intention of this wakelock is to prevent dropping unicast or
local ARP packet, but I'm having a hard time understanding why are those
packets critical to regular Android users.
qcacld's packet filter will still allow notifications to flow in.
Stop allowing this to be configurable on this kernel.
Nuke this entirely to reduce resource usage.
Change-Id: I8ae655b871e58dc1c9a880c831cc6a5e2d118594
* This method of building QCACLD isn't meant to be
used and causes conflicts with the new OEM profile
configuration.
* Configuration is now done with drivers/staging/qcacld-3.0/configs.
Change-Id: I7e9f2ad34c360da587707fa4c2519c48a622af18
* These symlinks were meant for the out-of-tree module. Now that we
build them in-tree, we need to correct them.
Change-Id: If2f506138c7e08123a90e0f897f0e899bb47ef0c
Rename Android.bp to Androidbp. This is done to
avoid compilation failure reported for SA* targets.
Ignore tracking of Android.bp link file.
Change-Id: Ie36f8bf5e0ac011e5f82e4cbd3c2cc7d6bf14070
Signed-off-by: Prateek Sood <prsood@codeaurora.org>
Signed-off-by: Naitik Bharadiya <bharad@codeaurora.org>
* This prevents inclusion of drivers/staging/greybus/tools/Android.mk
which will conflict in case we have more than 1 kernel tree in AOSP
source dir.
Change-Id: I335bca7b6d6463b1ffc673ab5367603347516e13
Panel dead happen randomly because of high panel power consumption,
increase max vddio for r66451 panel to fix panel dead issue.
Change-Id: Ib091cbab6ba4e9e1dd3f8a9ca4b6ad9afc36c174
The display panel timings for Blair QRD need to be updated to match
with latest timing revision to avoid display issues.
Change-Id: I49cd26e2bde2dbc8100580269e06b0e159ecc2ca
When the AMOLED panel is powered from the external power source,
the IBB regulator is not needed. In the absence of ibb regulator
node we are getting error message (non-fatal) for AMOLED panel's
operation on ibb during change in the power states. Using stub
regulator for ibb supply to fix this error. The Blair display DT
includes DT of PM6125 variant of Holi, so this change applies to
both.
Change-Id: I851cef3e6c235b8ee2fa334c45c96caa038262bf
The qcom,mdss-dsi-t-clk-post and qcom,mdss-dsi-t-clk-pre panel
properties are not required for DSI ctrl v2.3.0 and above, using
DSI phy v4.0.0 and above. As the Blair is reusing the display
nodes from the Holi target, these two properties are getting
included automatically.
If these properties are defined, the DSI ctrl programs the
DSI_CLKOUT_TIMING_CTRL register for all the DSI PHY versions,
that is not recommended as per the DSI HPG.
We don't need these two for the Blair, remove them.
Change-Id: Ic4e1a3a306e4aa191cd7cb3b6017cd3b2f226e8e
The qcom,mdss-dsi-t-clk-post and qcom,mdss-dsi-t-clk-pre panel
properties are not required for DSI ctrl v2.3.0 and above, using
DSI phy v4.0.0 and above. As the Blair is reusing the display
nodes from the Holi target, these two properties are getting
included automatically.
If these properties are defined, the DSI ctrl programs the
DSI_CLKOUT_TIMING_CTRL register for all the DSI PHY versions,
that is not recommended as per the DSI HPG.
We don't need these two for the Blair, remove them from Blair
CDP and MTP platforms.
Change-Id: I81d66c53fabfc389466b0dbf82c8d8678f08868a
Enable NT36672E 60/120/144fps D-PHY fhd plus video mode
display panel support for the Blair target.
Change-Id: Ie5e69943f7b7984f4b625372ce91a6555a1f2467
In Blair target, the MX Rail supports till SVSL1 mode whereas
in Holi target it’s Nominal. Change the qcom,supply-min-voltage
of the dsi phy 0p9 power supply to SVSL1.
Change-Id: If6bfe3021f27ce844783b586b42ef0edb7db157f
Add list-cells property for mdp device node. Which is
needed to populate parent device node for rotator device.
Change-Id: I679343160c81f6047cb1a3ff207cd386a0f31580
