* refs/heads/tmp-dc2d5a0:
ANDROID: ABI: Update allowed list for QCOM
ANDROID: ABI: Update allowed list for QCOM
ANDROID: modules: cfi cleanup for module load failure
ANDROID: Temporarily disable XFRM_USER_COMPAT filtering
ANDROID: ABI: Update allowed list for QCOM
ANDROID: ABI: update allowed list for QCOM
ANDROID: fix kernelci build-break due to stop_ipi hook
BACKPORT: rcu/tree: Export rcu_idle_{enter,exit} to modules
ANDROID: GKI: Add some symbols to symbol list
ANDROID: arm64: smp: fix Lockdep warning: RCU used illegally from idle CPU.
ANDROID: Fix build-break caused by android_rvh_nf_conn_alloc hook
ANDROID: GKI: Enable DEBUG_INFO_DWARF4
ANDROID: cfi: ensure RCU is watching in __cfi_slowpath
UPSTREAM: mm/sl[uo]b: export __kmalloc_track(_node)_caller
BACKPORT: xfrm/compat: Translate 32-bit user_policy from sockptr
UPSTREAM: xfrm/compat: Add 32=>64-bit messages translator
UPSTREAM: xfrm/compat: Attach xfrm dumps to 64=>32 bit translator
UPSTREAM: xfrm/compat: Add 64=>32-bit messages translator
BACKPORT: xfrm: Provide API to register translator module
ANDROID: ABI: update allowed list for galaxy
ANDROID: Update the KMI_GENERATION after KMI changes on October 31
ANDROID: Input: bump SW_MAX up to 0x3f
ANDROID: GKI: ABI update for Oct 31 KABI break
ANDROID: GKI: add Android ABI padding to struct nf_conn
ANDROID: GKI: add vendor padding variable in struct skb_shared_info
ANDROID: GKI: net: add vendor hooks for 'struct nf_conn' lifecycle
ANDROID: GKI: add vendor padding variable in struct nf_conn
ANDROID: GKI: net: add vendor hooks for 'struct sock' lifecycle
ANDROID: GKI: add vendor padding variable in struct sock
ANDROID: fuse: Add support for d_canonical_path
ANDROID: vfs: add d_canonical_path for stacked filesystem support
ANDROID: fscrypt: prevent fscrypt_operations from affecting KMI
Revert "ANDROID: GKI: fix ABI breakage in module.h"
ANDROID: ABI: update allowed list for galaxy
FROMLIST: char: misc: increase DYNAMIC_MINORS value
Conflicts:
net/netfilter/nf_conntrack_core.c
Change-Id: I0687237ba5f07f291a5f3b49ee2057071fcb2717
Signed-off-by: Blagovest Kolenichev <bkolenichev@codeaurora.org>
After reclaiming vmalloc and adjusting lowmem, the two
regions are no longer contiguous. Update the messages
printed during bootup to list all regions corresponding
to low memory and vmalloc respectively.
Change-Id: Ib3e25b530b3dfbd1f9796cdc580fb79da484e850
Signed-off-by: Susheel Khiani <skhiani@codeaurora.org>
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
Signed-off-by: Qingqing Zhou <qqzhou@codeaurora.org>
This size is the maximum amount of virtual address space we gather
up before attempting to purge with a TLB flush. It is 128M in most cases.
With repeated and high size vmalloc operations, it may easily generate
more fragments. This is wasting limited vmalloc area, for 32bits.
So make it configable and the default multiplier as 8, 32bits only.
Change-Id: I68a75acb16d3cff05f8b13c05ae78922269e219f
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
When the CONFIG_ENABLE_VMALLOC_SAVING is enabled, even though
the unused lowmem is used as vmalloc space, but __vmalloc_node()
still uses VMALLOC_START as the start point to allocate vm area,
but the range [VMALLOC_START, VMALLOC_END] is limited, this
may cause vmalloc allocation failure. Change the start point
to allocate the vm area from VMALLOC_START to PAGE_OFFSET to make
that allocation can be chosen from [PAGE_OFFSET, VMALLOC_START)
also.
Change-Id: I89c099484846c4bcd9b607c1925f253c165d0dd9
Signed-off-by: Qingqing Zhou <qqzhou@codeaurora.org>
Even though lowmem is accounted for in vmalloc space,
allocation comes only from the region bounded by
VMALLOC_START and VMALLOC_END. The kernel virtual area
can now allocate from any unmapped region starting
from PAGE_OFFSET.
Change-Id: I291b9eb443d3f7445fd979bd7b09e9241ff22ba3
Signed-off-by: Neeti Desai <neetid@codeaurora.org>
Signed-off-by: Susheel Khiani <skhiani@codeaurora.org>
For some targets that have less vmalloc space this can be increased by
enabling config ENABLE_VMALLOC_SAVING. With this config we can reclaim
virtual mappings which remains unused because of non hlos carveout
reservations in lowmem.
Select the default method of reclaiming virtual memory as vmalloc
saving.
Change-Id: I249992871babe8c64c34d52ef43bbc7c81636d47
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
Signed-off-by: Qingqing Zhou <qqzhou@codeaurora.org>
is_vmalloc_addr currently assumes that all vmalloc addresses
exist between VMALLOC_START and VMALLOC_END. This may not be
the case when interleaving vmalloc and lowmem. Update the
is_vmalloc_addr to properly check for this.
Correspondingly we need to ensure that VMALLOC_TOTAL accounts
for all the vmalloc regions when CONFIG_ENABLE_VMALLOC_SAVING
is enabled.
Change-Id: I5def3d6ae1a4de59ea36f095b8c73649a37b1f36
Signed-off-by: Susheel Khiani <skhiani@codeaurora.org>
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
Signed-off-by: Qingqing Zhou <qqzhou@codeaurora.org>
Signed-off-by: Sudarshan Rajagopalan <sudaraja@codeaurora.org>
Currently on 32 bit systems, virtual space above
PAGE_OFFSET is reserved for direct mapped lowmem
and part of virtual address space is reserved for
vmalloc. We want to optimize such as to have as
much direct mapped memory as possible since there is
penalty for mapping/unmapping highmem. Now, we may
have an image that is expected to have a lifetime of
the entire system and is reserved in physical region
that would be part of direct mapped lowmem. The
physical memory which is thus reserved is never used
by Linux. This means that even though the system is
not actually accessing the virtual memory
corresponding to the reserved physical memory, we
are still losing that portion of direct mapped lowmem
space.
So by allowing lowmem to be non contiguous we can
give this unused virtual address space of reserved
region back for use in vmalloc.
Change-Id: I980b3dfafac71884dcdcb8cd2e4a6363cde5746a
Signed-off-by: Susheel Khiani <skhiani@codeaurora.org>
Signed-off-by: Qingqing Zhou <qqzhou@codeaurora.org>
Enable the config ENABLE_VMALLOC_SAVING only when QGKI
config is enabled.
Change-Id: Ic688d27bb31702a60be72b22033cfe1eed5efadc
Signed-off-by: Sudarshan Rajagopalan <sudaraja@codeaurora.org>
Update Galaxy list of symbols with ones that are already in the .xml
file to manage symbols by used our modules
Bug: 173174399
Signed-off-by: Jeehong Kim <jhez.kim@samsung.com>
Change-Id: I0b26dff0c0075ba74fbbb3948f4e71c636f3a6cb
Add support for 5nm DSI PLL C-PHY shadow clocks, which
will be used during dynamic dsi clock switch.
Change-Id: I6aed40f7347b5a098c6c7f4d160d5456424a3507
Signed-off-by: Satya Rama Aditya Pinapala <psraditya30@codeaurora.org>
Sanitize the ring buffer length read from the other side to ensure
the bounds match the memory that is mapped.
Change-Id: Ifdac3e0dee11374e61ede3a2cfb82e1957c6a2b2
Signed-off-by: Chris Lew <clew@codeaurora.org>
There are some control packets such as DEL_CLIENT that will not always
match the local node address. All packets addressed to the control port
should be decoded as qrtr control packets.
Change-Id: I46b366c77fd2d8defc203e0c74181a228710c48e
Signed-off-by: Chris Lew <clew@codeaurora.org>
Consider a scenario where a peripheral connected to the host gets
runtime suspended because of no bus activity. When the device tries
to enter suspend/deep sleep from this state and if it fails to suspend
PM framework calls pm_resume of the suspended device. Currently
xhci_plat_resume will call xhci_resume but it will fail since the parent
(dwc3) is not resumed.
Fix this by resuming glue driver and core by performing pm_runtime_resume
on xhci-plat device.
Change-Id: I71349fa88bce65fa9ec9bceb7c42ef79db763a84
Signed-off-by: Pratham Pratap <prathampratap@codeaurora.org>
This patch adds to upload initial symbol list for Exynosauto SoC.
To find what has updated from GKI symbol easily, this list does not
include full list of symbol. So, nothing has added to GKI ABI symbols.
Bug: 172885440
Signed-off-by: Chanho Park <chanho61.park@samsung.com>
Change-Id: I41cc355687a5ba859ad601b8f1efdad13e52f20f
With use of sync suspend, driver is going to suspend
in atomic context which is not permitted and leading to
below below stack.
pc : __schedule_bug
lr : __schedule_bug
Call trace:
__schedule_bug
__schedule
schedule
rpm_suspend
__pm_runtime_suspend
mmc_release_host
mmc_put_card
mmc_blk_cqe_complete_rq
mmc_blk_mq_complete
blk_done_softirq
To avoid this use auto suspend.
Change-Id: Ie19c06ba07c8340faefebbde9810e65dc11ec6b2
Signed-off-by: Ram Prakash Gupta <rampraka@codeaurora.org>
This change removes disable_irq call from
mxt_configure_objects(). Without this change
touch does not work on dual dsi which uses
atmel touch driver.
Change-Id: Ie215c8a08060d56d1f087490bf01f85a202fcb55
Signed-off-by: Harigovindan P <harigovi@codeaurora.org>
Enable dependency on CONFIG_TYPEC so that typec_* APIs used in
smb5-lib.c may be found by the build system.
Change-Id: If70c09cd6ddee799a87868fa8db36611c35a3fb0
Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
When setting target link speed, it is correct to use
PCI_EXP_LNKCTL2_TLS instead of PCI_EXP_LNKCAP_SLS and
PCI_EXP_LNKSTA_CLS. All 3 macros have the same value defined
but it is proper to use the right one.
Change-Id: I5d99a696168170adf8dc577a6bf1fceb4fe82686
Signed-off-by: Tony Truong <truong@codeaurora.org>
Instead of using msm_pcie_write_mask, use msm_pcie_write_reg_field
which will shift the write value based on the mask.
Change-Id: Ie125655776d9ab0091d9ef813e1761126e920549
Signed-off-by: Tony Truong <truong@codeaurora.org>
