Following flags are needed to support block crypto
based inline encryption framework on EMCC devices:
1. CONFIG_MMC_CQHCI_CRYPTO.
2. CONFIG_MMC_CQHCI_CRYPTO_QTI.
Test:
1. Device booted upto UI with File Based Encryption enabled.
2. Key insertion using fscryptctl tool.
3. Created new files under /data and checked retention across
multiple re-boots.
4. vts_kernel_encryption_test tests.
5. check_encryption test for verifying metadata encryption.
Change-Id: I574838b0e65e336d2c056ab7cfce8c9cd3e801e0
Signed-off-by: Vaibhav Agrawal <vagrawa@codeaurora.org>
store eth_ready_info pointer for late callback
trigger instead of storing cb and user data addresses.
eth_ready_info pointer is static and shall be searched
when callback is unregistered.
Change-Id: I03cbbc4920ee663890bad12ece6d41e9bd2a68d5
Signed-off-by: Amir Levy <alevy@codeaurora.org>
On A660 GPU, PWR_COL_PREEMPT_KEEPALIVE register is used to disallow
ifpc during preemption trigger. Dump this register also in case of
wait for lowest idle timeout to capture this ifpc abort reason.
Change-Id: Ide6bef3169987f17ec6a761e9735caef1c5deaa7
Signed-off-by: Deepak Kumar <dkumar@codeaurora.org>
Jann spotted the security hole due to race of mm ownership check.
If the task is sharing the mm_struct but goes through execve() before
mm_access(), it could skip process_madvise_behavior_valid check. That
makes *any advice hint* to reach into the remote process.
This patch removes the mm ownership check. With it, it will lose the
ability that local process could give *any* advice hint with vector
interface for some reason (e.g., performance). Since there is no
concrete example in upstream yet, it would be better to remove the
abiliity at this moment and need to review when such new advice comes
up.
Change-Id: I536de5167b6cf7378a06a6b7815f1dd2869a56a4
Fixes: ecb8ac8b1f14 ("mm/madvise: introduce process_madvise() syscall: an external memory hinting API")
Reported-by: Jann Horn <jannh@google.com>
Suggested-by: Jann Horn <jannh@google.com>
Signed-off-by: Minchan Kim <minchan@kernel.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Git-Commit: a68a0262abdaa251e12c53715f48e698a18ef402
Git-Repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
- This change will add sfe support for the target
Change-Id: I0088f2d64fbf2ebb10435138edcca0eb9ddb0f4b
Signed-off-by: Aman Gupta <amangupt@codeaurora.org>
Qmuxd bridge daemon is opening /dev/gps before USB enumerated with
USB composition having GPS interface as part of it. This daemon
performs EP_LOOKUP ioctl and encounters failure. It keeps retrying
for some iterations, and later goes into sleep and doesn't perform
any IOs. This results into no GPS related IOs between daemon and
host side QMUXD driver. Hence this change sends zero length packet
for MBIM (as QBI also faces same issue) and GPS interface when
USB cable is connected and those interfaces are part of USB
composition. Both QBI and Qmuxd bridge daemon are now wait for zero
length packet as indication for change in USB cable status, and
queries using GSI_MBIM_GPS_USB_STATUS IOCTL (newly added). Based on
this IOCTL related response, both daemons performs read/write with
created control devices.
Change-Id: Ib47443fe0e473ab4e27facb3f2927b8c13966158
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
gps usb functionality is implemented using qmi packets.
User space entity sends and receives QMI packets using
misc device named /dev/gps.
Change-Id: I73af1caa9b272597909199022739390274a4b034
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Signed-off-by: Elson Roy Serrao <eserrao@codeaurora.org>
If emergency system shutdown is called, like by thermal shutdown,
dm device could be alive when the block device couldn't process
I/O requests anymore. In this status, the handling of I/O errors
by new dm I/O requests or by those already in-flight can lead to
a verity corruption state, which is misjudgment.
So, skip verity work for I/O error when system is shutting down.
Change-Id: I7b2e79283bb5810cefe688bf43b9ae97030ce917
Reviewed-by: Sami Tolvanen <samitolvanen@google.com>
Signed-off-by: Hyeongseok Kim <hyeongseok@gmail.com>
Patch-mainline: dm-devel @ 12/03/20, 00:46
Signed-off-by: Ravi Kumar Siddojigari <rsiddoji@codeaurora.org>
This reverts commit b649934e08.
Based on the upstream review comments its not advised to
ignore the block error and continue so reverting this .
Change-Id: Icf18bd5bdba96b396eee3ddff7e6d39a9bed5816
Signed-off-by: Ravi Kumar Siddojigari <rsiddoji@codeaurora.org>
This change enables novatek nt36xxx config for holi target.
Change-Id: I11842aae692dd9294c314e0a7fddb1c9cf63942b
Signed-off-by: Ravikanth Tuniki <rtunik@codeaurora.org>
Cleanup the clock ID's of GPU and Video clock controllers that are
not required to be controlled from HLOS.
Change-Id: I0d5b67ddbf3f080c70ed0a1a743f3bf7afef240f
Signed-off-by: Jagadeesh Kona <jkona@codeaurora.org>
Pull the RFR line before doing stop_rx in uart driver.
This is to prevent any rx data to come into the uart rx fifo when
stop_rx is being executed.
Remove the rx length zero check in
handling dma rx to prevent race conditions with EOT and DMA_DONE
interrupt bits.
Issue scenarios could be that during baud rate change/ runtime
suspend or any other place where stop_rx is used, there might
be a race between rx data entering uart rx fifo and availability
of dma buffers in uart driver. In this scenarios there will
be interrupt storm with rx water mark interrupt.
Change-Id: I92163c4997c1709269dce67a1d492533f710abfb
Signed-off-by: Prudhvi Yarlagadda <pyarlaga@codeaurora.org>
Add snapshot of the smb358 charger as of msm-4.14
commit 790f0644f00c ("net: stmmac: Alert QTI on SDX
of host AP's SSR status"). Fix minor static analysis
tool errors.
Change-Id: I7c88f48a90cfca6c22ac4ed5289f78a32e524dc4
Signed-off-by: Kavya Nunna <knunna@codeaurora.org>
When calculating play length for FIFO play, it is out of bound
of the FIFO samples array. Fix it.
Change-Id: I8ad458802a0070f493ac53160ab90a6cf648d9e7
Signed-off-by: Fenglin Wu <fenglinw@codeaurora.org>
Add novatek chip id and firmware during boot up to
enable touch.
Change-Id: I382ae51c7bb4bf270c2e01b484281fcc24270062
Signed-off-by: Ravikanth Tuniki <rtunik@codeaurora.org>
Update phy revision information before calling phy_init(),
so that phy driver can perform revision specific configurations.
Change-Id: I834306851e30a203705ad824fc142813b989abc5
Signed-off-by: Veera Vegivada <vvegivad@codeaurora.org>
Enable MFD SPMI PMIC driver and several SPMI and PMIC drivers
which are needed to provide baseline support of PMIC peripherals.
Change-Id: Ic0b24c62bec654c61bbf0034c20d775d686eb9c4
Signed-off-by: Veera Vegivada <vvegivad@codeaurora.org>
Add support for UFS controller and add support for
QTI inline encryption.
Change-Id: I680c75448c0fd9b2e6c37d106075c1a39213abac
Signed-off-by: Veera Vegivada <vvegivad@codeaurora.org>
Enable interconnect L3 driver so that consumer can vote
for L3 performance points.
Change-Id: Id0ff3e976976a05fa6ff47c7ccb9e1a3a3aed2e3
Signed-off-by: Veera Vegivada <vvegivad@codeaurora.org>
