Use Vmax from play effect in haptics_set_gain() only if the effect
is valid. Otherwise, use Vmax from the haptics configuration instead.
Change-Id: I7ec0f8c869096bccb26f7fda0057e3db3a51225d
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Discard size calculation uses max_busy_timeout in deriving the
value. So, we can ensure a larger discard size by setting this
timeout as zero. If this timeout is zero then it takes max erase
timeout vlaue (which is 60sec) in the discard size calculation.
And qcom SDHC can support h/w based busy detection, So
we need set MMC_CAP_NEED_RSP_BUSY capability flag.
Since Qcom SDHC can support h/w based busy detection for R1b
commands, this timeout value is not relevant for us.
Setting it zero won't affect in any operation provied
MMC_CAP_NEED_RSP_BUSY cap is set.
Change-Id: Ib20a1e536d2e24cf8de1e927715a8a3aa7f0ae27
Signed-off-by: Veerabhadrarao Badiganti <vbadigan@codeaurora.org>
This change is for general scheduler improvements.
Change-Id: I511e49ea6c207378c66a580e29e89f28aaa9f7f3
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Driver currently restrict upper bound check for bInterval
to 4 which corresponds to 1 ms. Fix the bInterval range
check as per the USB spec for ISOC endpoint.
Change-Id: I580e1fdfab0eeb1231642b920239691e7af67727
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Similar to xhci_stop_endpoint(), this API is called when a device
is removed. The check for udev->state == USB_STATE_NOTATTACHED
was added by mistake and should be removed.
Change-Id: Ie0df67c3139bd585f098215d093169c961710349
Signed-off-by: Jack Pham <jackp@codeaurora.org>
Most of the times mink returns response type as inbound
request needed, which is nothing but call back object
requests. While decoding the response type it should
provide as info or debug message instead of error message.
Change-Id: I7eac9f6ae779b4c3d952fac38880cf4a658428c5
Signed-off-by: AnilKumar Chimata <anilc@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: I65e81e5ec01ebb3747936cdd81f886632c5419f1
Signed-off-by: Tao,Zhang <taozha@codeaurora.org>
Forbid enabling sink in the process of reading sink. Otherwise,
sink flag "activated" will be set to true, and the source has a
chance to be added to "cs_active_paths" twice. Then, system will
crash if sink is continued to be read due to two same source in
"cs_active_paths".
Change-Id: I3317ea435e9d84258e3fcbf854a6078afcd4a08e
Signed-off-by: Tao,Zhang <taozha@codeaurora.org>
Use cmpxchg instead of a spinlock in scs_check_usage() to avoid
deadlocks.
Bug: 157781894
Change-Id: I1701ccaf25fdbd34ce4798c6f93e220b1565fb34
Signed-off-by: Sami Tolvanen <samitolvanen@google.com>
Git-commit: e467b8c7db
Git-repo: https://android.googlesource.com/kernel/common
[jshriram@codeaurora.org: cherry-pick]
Signed-off-by: Jeevan Shriram <jshriram@codeaurora.org>
This API can be called by the QMI sound driver precisely when a
device is disconnected in order to issue a stop endpoint command
to properly halt the transfer ring. With this check the function
silently bails, so the XHCI controller hardware may continue to
be accessing the buffers on the transfer ring; meanwhile the
QMI sound driver proceeds to unmap the buffers from DMA
resulting in an SMMU fault. Remove the check to allow the
endpoint to be properly stopped.
Change-Id: I80315c31d9b1685ac4375c1da051a8e22cab07ca
Signed-off-by: Jack Pham <jackp@codeaurora.org>
Remove redundant function name information from the log string, and add
a word to help in readability.
Change-Id: I464b7c8e60771ea06744ef910c525c6dd664492e
Signed-off-by: Guru Das Srinagesh <gurus@codeaurora.org>
The write performance of TLC NAND is considerably lower than SLC NAND.
Using SLC NAND as a WriteBooster Buffer enables the write request to be
processed with lower latency and improves the overall write
performance.
Adds support for shared-buffer mode WriteBooster.
WriteBooster enable:
SW enables it when clocks are scaled up, thus it's
enabled only in high load conditions.
WriteBooster disable:
SW will disable the feature, when clocks are scaled
down. Thus writes would go as normal writes.
To keep the endurance of the WriteBooster Buffer at a maximum, this
load-based toggling is adopted.
Change-Id: I55a348f17e2d29b46ed9b29960254937c146f147
Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
Add a config fragment for disabling DEBUG_FS.
Change-Id: I877c74955e467002976c3bac6c946183c8be7043
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
The energy values passed to sched_compute_energy trace event
are of unsigned long type. So use %lu format specifier instead
of %llu.
Change-Id: I1e82b34559d76d5cfb023598a8ce62917281a9af
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
The cpu_grp->mons_lock is acquired in the memlat hotplug notifier
callbacks to prevent races within the driver. The cpus_read_lock is
inherently acquired as well since it is in the middle of a hotplug
event. In parallel, stop_hwmon() could unregister from the hotplug
notifier (i.e. when last memlat mon in system is removed). However,
unregistering the hotplug notifier also requires the cpus_read_lock
and is done with the cpu_grp->mons_lock held as well which would lead
to a deadlock if a hotplug is currently in progress with the memlat
notifier callback waiting for the cpu_grp->mons_lock.
To fix this, release the cpu_grp->mons_lock in stop_hwmon() before
unregistering with the hotplug notifier. Also, make sure the memlat
hotplug notifier callbacks check cpu_grp->num_active_mons before
restarting events since that work won't be necessary if there are no
active memlat mons in the system.
Change-Id: I401639a6e28a472a64a96456d2c06f57b35dbc0d
Signed-off-by: Amir Vajid <avajid@codeaurora.org>
Update yet another batch of QCOM whitelist file with additional
symbols and regenerate the snapshot accordingly.
Change-Id: I0997a786fd50180744f1eb8fc9b0a817c589eb5e
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
A task can migrate either while it is waking or while it
is running via load balancer. Print the task status
i.e running or not in sched_migrate_task. This helps in
counting the different types of migrations without relying
on other trace events.
Change-Id: Ib473f9ccdc78003bb1f5d2dc24354f2db7a684f5
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
This change is for general scheduler improvements.
Change-Id: I6dc8fd228ca34fd36cdbaf58c42812bae3dcff7d
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Signed-off-by: Stephen Dickey <dickey@codeaurora.org>
Used by some Linux hypervisor support to tell userspace which hypervisor
it is being run under.
Bug: 157224726
Change-Id: Ia1cb56e665af6b60f6a51b5e81dd7abed240f812
Signed-off-by: Alistair Delva <adelva@google.com>
Git-repo: https://android.googlesource.com/kernel/common/
Git-commit: f8aa5f514ccb2ded066fe47f6fd571fe016ca648
Signed-off-by: Siddharth Gupta <sidgup@codeaurora.org>
