F2FS already has a default timeout of 5 secs for discards that
can be issued during umount, but it can take more than the 5 sec
timeout if the underlying UFS device queue is already full and there
are no more available free tags to be used. Fix this by submitting a
small batch of discard requests so that it won't cause the device
queue to be full at any time and thus doesn't incur its wait time
in the umount context.
Change-Id: Ib9669453795601e9e602c204aad31a5cb70688a4
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Git-commit: 141af6ba5216d4d49de683582b600d5c9b51792c
Git-repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/
[stummala@codeaurora.org: Fix trivial merge conflicts]
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
The firmware version which less than 0x40 did not support hpd,
so do not enable hpd for it.
Change-Id: Ic3567b42834fe060e494f859f007e7dc3657e7b7
Signed-off-by: Yuan Zhao <yzhao@codeaurora.org>
If eud driver is enabled in xbl, there was a explicit need
to enable eud from hlos side also. This change enables eud
if eud_mode_manager2 register is set.
Change-Id: I72a8560a7fd8dfa4eaed7895bb423a867ab90e91
Signed-off-by: Komal Bajaj <kbajaj@codeaurora.org>
From ICE 3.0 onwards the keys are used in little endian format
but legacy ICE driver in trustzone reverses the endianness. So reverse
the endianness of keys before passing it to trusted ICE driver.
Change-Id: I5c343054526d43234d5ab1f072a199c6f4203e5a
Signed-off-by: Neeraj Soni <neersoni@codeaurora.org>
Existing api returns failure when requested frequency
is larger than fmax supported. This creates problem to
clients as they consider this as error case. This
can be improved if api returns success when requested
frequency is larger than fmax supported because requested
limit frequency is larger than fmax device will never
go beyond that at all and clients can execute normally.
Change-Id: Id1077ca03019a61d7fd6fef8eccd605131b9c150
Signed-off-by: Pranav Patel <pranavp@codeaurora.org>
Add CONFIG_DM_ANDROID_VERITY_AT_MOST_ONCE_DEFAULT_ENABLED config support,
because this config is needed for go.
Change-Id: Ic6575acbdf09d8380aeb12cbd99b9fde35f4bf5d
Signed-off-by: Tengfei Fan <tengfeif@codeaurora.org>
Add status check in usb_notifier to avoid the exceptions.
Change-Id: I6f9f2fc66c0b26329153783dde2969ef60edc20a
Signed-off-by: Mao Jinlong <jinlmao@codeaurora.org>
It is possible that notify call is called after etr is disabled or
after mode switch from usb to etr. Add etr status check to avoid
exception.
Change-Id: I4feb36df28b6fc059598af98b6fb9ccf698d3aaf
Signed-off-by: Mao Jinlong <jinlmao@codeaurora.org>
Avoid decrementing ICL twice when we are above _UB threshold.
Also, increment back the ICL only when DIE_STATUS is 0 i.e when
we are below the _LB threshold.
Change-Id: I58027cb94500cf93eb42b44dcec9a5e68670b5e1
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
This flag is needed for Metadata encryption to work:
CONFIG_DM_DEFAULT_KEY=y.
Change-Id: Ia1c52c22a0a1c565dde1a827409444cdc4a66769
Signed-off-by: Neeraj Soni <neersoni@codeaurora.org>
Some of the IPC message requires long processing time. If there
are multiple messages in the queue, driver will finish processing
all of them before user process can be waken up. This change is to
force context switch each time after processing each IPC message
to allow user process to have a chance to run.
Change-Id: I3cdebe074834d85f89bb42fd872ae4733b6a8510
Signed-off-by: Jilai Wang <jilaiw@codeaurora.org>
Currently, in syna_tcm shutdown syna_tcm remove operations
are performed. If shutdown is called when resume is in
progress, it can lead to using of already freed memory in
resume function.
Change-Id: I8c226d0866e68ce6a6d22346a0678acc0cc09e46
Signed-off-by: Ritesh Kumar <riteshk@codeaurora.org>
uport->lock was first initialized in msm_geni_serial_probe() with IRQ
enabled and calling uart_add_one_port() API. Same uport->lock will
be re-initialized again from uart_add_one_port() context.
In issue case IRQ is getting fired in one core and acquiring uport-> lock,
at the same time uport->lock is getting re-initialized by serial_core.c
driver on other core and changing the lock owner value to initial value.
When msm_geni_serial_isr() trying unlock uport->lock it is checking for
owner value with initialized value and reporting kernel crash.
Fix this by setting NO_AUTO_ENABLE flag while IRQ registration in probe
and enable and disable the IRQ form port_open and port_close.
Also added changes in this patch to do not stop RX engine from
msm_geni_serial_poll_tx_done API. Currently driver sending
S_GENI_CMD_CANCEL instead of M_GENI_CMD_CANCEL to cancel TX.
Change-Id: I4077f07335f572f190f2f17eb6ee1bf99fe5f189
Signed-off-by: Chandana Kishori Chiluveru <cchiluve@codeaurora.org>
Header file is added along with new FBE framework.
Change-Id: Iaff7b0408c3ee9f92264da0d145b3f761b551e16
Signed-off-by: Neeraj Soni <neersoni@codeaurora.org>
When switch mode with etr being enabled more than one time, it needs
to reset all the etr settings for previous mode instead of return busy.
Change-Id: I243a6d910bb3dd8ac9ca30dadbd1c6ab3cefd00f
Signed-off-by: Mao Jinlong <jinlmao@codeaurora.org>
fg_gen4_probe() should not be dependent on DEBUG_FS
API's returning success. Continue device probe,
when DEBUG_FS is disabled.
Change-Id: Ibb01e00d4f6cc7982701e8dd2ac2cd51148a9aea
Signed-off-by: Prateek Sood <prsood@codeaurora.org>
