Age | Commit message (Collapse) | Author |
|
Bug 1315200
Change-Id: If1bfc2a17d302f10b4d5439fa5e1ba5914b2fcc5
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/244113
Reviewed-by: Tao Xie <txie@nvidia.com>
Tested-by: Tao Xie <txie@nvidia.com>
|
|
Call tegra_hotplug_signal to queue deferred work after a delay of 30ms and call gpio_get_value
in tegra_dc_hpd
bug 1310096
bug 1298680
Change-Id: Iab37af3258429b1e281705eb5b077be31b53b07f
Signed-off-by: sharath sarangpur <ssarangpur@nvidia.com>
Reviewed-on: http://git-master/r/241633
GVS: Gerrit_Virtual_Submit
Reviewed-by: Jon Mayo <jmayo@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
This change takes a wakelock before stating the recovery
mechanism of JS
Bug 1306389
Change-Id: I0109455647988248f1e37d5a000e1e34654e40e5
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/241103
|
|
This change recovery the JS uC after USB resume failure by
unloading USB, resetting uC from ISSP and then reloading USB
Bug 1306389
Change-Id: I086636d4b7b91e3a2874f584fa6efbfd2cae6014
Signed-off-by: Michael Hsu <mhsu@nvidia.com>
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/240004
|
|
Unbalanced irq_enable/disable will cause potential risk of the sensor
data not being sent out. Add critical section and flag to prevent
this situation.
Change-Id: I4a8b3ebfd07b3e4901ad807c8052c38e3f23315e
Signed-off-by: Xiaohui Tao <xtao@nvidia.com>
Reviewed-on: http://git-master/r/239385
Reviewed-by: Sang-Hun Lee <sanlee@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Robert Collins <rcollins@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Change DEF_ACCEL_ST_SHIFT_DELTA and DEF_GYRO_CT_SHIFT_DELTA to
500.
Change-Id: Id4db11789d561dfc3899d8de592421f04dbf19db
Signed-off-by: Xiaohui Tao <xtao@nvidia.com>
Reviewed-on: http://git-master/r/239833
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Robert Collins <rcollins@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Change-Id: I342d1f1505caedabaefa0b2f0eb5dccdf5046bca
Signed-off-by: Jean Huang <jeanh@nvidia.com>
Reviewed-on: http://git-master/r/239022
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Tao Xie <txie@nvidia.com>
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
This is a WAR to reset the USB device if the device
fails to resume. We assume that the resume failure is
because of the uC hang.
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Change-Id: I6fc85cd0ce2fad7a7dbff5b6ddee0a96149a5d76
Reviewed-on: http://git-master/r/239086
GVS: Gerrit_Virtual_Submit
Reviewed-by: Tao Xie <txie@nvidia.com>
Tested-by: Tao Xie <txie@nvidia.com>
Reviewed-by: Ankit Pashiney <apashiney@nvidia.com>
|
|
v58->v59:
- Keep uC USB buffer unchanged for about 1 second when exiting suspend
mode, in order to fix false wakeup events issue
Change-Id: I175bb0328af1840cbfe8c70e0607d7d8023e0c26
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/239099
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Tao Xie <txie@nvidia.com>
Reviewed-by: Ankit Pashiney <apashiney@nvidia.com>
|
|
Use mutexes to prevent concurrent wifi / bluetooth turn
on sequence.
Bug 1302412
Change-Id: Icd086b616af2f5ccbff7968d613310c365ad549a
Signed-off-by: Michael Hsu <mhsu@nvidia.com>
Reviewed-on: http://git-master/r/236533
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Change-Id: I2158918b6a22a4ceeadecdfa5a51fc87a624a105
Signed-off-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-on: http://git-master/r/235510
Reviewed-by: Mandar Padmawar <mpadmawar@nvidia.com>
Tested-by: Mandar Padmawar <mpadmawar@nvidia.com>
|
|
On P2560 hardware only, wifi chip generates excessive wifi
activity interrupts:
- on first boot after flashing image
WAR is to mask this specific wifi activity interrupt to
prevent it from keeping application processor awake.
Bug 1299635
Change-Id: Idf0fdaf817621e3ae5e0f63864c488366dbbcaba
Signed-off-by: Michael Hsu <mhsu@nvidia.com>
Reviewed-on: http://git-master/r/235330
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
v57->v58
-changed dead band to 38
-changed cal window to 80
Bug 1266521
Change-Id: I686ef709df77ad7d29e8cee6420683ee901a73cf
Signed-off-by: Jun Yan <juyan@nvidia.com>
Reviewed-on: http://git-master/r/235156
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
v56->v57
added changes to uC FW that will check to make sure if LED PWM timer0 == Started then check the timer0 start bit and if not set
then set it to start running again.
v55->v56
- Bump revision to v0_56.
- Changed the following End Point 2 commands:
LED_UC_DRIVE- This function now does Nothing. Left it in for backwards compatibility.
(Previously this function setup the Port 1.1 pin to drive from tri-state. And also set the LED pin high (ON).)
LED_BREATHE_ON- This function now sets up port 1.1 in a drive state from tri-state and starts timer0 for the SW PWM.
LED_BREATHE_OFF- This function now sets up port 1.1 in a drive state from tri-state.
Also keeps the same logic as before stopping the SW PWM timer0 and set P1.1 LED LOW (OFF).
Bug 1266521
Change-Id: I2ef12fe6c66e03d299b0135e749498d8154f3937
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/234431
Reviewed-by: Automatic_Commit_Validation_User
|
|
Change-Id: Ib87ff58487c324124987a563fc0621d8f8482784
Signed-off-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-on: http://git-master/r/234417
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Tao Xie <txie@nvidia.com>
Tested-by: Tao Xie <txie@nvidia.com>
|
|
- Bump revsion to v0_55.
- Center point calibration window (power on/reset) now 40 from 80
- power on defaults for Right/Left Joystick X,Y axes are now 250 from150.
Note: doing this makes the scaling values less granular or smaller steps on power on.
Thus helps with RS mouse drift being a larger value just outside the center dead band.
Noticed that the RS mouse drift can go away after moving the joysticks to its max and min points.
- power on defaults for right/left analog triggers are now 600 and 300 max/min.
The original version had this at 300 and 700 reversed. Hence, on the very first trigger pull,
you only had to move a very small distance to hit max.
NOTE: Center point stiction dead band is still set to 37. Same as v52.
Bug 1266521
Change-Id: I071c9b1ef2cb837787fd4f21f0e4a6bee9aafc01
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/233806
Reviewed-by: Automatic_Commit_Validation_User
|
|
Improve headphone jack detection in certain
scenarios.
Bug 1296602
Change-Id: I748f7649680ad60edbc450c09027cb3b76552f8c
Signed-off-by: Scott Peterson <speterson@nvidia.com>
Reviewed-on: http://git-master/r/233081
Reviewed-by: Vinod Subbarayalu <vsubbarayalu@nvidia.com>
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
disable OTG mode when over temprature and over current
interrupt occurs and re-enable OTG mode after 30sec.
Bug 1285652
Change-Id: Ic7ee97a3b14cea03462d16b24f8de670e0e76904
Signed-off-by: Syed Rafiuddin <srafiuddin@nvidia.com>
Reviewed-on: http://git-master/r/226994
(cherry picked from commit 4e8d08beb0a8659862018eda355c845167adac9d)
Reviewed-on: http://git-master/r/231751
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
|
|
When new VDD_CORE override level is the same as the one already in
place do not return error from the override API.
Bug 1280293
Change-Id: Ic4393541308139c2ac9579acc8e2af47b144d521
Signed-off-by: Alex Frid <afrid@nvidia.com>
Reviewed-on: http://git-master/r/225378
(cherry picked from commit cea34a24e79f8be40fa5aaf6a38992a0d54e705e)
Reviewed-on: http://git-master/r/231750
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
|
|
Problem description:
- nct1008_suspend powers off nct1008
- nct1008_suspend does stop the workqueue and irq, but
if there is a kernel thread which would trigger
nct1008_read_reg or nct1008_write_reg, nct1008 would
still be accessed after it is powered off
Fix description:
- Rename the existing flag shutdown_complete to nct_disabled
- Update the value of nct_disabled when powering nct1008 on and off
Bug 1288427
Change-Id: Id885794eb39a71025ad9f5c3615156c19039d13f
Signed-off-by: Sang-Hun Lee <sanlee@nvidia.com>
Reviewed-on: http://git-master/r/228011
(cherry picked from commit 08eed1ddbacece2f1c8b4fba633c01c0f87ba2cd)
Reviewed-on: http://git-master/r/232275
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
Problem descritpion:
- Even after powering off the device through inv_set_power_state,
inv_read_fifo can be running in paralell, still talking to the
device
Fix description:
- When powering off the device, also disable the irq to avoid
talking to a powered off device
- As a side effect, this change will also ensure interrupts from gyro
do not result in a lock up of i2c bus during suspend even in case
of an interrupt storm
Bug 1285239
Change-Id: I42dfa094b645944e22d600b64abc18b10b7fb38b
Signed-off-by: Sang-Hun Lee <sanlee@nvidia.com>
Reviewed-on: http://git-master/r/227781
(cherry picked from commit a2ce58ee6da12bbe3f9d18dfcef1e6a48a4572a9)
Reviewed-on: http://git-master/r/232274
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
1. CTS failure
2. Suspend/Resume time
Bug 1283362
Change-Id: I5cbd85bbab26f029dd7400cd17c9bb1358fc2ef8
Signed-off-by: Xiaohui Tao <xtao@nvidia.com>
Reviewed-on: http://git-master/r/231660
(cherry picked from commit 10c3573c922e79d81be2d2e0812b1945d4fab0f4)
Reviewed-on: http://git-master/r/232253
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-by: Tao Xie <txie@nvidia.com>
Tested-by: Tao Xie <txie@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
Update speaker model, EQ, and configs for
the NXP tfa8997 device.
Change-Id: Iabed2761aa6156eaac1ca3753d8c58599f885726
Signed-off-by: Scott Peterson <speterson@nvidia.com>
Reviewed-on: http://git-master/r/231741
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
|
|
Don't wait for communication to stop if HDMI isn't plugged
Bug 1275577
Change-Id: Ifb56bc8a4b36ac2cb40614811398920b7e293e04
Signed-off-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-on: http://git-master/r/231350
(cherry picked from commit fc774f94ffa54b1a6ce1771ac82b82c3a1eea39f)
Reviewed-on: http://git-master/r/231692
Reviewed-by: Automatic_Commit_Validation_User
|
|
Disable the h/w alignment fix for T114 A02.
Bug 1289107
Change-Id: I6d64e2de23d0358a2edbf3730e4f1b6a70f6903b
Signed-off-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-on: http://git-master/r/228649
Reviewed-on: http://git-master/r/231096
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Peter Zu <pzu@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
Tested-by: Peter Zu <pzu@nvidia.com>
|
|
- Fixed Miracast discovery issue after P2P disconnection.
- Fixed P2P action frame issue when multiple P2P IEs are in the probe response.
- BW allocation for VSDB
- Support offset for RSSI report
Bug 1282745
Change-Id: Ie55a05c51e95941e09e5c582c4936909f490575e
Signed-off-by: bibhayr <bibhayr@nvidia.com>
Reviewed-on: http://git-master/r/#change,228838
(cherry picked from commit 6147573414026a4ff978885f38e4842de55fb4fe)
Reviewed-on: http://git-master/r/230104
Reviewed-by: Narayan Reddy <narayanr@nvidia.com>
Tested-by: Narayan Reddy <narayanr@nvidia.com>
Reviewed-by: Rakesh Kumar <krakesh@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Wifi prepower logic is needed to support
multiple wifi chip vendors so that we can
load different wifi driver at run-time.
Disable this flag for rel_roth as it uses
only bcm43241 wifi chip.
Bug 1280309
Change-Id: Ia1399c3fe003c6704a868f7646c011d0899e8ddf
Signed-off-by: Nitin Bindal <nbindal@nvidia.com>
Reviewed-on: http://git-master/r/230826
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Rakesh Kumar <krakesh@nvidia.com>
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
Code drop from raydium
1. RESET signal correction during suspend/resume
2. The LP0 touch not work issue fix
3. The old functionality such as environment variable and calibration should remain the same.
Change-Id: Ibb71c2ddb4a7b6760baa991a737fa6c3580b893a
Signed-off-by: Xiaohui Tao <xtao@nvidia.com>
(cherry picked from commit 7df8f34a4b4a26305afac8aff42eeaa528655d33)
Reviewed-on: http://git-master/r/230050
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
Mask HS200 mode support for sdmmc4.
In DDR50 mode for eMMC can support max clock of 52MHz. For Tegra sdmmc
controllers, the host clock in ddr mode should be double that of the
eMMC device. Taking into consideration the dvfs tables, limiting ddr
mode clock to 51MHz to allow for lower core voltages to set even when
sdmmc4 clock is ON.
Bug 1287739
Change-Id: Ib04dce91d771ab5505dd67ea3a8d5c704d0b499e
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
(cherry picked from commit 3db4b21d8d5eb5a99dbcd3d660478a3a89ced104)
Reviewed-on: http://git-master/r/230048
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Tested-by: Matt Wagner <mwagner@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
If "caps2" host capabilities does not indicate support for MMC
HS200, don't allow clock speeds >52MHz. Currently, for MMC, the
clock speed is set to the lesser of the max speed the eMMC module
supports (card->ext_csd.hs_max_dtr) or the max base clock of the
host controller (host->f_max based on BASE_CLK_FREQ in the host
CAPS register). This means that a host controller that doesn't
support HS200 mode but has a base clock of 100MHz and an eMMC module
that supports HS200 speeds will end up using a 100MHz clock.
Change-Id: I2967fcc733b7178bdf54d6f75f65bdff253fc1cc
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Signed-off-by: Al Cooper <alcooperx@gmail.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Reviewed-on: http://git-master/r/227758
(cherry picked from commit ed5cc4ef1e8bcdae292b6f234dbb7054cf5542cb)
Reviewed-on: http://git-master/r/230047
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
|
|
Current implementation decides the card type exclusively. Even though
eMMC device can support both HS200 and DDR mode, card type will be
set only for HS200. If the host doesn't support HS200 but has DDR
capability, then DDR mode can't be selected.
Change-Id: Id2b9095f8ffe59c520850acd40681a9ef15c3ff9
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Reviewed-on: http://git-master/r/227757
(cherry picked from commit 084aa8cc074b0e95883934f82f5521d0cc5e0941)
Reviewed-on: http://git-master/r/230046
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
|
|
Increase by 30mV
Bug 1278943
Change-Id: I554c281ca1f12cb7494516844f4fd72e1d4b03b1
Signed-off-by: Matt Wagner <mwagner@nvidia.com>
(cherry picked from commit e61f283f9966358e68c7cdcd9ea26bbc7bbc18c3)
Reviewed-on: http://git-master/r/230045
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
|
|
Clear dhd driver hang event upon device close, so that next open
will not be blocked.
Prevents condition where wifi cannot be turned off / on because
of a previous hang event flag being set.
Bug 1280309
Change-Id: I6569cd39c8866682c7a19fa840b32162c2a4dd5b
Signed-off-by: Michael Hsu <mhsu@nvidia.com>
Reviewed-on: http://git-master/r/229999
Reviewed-by: Rakesh Kumar <krakesh@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
Updated the auto calibration values.
Fixed call to register access function.
Bug 1166307
Bug 1283871
Change-Id: I39976bd3cbdcc09df682589c418b06281d7eec97
Signed-off-by: Vineel Kumar Reddy Kovvuri <vineelkumarr@nvidia.com>
Reviewed-on: http://git-master/r/229915
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
Implementation of DSI MIPI auto calibration
Bug 1166307
Change-Id: Id4be420978b56d662d77c6d145f9e51dc881d159
Signed-off-by: Vineel Kumar Reddy Kovvuri <vineelkumarr@nvidia.com>
Reviewed-on: http://git-master/r/229914
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
Tested-by: Matt Wagner <mwagner@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
This change will force update firmware on P2560, this is
done to help with downgrading versions as required.
Bug 1266521
Change-Id: I9121a75c108d8a79f496ed7686a34e7fce66a3ad
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
(cherry picked from commit 428c5acf8cabde6d72a9eee98f98b2bdefc52f60)
Reviewed-on: http://git-master/r/229466
Reviewed-by: Automatic_Commit_Validation_User
|
|
v51->v52
- Bump revsion to v0_52.
- All Joystick Wakeup out of Suspend Tuning changes:
- Added a ADC Channel Synchronizer so as to make the Left and right joystick axes has a higher suspend mid point value.
This helps the sensitivity when moving the POT towards the GND node.
- Because of the ADC channels Sychronizer the Left and Right Analog triggers needed more Threshold tuning:
now Left Analog Trigger threshold is < 100 (was 150) and Right Analog Trigger Threshold is > 350 (was 375)
This helped move the wakeup trigger point more away from the ends.
- For the Left and Right Joysticks; we added two Thresholds wakeup methods:
1) the original dADC/dt with a delta threshold of 80. same as v46.
2) a "Measured" suspend MID-point min and max threshold.
This helps wake up when user move joystick slowly to one side or the other.
Measured absolute Thresholds are set to suspend mid point- 150 and + 150.
If suspend mid-point is too low then we will default to a low threhold of 85.
v46->v51
- Bump revsion to v0_51. This has everything that v46 has.
- Has joystick wakeup and Left and Right Analog trigger wake up.
- Analog triggers use a fixed absolute threshold: Left is set to < 150 and Right is set to > 375
- The Left and Right Joysticks still are using dADC/dt methodolgy with a threshold of 80.
However, it can be a little difficult to wake up using these. Especally if the using moves towards GND side of the POT.
Bug 1266521
Change-Id: I2322d0265fac69314368d025656e3fef8d3be414
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
(cherry picked from commit 9d0f6ae86de61f3360932b1598e8da18b0fe7404)
Reviewed-on: http://git-master/r/229465
Reviewed-by: Automatic_Commit_Validation_User
|
|
Update charger type up on connection.
Bug 1281945
Change-Id: Iea2bf0323636ae54e2e911705fd795c273de50f7
Signed-off-by: Pradeep Goudagunta <pgoudagunta@nvidia.com>
Reviewed-on: http://git-master/r/225208
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Syed Rafiuddin <srafiuddin@nvidia.com>
Reviewed-by: Anshul Jain (SW) <anshulj@nvidia.com>
|
|
Trinity discovered that we fail to check all 64 bits of
attr.config passed by user space, resulting to out-of-bounds
access of the perf_swevent_enabled array in
sw_perf_event_destroy().
Introduced in commit b0a873ebb ("perf: Register PMU
implementations").
Signed-off-by: Tommi Rantala <tt.rantala@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: davej@redhat.com
Cc: Paul Mackerras <paulus@samba.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Link: http://lkml.kernel.org/r/1365882554-30259-1-git-send-email-tt.rantala@gmail.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
(cherry picked from commit 8176cced706b5e5d15887584150764894e94e02f)
Change-Id: I5ecfb388007fba52435b49ac38855d1873ca63db
Signed-off-by: Bo Yan <byan@nvidia.com>
Signed-off-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-on: http://git-master/r/228787
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
|
|
Fix v_front_porch, v_back_porch and pwr_ctrl settings
Bug 1283232
Change-Id: Ic5f7fcd49977157bfe64e47a4b9fbcee42fa79d3
Signed-off-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-on: http://git-master/r/228540
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
|
|
Add vpp_fuse entry into ldo4 of palmas
Bug 1286520
Change-Id: I2caad9d715f1ea8fc40335c93dc36f8c7107289b
Signed-off-by: Shardar Shariff Md <smohammed@nvidia.com>
Reviewed-on: http://git-master/r/227900
Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
|
|
v40->v46
- Removed Debug GPIO P3.0
- No wakeup pulse sent in OS Idle/Display Off (aka Active/LED Breathing ON)
- If LED Breathing remains ON when Display is ON, will turn off LED
Breathing with button press or Joystick Motion (no Analog Triggers).
LED breathing on in this state is a DON’T care because Tegra is
overriding the LED control.
- Added back Joystick wakeup during USB Suspend. Only Left
and Right Analog sticks and NO Analog Triggers.
- Suspend Joystick wakeup Threshold is set to 80.
- Added a usb activity check before the LED control logic in the suspend loop. If usb activity detected; we will bail out of the loop.
This change more matches v31 suspend loop that seems to be running LP0 suspend/resume cycles just fine.
Noticed on the scope that the timing delta relationship from Resume to T-setup requests were varying quite a lot. The LED control logic
just seems to be the reason for the large timing jitter.
- Added Port 3.0 debug toggle in the following functions:
* uC Waiting for USB enumeration packets from the Host.
* While loop LED timer0 in the beginning of Suspend; Will toggle P3.0.
- While LED timer0 ISR timeouts are still implemented.
- LED flicker fix
Bug 1276644
Bug 1285468
Bug 1266521
Bug 1283114
Change-Id: I609742ea3aae5b84a90a929bb19db0b2edd4c576
Signed-off-by: Anshul Jain <anshulj@nvidia.com>
Reviewed-on: http://git-master/r/227147
Reviewed-on: http://git-master/r/228579
Reviewed-by: Automatic_Commit_Validation_User
|
|
tegra_dc_hpd(), which uses gpio_get_value_cansleep(),
is called from tegra_dc_hdmi_irq() in atomic context.
Move this call outside of the atomic context to avoid
potential lockup.
Change-Id: If62a3d257ab29eae34fd0999e6d182906a568846
Signed-off-by: Ray Poudrier <rapoudrier@nvidia.com>
Reviewed-on: http://git-master/r/226531
(cherry picked from commit e0a5c3a078138b9db103aa428a6667efb3e3a1d0)
Reviewed-on: http://git-master/r/228493
Reviewed-by: Jon Mayo <jmayo@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
GVS: Gerrit_Virtual_Submit
|
|
Update drive strengths to fix compliance issues
Bug 1278943
Change-Id: I83f9340f4031b2a675ed748307f0abd0455f1e3c
Signed-off-by: Matt Wagner <mwagner@nvidia.com>
Reviewed-on: http://git-master/r/225026
(cherry picked from commit 45a7dd54a9565efd63537a16c2cfc6f2e9194c43)
Reviewed-on: http://git-master/r/228126
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
|
|
Wait for hdmi accesses to finish before turning nvhdcp off.
Bug 1275577.
Change-Id: Ieef8635b66cfdddece7b2e1140b776b91350d272
Signed-off-by: Rakesh Iyer <riyer@nvidia.com>
Reviewed-on: http://git-master/r/227243
(cherry picked from commit ac6205a26fbf52d8439524543321012ed95c9d78)
Reviewed-on: http://git-master/r/228104
Reviewed-by: Jon Mayo <jmayo@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
Low Power Accelerometer is disabled due to known HW bug.
Bug 1279237
Change-Id: I8477fb84bbca7f8d139f5495ab7f584df528f44d
Reviewed-on: http://git-master/r/224897
(cherry picked from commit e0a3ba3b906cda0c54242c37e1fb5e03af5ba562)
Signed-off-by: Erik Lilliebjerg <elilliebjerg@nvidia.com>
Reviewed-on: http://git-master/r/227973
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Robert Collins <rcollins@nvidia.com>
GVS: Gerrit_Virtual_Submit
Reviewed-by: Matt Wagner <mwagner@nvidia.com>
|
|
This reverts commit 1c48c746ea721f95c594c08f5f1320ba78de40e4.
Bug 1281367
Change-Id: I78ad0f9886d4834b2a19542331bfd2b2e0f823af
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/227044
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Nitin Bindal <nbindal@nvidia.com>
Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
|
|
pm_flags should be set by the core/client driver if the card needs to
be powered ON during suspend and full enumeration is not required in
resume. These flags should not be set by default through platform data
Bug 1281367
Change-Id: I2b3301e92ca25e5db93809fc2a727182ede7c92a
Signed-off-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-on: http://git-master/r/227043
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Nitin Bindal <nbindal@nvidia.com>
Tested-by: Nitin Bindal <nbindal@nvidia.com>
Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
|
|
Change-Id: I9df90c7774a30f5e512d492b3dce85d3f689cfff
Signed-off-by: Narayan Reddy <narayanr@nvidia.com>
Reviewed-on: http://git-master/r/222776
Reviewed-by: Harshada Kale <hkale@nvidia.com>
Tested-by: Harshada Kale <hkale@nvidia.com>
|
|
Remove warning about creation of debugfs
nodes for the NXP tfa9887 devices.
Bug 1284011
Change-Id: Iaf67b5e0e50a803d2d934370165c7887809f0685
Signed-off-by: Scott Peterson <speterson@nvidia.com>
Reviewed-on: http://git-master/r/226353
Reviewed-by: Vinod Subbarayalu <vsubbarayalu@nvidia.com>
GVS: Gerrit_Virtual_Submit
|