| Age | Commit message (Collapse) | Author |
|
The kernel now receives wait tracking data (similar to gathers and
relocs) and compares the current syncpt with the threshold value.
If it's old, it gets a kernel mapping and rewrites the method data
to use a kernel reserved syncpt that is always 0 (so trivially pops
when seen by the HW).
Bug 519650
Bug 785525
Bug 803452
(cherry picked from commit 4069d8e67665624ad3dceb628e572980dd57acd0)
(cherry picked from commit 6e4336408588e348804a62e53386acc9abc06823)
Change-Id: I60374cb81318f9166e49aa2afca52c9d44d4a20e
Reviewed-on: http://git-master/r/23159
Tested-by: Nitin Kumbhar <nkumbhar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
This reverts commit b514cec462faa2e29adc8c76e43acffcfca248f6.
Change-Id: I674b74e0e173a5af1c5107ffa106f16919887c2f
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/22828
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
This reverts commit 03bc8a7c8aec3ed2c2bbe60442df9d4789975f1f.
Revert "tegra: usb: ehci: Error handling for hsic phy rx error"
This reverts commit ea85e0c7a3a8a8b70478befb1fd7c9ff1d69821b.
Bug 791857
Change-Id: Ied16b58afd572c42eb7cfc77352996b5fafaf4d1
Reviewed-on: http://git-master/r/22737
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
|
|
Update Invensense Motion Library (MPL) to production version
v3.3.3. Previous version was engineering release and is not
suitable for mass production. This version of the MPL most
notably fixes problems with suspend/resume where touch screen
would quit working during a suspend/resume cycle.
Cherry-pick from http://git-master/r/#change,22109
Change-Id: Ic2e138ee665453da4c3eaa386a1bec9abf81b7cd
Reviewed-on: http://git-master/r/22190
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Robert R Collins <rcollins@nvidia.com>
|
|
When DC(Display controller) meets underflow,
DC needs to be reset to recover this,
but in several resets, it hangs.
To avoid this,
- Set DC STOP mode ahead of DC reset assert
- Off read host bus by DC ahead of DC reset
- In DC0 reset period, to avoid DC1 access
and vice versa
- In reset worker, do not try to off host1x
Bug 785529
Bug 789567
Change-Id: I24b242425ba6d7e59ec649fe8f10b41ac3d0c091
Reviewed-on: http://git-master/r/22028
Reviewed-by: Min-wuk Lee <mlee@nvidia.com>
Tested-by: Min-wuk Lee <mlee@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Fix for sending zero length packet on control endpoint when
transfer size is multiples of MAX packet size.
Bug 793731
Reviewed-on: http://git-master/r/20850
(cherry picked from commit 38d4a5a3e53ca4a9f821bb081062da616ee9ee79)
Change-Id: Id7022d233b88ca18937b244ae9dc4a2d08f32bba
Reviewed-on: http://git-master/r/22001
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
|
|
if the system is woken by an alarm, tps' irq handler
gets called and it tries to communicate on i2c. i2c adapters
resume later which causes communication failures in tps' irq
handler. the right way is to disable tps' irq while suspending
in order to avoid such i2c communication failures.
original change: http://git-master/r/#change,21099
(cherry picked from commit 5acaf09b682e5c9e0309bae53067f2fde557bbc1)
Change-Id: I76fb13db8b7a3543f5e6d772fda2549493d22876
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/22002
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Increased timeout values to maximum safe values
BUG 791857
Change-Id: Ib3aa2a495391b8cf1e3795759bfe3bb78598839d
Reviewed-on: http://git-master/r/21234
Tested-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
Reviewed-by: Shail Dave <sdave@nvidia.com>
|
|
Implementation of recover function for hsic phy rx error.
BUG 791857
Change-Id: Iedd16caf8ce61a9fa280ae3f62d4f1475318ee72
Reviewed-on: http://git-master/r/21225
Tested-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
When device resumes vbus_active status should be set.
Also, correcting the spin_lock_irqsave calls.
Bug 770041 791252
Reviewed-on: http://git-master/r/20529
(cherry picked from commit f17ce7e1a68be7410e8b7a2bde9736ffc0f4b14e)
Change-Id: I1b65a875005233a7cbce0c754b9a3ee25beb108f
Reviewed-on: http://git-master/r/20966
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
|
|
after enabling any LDO/SM, there is a specific amount of delay
required before the regulator becomes stable.
Reviewed-on: http://git-master/r/20738
(cherry picked from commit 1d61f12a9a4cb2277503636085896a32f989fa54)
Change-Id: If79fba17a9424d0324a05a9e35607c830f5576f9
Reviewed-on: http://git-master/r/20980
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Adding support for 1080p@30Hz.Disabled by default.
Fixes Bug 789164
Reviewed-on: http://git-master/r/20349
Tested-by: Gaurav Sarode <gsarode@nvidia.com>
(cherry picked from commit dbb4aa8f2a8f6126a8b7f90447c7464dce4c66ab)
Change-Id: I678b34087a8bdc5b9a4778c16c7ca34bf9e34098
Reviewed-on: http://git-master/r/20979
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
bug 773671
Change-Id: Ia3d5ff4843a3da48a9a43123040b8bb75497cfef
Reviewed-on: http://git-master/r/18757
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
bug 773671
Change-Id: If4265051873809491c80ada9401e48014c15f63d
Reviewed-on: http://git-master/r/19397
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Fixing the hsic resuem issue by enabling the interrupts on ehci-restart.
BUG 790888
Change-Id: Ibdd6e844c2f80d2f3ba0a17266717fea949cc383
Reviewed-on: http://git-master/r/20063
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
bug 773671
Change-Id: Ib93f0dcb7e22220fe297c81d403c401548f3c649
Reviewed-on: http://git-master/r/18280
Tested-by: Joseph Lehrer <jlehrer@nvidia.com>
Reviewed-by: Thomas Cherry <tcherry@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
|
|
For USB, in OTG mode driver interrupt enable registers
must be saved when device goes into suspend mode and
must be retained when device resume.
Bug 791252
Change-Id: I349a629105d4f5a236c35ef5cd37aeefcd2cece7
Reviewed-on: http://git-master/r/20375
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
A new driver is implemented to actively manage the bluetooth module
power. bluesleep also tries to manage the power of the transport used.
Two signals (GPIOs) are used to manage the power events.
BT_WAKE : signal from HOST to BT chip to intimate BT chip can sleep.
HOST_WAKE: signal from BT chip to HOST to intimate HOST should wakeup/
activate the transport modules required for BT communication.
Bug 791669, 773186
(cherry picked from commit 111f4ccd3c4cfde2fa52ae4c0c56a2288c3af3a8)
Change-Id: Iff1e81bb22d9bd43113f7cdd01329da3ae852a15
Reviewed-on: http://git-master/r/19858
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
The commit 4547be7 rewrites suspend and resume functions, this
introduces a problem on the OMAP3EVM platoform. when the kernel boots
with no_console_suspend and we suspend the kernel, then resume it,
the serial console will be not usable. This problem should be common
for all platforms.
The cause for this problem is that when enter suspend, if we choose
no_console_suspend, the console_stop will be skiped. But in resume
function, the console port will be set to uninitialized state by
calling set_termios function and the console_start is called without
checking whether the no_console_suspend is set, Now fix it.
Refer
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.37.y.git;
a=commit;h=ca2e71aa8cfb0056ce720f3fd53f59f5fac4a3e1 for
cherry-pick the changes from the kernel 2.6.37, commit id as
ca2e71aa8cfb0056ce720f3fd53f59f5fac4a3e1
Bug 758845
Change-Id: Ib83494b2b13cd7179d3ae173be328c8cd776d431
Signed-off-by: puneet saxena <puneets@nvidia.com>
Reviewed-on: http://git-master/r/19590
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
|
|
Added support to tegra_hsuart driver for bluetooth wakeup.
Bug 773186
Change-Id: Id8f1face1b99942fd13949d0815a1dedd1a5a5d0
Reviewed-on: http://git-master/r/19586
Reviewed-by: Anantha Idapalapati <aidapalapati@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Anantha Idapalapati <aidapalapati@nvidia.com>
|
|
Conflicts:
drivers/net/wireless/bcm4329/Makefile
Change-Id: I5e6994d4db216062b9cd1673f45bd9fdcf1f96ae
|
|
bug 788941
Change-Id: Ib6c3da2f30fa5e7240cbdd1d406682aca3c820a2
Reviewed-on: http://git-master/r/20144
Tested-by: Chong Zhang <chzhang@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
|
|
We call tegra_overlay_put inside the overlay lock, which can do a flip.
It's not safe to do a flip in an atomic context.
Change-Id: I4b043737a3eede0d47b8269a2d40e7c739f75df3
Reviewed-on: http://git-master/r/20087
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Tested-by: Daniel Willemsen <dwillemsen@nvidia.com>
Reviewed-by: Prajakta Gudadhe <pgudadhe@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|
|
Enabled mutex debugging reavealed potential deadlocks
introduced with compaction.
Handle spin lock replaced with mutex. Heap functions cannot be
protected with spinlock because they call kernel slab allocation
functions which cannot be called from atomic context.
nvmap_client ref_lock is also replaced with mutex. Otherwise we
cannot access heap parameters protected by mutex nvmap_handle lock.
Extra locking for handle->owner removed.
bug 793364
Change-Id: I635ce9ebf259dd7bf8802457567f93b7be5795ea
Reviewed-on: http://git-master/r/19850
Reviewed-by: Kirill Artamonov <kartamonov@nvidia.com>
Tested-by: Kirill Artamonov <kartamonov@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
|
|
|
|
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
This driver supports devices conforming to the Communication Device
Class (CDC) Network Control Model. The CDC specifications are
available from <http://www.usb.org/>. This driver is implemented as
a minidriver for usbnet driver framework.
Bug 776360
Change-Id: If5e900f80edebc742536a59716aad546b714ba4c
Reviewed-on: http://git-master/r/14921
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Change-Id: I6ce3f66075856397b394f433a4ee29ff3357b548
Reviewed-on: http://git-master/r/16977
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Switch to 2080x1164 for 1080p resolution. Add a reset to
the I2C sequences.
Bug 786227
Change-Id: I0514275c87504673a4297679bfa77d0a786f1532
Reviewed-on: http://git-master/r/19649
Reviewed-by: Nathan Lord <nlord@nvidia.com>
Tested-by: Nathan Lord <nlord@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
|
|
tegra_hdmi_writel should be _tegra_hdmi_writel in this function
Change-Id: I7bbd85b634cd6dbd67637db57b66559cb092c8ba
Reviewed-on: http://git-master/r/19664
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Change-Id: I3b060b622a593d48319a442072a21d0c4f9527ae
Reviewed-on: http://git-master/r/19049
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Change-Id: Ie894d71f45cc08709daff3f258e0c4676b7778b0
Reviewed-on: http://git-master/r/19687
Reviewed-by: Nathan Lord <nlord@nvidia.com>
Tested-by: Nathan Lord <nlord@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
|
|
tegra_fb_set_windowattr() has logic to adjust
window y according to yres, however when in stereo
mode, the max y allowed should be v_active, which
could be larger than yres.
bug 784597
Change-Id: I63342be8e2d87396502574f3a8dd0fb2769a47a8
Reviewed-on: http://git-master/r/17537
Reviewed-by: Chong Zhang <chzhang@nvidia.com>
Tested-by: Chong Zhang <chzhang@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
VIC for 720p stereo mode should be 4 (60Hz) or 19 (50Hz).
bug 792143
Change-Id: I3edb468a992842ed6a3247fbab02970b0c078acb
Reviewed-on: http://git-master/r/19468
Reviewed-by: Chong Zhang <chzhang@nvidia.com>
Tested-by: Chong Zhang <chzhang@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
There are places where nvmap_free_handle_id is called
when interrupts are disabled and mutex cannot be used as
nvmap handle lock.
Change-Id: Icc220fe627c08f21c677d936a54f70c818dc8e8c
Reviewed-on: http://git-master/r/19489
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Change-Id: I2b572a4fdfd83f7f9dc9b3f5b9244072cb240764
Reviewed-on: http://git-master/r/19528
Reviewed-by: Nathan Lord <nlord@nvidia.com>
Tested-by: Nathan Lord <nlord@nvidia.com>
Reviewed-by: Erik M Lilliebjerg <elilliebjerg@nvidia.com>
Reviewed-by: Chien-Yu Chen <chichen@nvidia.com>
Reviewed-by: Patrick Shehane <pshehane@nvidia.com>
Reviewed-by: Chan Vu Truong <jtruong@nvidia.com>
Tested-by: Chan Vu Truong <jtruong@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Conflicts:
drivers/net/wireless/bcm4329/Makefile
Change-Id: I13ed89657bb43ac906c6424372050df5fd681374
|
|
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
Change-Id: Ie4606d9a5154090274168babc110ea2d79747c05
Signed-off-by: Erik Gilling <konkers@android.com>
|
|
|
|
Reverting previous hdmi hotplug fix (commit
633a7967cad4454327572f85fbdf5cd88eb68b78). It doesn't
seem to fix hotplug problem on ventana, and it is
causing tegra_dc_enable() to be called before we
set up hdmi mode properly. It's no longer needed
when we set ventna_hdmi_enb=1.
The 5ms sleep time after tegra_dc_enable() is no
longer needed, as the tegra_dc_enable() is removed
from tegra_dc_hdmi_detect_worker().
bug 784597
Change-Id: Ibd2ef95f45bec23031e6f839490f06a2832c6931
Reviewed-on: http://git-master/r/17084
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
- Add support to PNO with adaptive scan time
- Remove logic to generate Link Down based on Roaming Event
- Improve sco/esco detection method for BT COEX
- Add new function TXPOWER to reduce power if needed
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
|
|
An attempt had been made to reduce the number of pte operations
while patching relocs. The optimization was incorrectly coded
and was not providing the expected speedup.
Credit for the find goes to Peter Pipkorn.
Change-Id: Ic83b20ee470e54d5053f747dbcbdf7b038b7c7c4
Signed-off-by: Rebecca Schultz Zavin <rebecca@android.com>
|
|
This reverts commit 5f2e1258ff35f700f5ca9df3047dc5fe19b99017.
|
|
devices""
This reverts commit 6b53bad8ac54b3d748c4b0dbe6b0a4ed6e2e60f4.
|
|
Conflicts:
drivers/usb/host/ehci-tegra.c
include/linux/usb.h
include/linux/usb/hcd.h
Change-Id: I2499459b717e36a2a994af9d7a5ae1ecb5e7ca9c
|
|
|