Kernel 8.9
Revert "msm: vidc: Send resolution along with output buffer"

This reverts commit 07962ad68350a92fa532c14addf5a533d5ed80bb.

Change-Id: Ia5ff34180d8c7e4aa9af40bed6e54c9c8e7c9ad1
Config: Enable CONFIG_NETFILTER_XT_TARGET_IDLETIMER
msm: vidc: Change inline functions to function macros

Stripped out kernel headers remove the function definitions
so changing these functions to macros.

Change-Id: I550157301b92855eaf2fbb92bcba050f84fe0b95
Signed-off-by: Vinay Kalia <vkalia@codeaurora.org>
Signed-off-by: Praveen Chavan <pchavan@codeaurora.org>
Config: DISABLE CONFIG_IP_MULTICAST
NET: fix net/ipv4/ping.c as with main line. was mess.
CONFIG: Cleanup.
FORCE FAST CHARGE: 2.4 removed 2000 and 1800ma limits. we cant use them.

LG G2 stock charger code allow max 1600ma, i dont want to change that.
so remove not working limits.
ASoC: msm: extend proxy port period count and size range

Allow more choices in proxy port period size and count
for use by telephony use cases

Change-Id: I6a2eff1c180188f969d7177898f9ec3e5bc178ec
Signed-off-by: Eric Laurent <elaurent@google.com>
msm: mdss: unmap user writeback buffers after session is terminated

Currently if buffers are provided to writeback driver through user space
ioctl, these are never unmapped and may cause leaks in memory. Also, we
can reuse the nodes which are already mapped until session is
terminated.

Change-Id: Ic786dfa735af529998bfc9467ac872b2badc0e31
Signed-off-by: Adrian Salido-Moreno <adrianm@codeaurora.org>
Signed-off-by: Iliyan Malchev <malchev@google.com>
msm: mdss: fix wb memory registration optimization

In order to avoid multiple mappings of same buffer handle, we check for
any existing handles that are already mapped within writeback. However
current checks are based on file descriptors, and these may be reused
for a new buffer handle, and in turn we end up having wrong assumptions
of the actual queued buffer while performing the writeback commit.

Fix this by getting the actual ion handle mapped to the file descriptor
and look for this handle instead.

Change-Id: Ib800dc4000ce8353ed16c7e779cda21644696ec8
Signed-off-by: Adrian Salido-Moreno <adrianm@codeaurora.org>
mm: Increase number of GFP masks

The __GFP_CMA mask is now placed after all available GFP masks.
With this we need to increase the total number of GFP flags.
Do so accordingly.

Bug: 17626969
CRs-Fixed: 648978
Change-Id: I53f5f064ac16a50ee10c84ff2bb50fdb7e085bd0
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Signed-off-by: Naveen Ramaraj <nramaraj@codeaurora.org>
msm: mdss: Change the writeback format enumerations

The enumerations used for writeback format through metadata set
and get ioctls should be the same in HAL and kernel.

Change-Id: I5fb7f9266d01c3ba4390a5a6bb168af507e3c298
Signed-off-by: Sree Sesha Aravind Vadrevu <svadrevu@codeaurora.org>
Merge Stock D801 20g source from LG. only what changed.
MSM_RQ_STATS: Clean the driver from mess, and unused function.
Staging: android: binder: Ratelimit binder debug messages

Ratelimit the binder debug messages, since they can get spammy and
flood the entire kernel log.

In some cases, enabling serial console with a spammy binder error can
cause a watchdog panic (and we don't have reports of this happening
with serial console disabled).

Signed-off-by: Chris Fries <cfries@motorola.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
nl80211: add scan width to bss and scan request structs

To allow scanning and working with 5 MHz and 10 MHz BSS, extend the
inform bss commands and add wrappers to take 5 and 10 MHz bss into
account.

Signed-off-by: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Signed-off-by: Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: Chet Lanctot <clanctot@codeaurora.org>
Signed-off-by: Amarnath Hullur Subramanyam <amarnath@codeaurora.org>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
cfg80211: clarify BSS probe response vs. beacon data

There are a few possible cases of where BSS data came from:
 1) only a beacon has been received
 2) only a probe response has been received
 3) the driver didn't report what it received (this happens when
    using cfg80211_inform_bss[_width]())
 4) both probe response and beacon data has been received

Unfortunately, in the userspace API, a few things weren't there:
 a) there was no way to differentiate cases 1) and 4) above
    without comparing the data of the IEs
 b) the TSF was always from the last frame, instead of being
    exposed for beacon/probe response separately like IEs

Fix this by
   i) exporting a new flag attribute that indicates whether or
      not probe response data has been received - this addresses (a)
  ii) exporting a BEACON_TSF attribute that holds the beacon's TSF
      if a beacon has been received
 iii) not exporting the beacon attributes in case (3) above as that
      would just lead userspace into thinking the data actually came
      from a beacon when that isn't clear

To implement this, track inside the IEs struct whether or not it
(definitely) came from a beacon.

Reported-by: William Seto
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Chet Lanctot <clanctot@codeaurora.org>
[amarnath@codeaurora.org: Only picked up the change in nl80211.h for the user
 space code to remain same. Other changes are not applicable for this version
 of the kernel]
Signed-off-by: Amarnath Hullur Subramanyam <amarnath@codeaurora.org>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
msm: usbaudio: remove usbaudiosdev switch

- Remove usbaudiosdev switch to avoid reporting
  analog dock headset for USB headset

Signed-off-by: Divya Narayanan Poojary <dnaray@codeaurora.org>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
ASoC: wcd9320: fix the no audio issue on triggering SSR

After the SSR is triggered there is possibility of the  mismatch
among  the cache register values and the actual hardware registers
values. Due to this some of the registers doesn't gets updated when
the enable sequence is triggered. This results incomplete path
getting enabled resulting in no audio.
Fix by updating the registers to the reset state and updating the
cache also. Also restart the mbhc for the proper headset detection

Signed-off-by: Aviral Gupta <aviralg@codeaurora.org>
Signed-off-by: Divya Narayanan Poojary <dnaray@codeaurora.org>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>