The previous patch added the NETIF_F_GRO_FRAGLIST feature.
This is a software feature that should default to off.
Current software features default to on, so add a new
feature set that defaults to off.
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Bug: 167707933
Change-Id: Ie56e82a2b2ba3ebd4fded1d865070ddcd311a26a
(cherry picked from commit 1a3c998f3a27ab6ecf56bdbb17e27e55fd6d47cd)
Signed-off-by: Hyunsoon Kim <h10.kim@samsung.com>
This adds new Fraglist GRO/GSO feature flags. They will be used
to configure fraglist GRO/GSO what will be implemented with some
followup paches.
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Bug: 167707933
Change-Id: I65a4b9fc631c88cd20c1b101fee70e864c2c4502
(cherry picked from commit 3b33583265ed3b0ae76eddbabf9d038b4076d1a9)
[hyunsoon: removed patch in net/ethtool/common.c which is not in android branch]
Signed-off-by: Hyunsoon Kim <h10.kim@samsung.com>
Commit 7d3ecfd796 ("input: qcom-hv-haptics: read CAL_TLRA_CL_STS from
SDAM after boot up") added support for LRA frequency calibration.
However, since bootloader changes needed to support this feature had
caused a regression on devices that has PM8350B v1 PMIC, this got
reverted with commit 844516d943 ("Revert "input: qcom-hv-haptics: read
CAL_TLRA_CL_STS from SDAM after boot up""). Now that the bootloader
changes handles PM8350B v1 configuration properly, re-enable this
change.
During LRA frequency calibration, reading CAL_TLRA_CL_STS has to be
done before de-asserting play. In the boot up LRA frequency calibration
sequence, CAL_TLRA_CL_STS was read out and stored in SDAM module
registers by the bootloader. Later, HLOS haptics driver can read it from
there and use it for calculating LRA frequency. This boot up LRA
frequency calibration sequence is only available for PM8350B 2.0 chip.
Update the driver to support this.
Change-Id: I23532dd2a0a2bced0ba4715e5b58f6f53fec3160
Signed-off-by: Fenglin Wu <fenglinw@codeaurora.org>
This reverts commit 2d5d56df7f.
Upstream reported that other fixes are required after this, and asked
why it is really needed here.
So get those answers first before accepting this patch, as we can not
take known-buggy patches into the tree.
Bug: 167477898
Cc: Hyunsoon Kim <h10.kim@samsung.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: If795972972fdd17ad85a50f460ce79e00baffb54
In case of callback deregistration failure, end further
signaling and memory free for the external sync obj.
Without the change, the memory shared with the external
callback would be released even on deregistration failure,
leading to possible double free, as callback might already
been dispatched.
Change-Id: Ic2e755b0b039a9b7ad2e25abb23949d673bda685
Signed-off-by: Sumukh Hallymysore Ravindra <shallymy@codeaurora.org>
Verbose log out side the write lock is getting preempted by
other irq and incorrectly identified that mhi irq hogging
cpu when the other irq is responsible for that. Remove
verbose logging from mhi threaded irq which is not really
needed.
Change-Id: I1608d64a43600e662de9076642d0097e31b01a46
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Add cnss_smmu_unmap API so that wlan function driver
could unmap IOVA addresses that are IOMMU mapped.
Change-Id: I1e3aa287589f73a609cc51fe8c826d1edf2fefd1
Signed-off-by: Jia Ding <jiad@codeaurora.org>
Add Trusted touch support to lahaina QRD Touchscreen
driver. This feature enables driver to operate in
trusted touch mode in trusted virtual machine(TVM).
The primary virtual machine(PVM) lends resources such
as IO memory and touch irq to TVM prior to trusted touch
is initiated and reclaims those resources back after trusted
touch usecase finishes.The resource requirements of TVM
such as clock, regulators etc are taken care by PVM.
Change-Id: I342a0a19977365ef08ea0c8fc191a2505e6e3984
Signed-off-by: Ritesh Kumar <riteshk@codeaurora.org>
During any sensor threshold notification, the of-thermal framework
checks whether any trip of each thermal zone for that sensor is
violated or not. It requests thermal zone re-evaluation only for
those thermal zones those trip is violated. If trips are violated
for none of thermal zones due to some reason, then of-thermal ignores
that sensor notification and it leads to no active trip threshold
for that sensor forever.
Notify and request thermal zone re-evaluation for at least one thermal
zone for that sensor if trips are violated for none in of-thermal.
It makes sure that for every sensor notification, thermal zone
aggregate and set next active trip.
Change-Id: If9955977fe32929d853815ddb9408385291b3c58
Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
in error handling path, remove qos request only if its active.
Change-Id: I322764ce736b581ecabdd82cece83c3d6595e4c7
Signed-off-by: Kishore Sri venkata Ganesh Bolisetty <bsrivenk@codeaurora.org>
When some problems happened in android, we can't use adb command because
android can be abnormal state. And we can't use uart because
uart pin is not connected in the board. So we need key combination
functions for debugging.
This function should only use in development environment.
In the market, this will be disabled.
Bug: 167516783
Signed-off-by: Changki Kim <changki.kim@samsung.com>
Change-Id: I1cbbc93642fb45da161eee983380e48045153a66
[ Added "#ifdef __GENKSYMS__" around the include <<trace/hooks/debug.h>
to prevent CRC errors due to visibility of struct trace_eval_map ]
Signed-off-by: Todd Kjos <tkjos@google.com>
Wakeup the isolated core for every new PMQoS update so that
we can re-evaluate the core lpm with new updated PMQoS latency
request.
Change-Id: I969ad216ab353f2dbfe4fc54a75000fa0140fce9
Signed-off-by: Raghavendra Kakarla <rkakarla@codeaurora.org>
Currently dma handles are not freed in the RPC call with no parameters.
This will cause fastrpc driver to hold the memory of the dma handle, that
is freed in both DSP and application user space. Free dma handles even
in the RPC call with no parameters.
Change-Id: Ica5bfc98edc07b77f79bfaf75630508b8c9ee1af
Signed-off-by: Himateja Reddy <hmreddy@codeaurora.org>
Make sure that the delayed work invoked in suspend
are completed.
Change-Id: I29df22cdd44590fca3ebf0ecc58d6d88505cc156
Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
This patch switches compiler-based stack initialization from 0xAA
to zero pattern, resulting in much more efficient code and saner
defaults for uninitialized local variables.
Bug: 154198143
Test: run cuttlefish and observe the following lines in dmesg:
test_stackinit: all tests passed!
test_meminit: all 130 tests passed!
Signed-off-by: Alexander Potapenko <glider@google.com>
Change-Id: If9f2047fcbee58b90dbd8ad45707c5b40a654e2d
Upstream commit f0fe00d4972a8cd4b98cc2c29758615e4d51cdfe.
In addition to -ftrivial-auto-var-init=pattern (used by
CONFIG_INIT_STACK_ALL now) Clang also supports zero initialization for
locals enabled by -ftrivial-auto-var-init=zero. The future of this flag
is still being debated (see https://bugs.llvm.org/show_bug.cgi?id=45497).
Right now it is guarded by another flag,
-enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang,
which means it may not be supported by future Clang releases. Another
possible resolution is that -ftrivial-auto-var-init=zero will persist
(as certain users have already started depending on it), but the name
of the guard flag will change.
In the meantime, zero initialization has proven itself as a good
production mitigation measure against uninitialized locals. Unlike pattern
initialization, which has a higher chance of triggering existing bugs,
zero initialization provides safe defaults for strings, pointers, indexes,
and sizes. On the other hand, pattern initialization remains safer for
return values. Chrome OS and Android are moving to using zero
initialization for production builds.
Performance-wise, the difference between pattern and zero initialization
is usually negligible, although the generated code for zero
initialization is more compact.
This patch renames CONFIG_INIT_STACK_ALL to CONFIG_INIT_STACK_ALL_PATTERN
and introduces another config option, CONFIG_INIT_STACK_ALL_ZERO, that
enables zero initialization for locals if the corresponding flags are
supported by Clang.
Cc: Kees Cook <keescook@chromium.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Alexander Potapenko <glider@google.com>
Link: https://lore.kernel.org/r/20200616083435.223038-1-glider@google.com
Reviewed-by: Maciej Żenczykowski <maze@google.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Change-Id: I3c69570e7e3d3bbb666709de6feb531000bce2bf
While system is going down fifo index are not reset which can
cause remote subsystem to read stale index.
Now resetting the index while system is going down.
CRs-Fixed: 2543040
Change-Id: Icb4010c120f4735da206a44a4eb1bcf06ae0a1b7
Signed-off-by: Deepak Kumar Singh <deesin@codeaurora.org>
After touch read is failed, reset touch IC and enable irq
before try to read by I2C once again.
Change-Id: I755ab9e41dcc953665f21df01ea03fe0f89b958d
Signed-off-by: Fei Mao <feim1@codeaurora.org>
Commit 323ebb61e3 ("net: use listified RX for handling GRO_NORMAL
skbs") made use of listified skb processing for the users of
napi_gro_frags().
The same technique can be used in a way more common napi_gro_receive()
to speed up non-merged (GRO_NORMAL) skbs for a wide range of drivers
including gro_cells and mac80211 users.
This slightly changes the return value in cases where skb is being
dropped by the core stack, but it seems to have no impact on related
drivers' functionality.
gro_normal_batch is left untouched as it's very individual for every
single system configuration and might be tuned in manual order to
achieve an optimal performance.
Signed-off-by: Alexander Lobakin <alobakin@dlink.ru>
Acked-by: Edward Cree <ecree@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Bug: 167477898
Change-Id: Ie9e079cf9a5799ca2c4924848ca6b3caeef056d7
(cherry picked from commit 6570bc79c0dfff0f228b7afd2de720fb4e84d61d)
[hyunsoon: fix conflicts in net/core/dev.c]
Signed-off-by: Hyunsoon Kim <h10.kim@samsung.com>
This change is for general scheduler improvement.
Change-Id: I19ec68fe40d931b501ea84a9306d04fcb58db60d
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
This change is for general scheduler improvement.
Change-Id: Id1692f724f2efd22ada3365cebd154f1999930b5
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Make the iommu clocks list dynamic so that we
can add new clocks to the list whenever needed.
Change-Id: I7a742c709d0bdc59d4f578329f7019959d4edb46
Signed-off-by: Nitheesh Muthuraj <nmuthuraj@codeaurora.org>
This change is for general scheduler improvements.
Change-Id: I917955ef029f30db6c185a41f717a89dd179cc49
Signed-off-by: Biao Long <blong@codeaurora.org>
To help with power savings, disable haptics module when the device
enters suspend and enable it when it exits suspend.
Change-Id: I8956be849b876a2b514c1de49f8ff447267d28a1
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Signed-off-by: Fenglin Wu <fenglinw@codeaurora.org>
During clock gating, after clocks are disabled, put hba into LPM to save
more power.
Change-Id: I1d8d76f3b72a2346c9ab6268555b0b416cb3b16f
Signed-off-by: Can Guo <cang@codeaurora.org>
Add a function md_get_region which returns md_region
when we pass minidump entry name to it.
Change-Id: Ibbd84737041c5b1c25cc46b9c740d415978de7e6
Signed-off-by: Vijayanand Jitta <vjitta@codeaurora.org>
Enable CONFIG_QCOM_INITIAL_LOGBUF for lahaina. This enables
copying of dmesg logs into separate buffer at 100 sec from
bootup.
Change-Id: I3ae2e1d5eca1a1eab42aa2161f9c0a7696497998
Signed-off-by: Prateek Sood <prsood@codeaurora.org>
Enable L3 interconnect driver so that consumers are
able to obtain their path handles properly.
Change-Id: I92b407621e6c65563e5e88b63cf6b776329657cb
Signed-off-by: Odelu Kukatla <okukatla@codeaurora.org>
Configure proper sleep state and touch works correctly
when device resume.
Change-Id: I06fc1dfd281cfa297fb8698a5b350aa062d603b2
Signed-off-by: Fei Mao <feim1@codeaurora.org>
Add support for dumping active modules information,
in minidump registered region.
Change-Id: Id8e81ea7beae425a1a0f68f91a8cf9aa093b8011
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>