Age | Commit message (Collapse) | Author |
|
With check from!=to it remains on when device is resumes and usb cable state is
not changed. Always disable the usbd clock after work is done.
Bug 812197
Change-Id: Id0f4bfc6d4eb8f82e010de35594720fc82bd77c4
Reviewed-on: http://git-master/r/27147
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Change-Id: I1f85b4ed49128a261b29bb7c3ffe8c5d511a44f9
|
|
Error-diffusion dithering on Tegra would never be enabled in video modes
where horizontal width exceeded 640 pixels. For large screen, either
24bit ture color or ordering dither may be used since it does not
require a line buffer.
Change-Id: If60a64858506ee96d444cb2cb3dcf7a1fbce5b1d
Reviewed-on: http://git-master/r/17393
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Change-Id: I0dea4f256442d7391808de8456fe35d3879682fe
|
|
use tegra_nvhdcp_on/tegra_nvhdcp_off in hotplug handler to clean up
state machine.
Change-Id: I62fe503f0628ad4b49d5d7d66fe1702122179877
Signed-off-by: Erik Gilling <konkers@android.com>
|
|
Change-Id: If54be4c2e106e24beb0ae3063156a0659fcbb943
|
|
use 3 seconds for i2c/ddc failures on hdcp (15 attempts at 250mS each)
Change-Id: Ia755c9b42d5a0d8467b68c9d334638bcb015eabd
Signed-off-by: Erik Gilling <konkers@android.com>
|
|
Change-Id: If9efc63de3427f263b121e102cd0168883a236a3
Signed-off-by: Erik Gilling <konkers@android.com>
|
|
Generated with the script:
find \( -name "*.c" -or -name "*.h" -or -name "*akefile" -or \
-name "*\.mk" \) -type f -perm /+x | xargs chmod -x
Change-Id: Iabae1aa20fd49a1c8db439fc132182d0f629deab
Reviewed-on: http://git-master/r/26806
Reviewed-by: Robert Morell <rmorell@nvidia.com>
Tested-by: Robert Morell <rmorell@nvidia.com>
Reviewed-by: Janne Hellsten <jhellsten@nvidia.com>
|
|
fb_videomode_to_var doesn't fill out all the
members of fb_var_screeninfo. So, we need to
perform memset before calling the function
Bug 808273
Reviewed-on: http://git-master/r/24430
(cherry picked from commit 17de002a0ff09138c9db244cb200380ba38f4033)
Change-Id: Id4d2975fa2b887e97601f1aee8304465aecc7cc2
Reviewed-on: http://git-master/r/26669
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Tested-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Minimum voltage for LDO0 was specified with a code construct,
better solve this with a voltage table. This avoids a warning
in kernel log, too.
Bug 798821
Change-Id: I706276a9aae3359006ddc7fe9134b67e00ec34fd
Reviewed-on: http://git-master/r/25185
Reviewed-by: David Schalig <dschalig@nvidia.com>
Tested-by: David Schalig <dschalig@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
New i2c slave should be configured with a non-zero i2c address.
Configure i2c slave with an i2c address assigned by platform
data for an i2c dev.
BUG 788286
Reviewed-on: http://git-master/r/25100
(cherry picked from commit e6e0610c72ffce3b734e079faf88fad3f0468d07)
Change-Id: I440aa2cc72007d2835b2027c0b26089d0aad9263
Reviewed-on: http://git-master/r/25223
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Detect vbus and enable clock for usb otg using the interrupt received in
usb phy. usb phy interrupt is configured to max8907c usb detect interrupt to
get event for usb insertion when otg is suspended.
Bug 806949
Change-Id: I73fb92534ce5ae8d1ea39dfe756f940b89af7d79
Reviewed-on: http://git-master/r/24684
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Using a factor of two to increase the emc frequency required by
the display panel to prevent underflow.
Bug 800993
Change-Id: Ibb60a88a4efb384bce6f1277022b335540f11a2e
Reviewed-on: http://git-master/r/24862
Reviewed-by: Wen Yi <wyi@nvidia.com>
Tested-by: Wen Yi <wyi@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
There is a race condition between fb_blank and pwm_update_status
that could cause kernel panic. The solution is to synchronize
the function tegra_dc_config_pwm with dc->lock.
Bug 803498
Change-Id: I9323cb223aa8feb92f56d0025b2d97ab3b8d1752
Reviewed-on: http://git-master/r/23776
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
|
|
clients call the algorithm's close api, which
results in the algo's cra_exit getting called, when
they are done using the hardware. we need to free the
key slot which was being used by the client when its
cra_exit is called.
Change-Id: Ib42d445f5068c4ea1ef6b3edbbc547fe9eeef583
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/24673
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Conflicts:
drivers/serial/tegra_hsuart.c
drivers/usb/host/ehci-tegra.c
Change-Id: Ief6c03a63615a41e85de59ad14dedef309d0b2fb
|
|
|
|
Change-Id: Iba5041f8428b13791004c96e6e8c2ed4dbcc37b8
Signed-off-by: Erik Gilling <konkers@android.com>
|
|
Wait for Start Of Frame interrupt, then wait 20 us, before starting
port resume. Workaround for hardware issue that can cause the SOF to
be sent out at the same time as the phy speed change.
Change-Id: I91ccbd2902448e87aa3cdf1970305de22efa1c10
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Change the emc frequency using number of overlays and the frequency
of the display panel.
Bug 800993
Change-Id: I30ef2edd1ed9b43afa8c38b0f05b5d6e49b7f892
Reviewed-on: http://git-master/r/24052
Reviewed-by: Amit Kamath <akamath@nvidia.com>
Reviewed-by: Wen Yi <wyi@nvidia.com>
Tested-by: Wen Yi <wyi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Matthew Longnecker <mlongnecker@nvidia.com>
|
|
In the function tegra_otg_probe(), usbd clock is kept on
after probe function completes. Fix this by disabling the clock
before exiting the probe function.
Bug 803498
Change-Id: I1aa7621f9dfcba1a249cc6d08a23b4106db3c1f2
Change-Id: I3da69f72a312243b3c869543de3f841588bcce89
Reviewed-on: http://git-master/r/23207
Reviewed-by: Wen Yi <wyi@nvidia.com>
Tested-by: Wen Yi <wyi@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
In case of inband interrupts i.e SDIO CARD INT, two
level of thread switching takes place to process wifi
interrupts one in SDHCI and the other in Wifi driver if
"SDIO_ISR_THREAD" flag is disabled.
Enabling "SDIO_ISR_THREAD" flag will prevent deferred
MAC interrupts processing because it is preventing thread
context switching in wifi driver.
Bug 789444
Bug 787054
Bug 795460
Change-Id: I4b00b5a1a3127380699c958d802e5d823078896e
Reviewed-on: http://git-master/r/24273
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
If the device isn't registered for this board, return out of the init
function early.
Change-Id: Ic806b4be1671a77a8fedc1c0376362bc177b0604
Reviewed-on: http://git-master/r/24254
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Tested-by: Daniel Willemsen <dwillemsen@nvidia.com>
Reviewed-by: Anantha Idapalapati <aidapalapati@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Add UART_CAP_HW_CTSRTS flag to tegra type for supporting auto control
of RTSCTS.
Bug 803910
Change-Id: I7b69e4b203e66903ba5755338fcb55f4a87b9a43
Reviewed-on: http://git-master/r/24463
Tested-by: Pradeep Goudagunta <pgoudagunta@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Initiate broadcast scan (active scan) just after
initializing with network interface.
BUG 781501
Change-Id: I6c9bc7b458fff604c12ea3c94c4d4a5255b3bb91
Reviewed-on: http://git-master/r/23216
Reviewed-by: Rahul Bansal <rbansal@nvidia.com>
Tested-by: Rahul Bansal <rbansal@nvidia.com>
Reviewed-by: Rakesh Kumar <krakesh@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Use new cam_i2c slave (i2c2) instead of the legacy one.
With old i2c slave controller, occasionally it generates
spurious slave interrupts causing disruptions in i2c transfers.
BUG 790315
Reviewed-on: http://git-master/r/24287
(cherry picked from commit 001805e9036b647e9a1220f2b50e8973ec28e917)
Change-Id: Icd5310286de0338a4458c26a8d491bcded032b03
Reviewed-on: http://git-master/r/24294
Tested-by: Nitin Kumbhar <nkumbhar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Write protection was disabled in K36. Enabling this feature by
storing the write protection GPIO pin number (wp_gpio) from
platform_data for the device and reading this GPIO (whenever the
card is inserted) to determine whether the card is write protected
or not.
Bug 686892.
Change-Id: I6f1855b7b974caaa5ea58aaee3881d85d5da6c18
Reviewed-in: http://git-master/r/#change,21101
Reviewed-on: http://git-master/r/23971
Reviewed-by: David Schalig <dschalig@nvidia.com>
Tested-by: David Schalig <dschalig@nvidia.com>
Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
tegra2 has an improved new i2c slave controller. This should be
used instead of the old i2c slave controller. With old i2c slave
controller, occasionally it generates spurious slave interrupts
causing disruptions in master i2c transfers.
BUG 788286
BUG 804545
Reviewed-on: http://git-master/r/24107
(cherry picked from commit 64a6e1d5a555be1c330de80cfb477563ae061452)
Change-Id: Id5d5bd809df4a583a743d84a91aecbb78889a3c6
Reviewed-on: http://git-master/r/24246
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
- fix an incorrect i2c address and a function return check.
- add checks for function returns.
- remove the developer name in the beginning comment.
- fix an uninitialized variable..
Change-Id: I2d42025b7ff47eb6228e626e65990f4da04b94ac
Reviewed-on: http://git-master/r/23594
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
Tested-by: Qinggang Zhou <qzhou@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
|
|
bug 802909
Change-Id: I061eb7082b251ef6963e2a68fd9821122e010966
Reviewed-on: http://git-master/r/23871
Reviewed-by: Peter Zu <pzu@nvidia.com>
Tested-by: Peter Zu <pzu@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|
|
Change-Id: I82081f6e4e3646fbf7c265851e548ca64b2415db
Reviewed-on: http://git-master/r/23760
Tested-by: Thomas Cherry <tcherry@nvidia.com>
Reviewed-by: Chih-Lung Huang <lhuang@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Kevin Huang <kevinh@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
|
|
During suspend/resume wifi chip's power mode is changed and this
impacts chip's internal registers reading/writing. Delaying reads/
writes to wifi chip from HZ/100 to 3*HZ which gives time for chip
to settle its state.
BUG 798783
Change-Id: Ie9c06c2d03fb38b6fba5acca48490d12c358e496
Reviewed-on: http://git-master/r/22150
Reviewed-by: Rahul Bansal <rbansal@nvidia.com>
Tested-by: Rahul Bansal <rbansal@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Changing the sysfs ehci permissons as per new requirments.
Reviewed-on: http://git-master/r/23516
(cherry picked from commit bbdaff2129511b1849d3252429b001435e7da501)
Change-Id: I7573313094f00c266ba7ac5e098124a0d7f23420
Reviewed-on: http://git-master/r/23640
Tested-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
In systems with multiple framebuffer devices, one of the devices might
be blanked while another is unblanked. In order for the backlight
blanking logic to know whether to turn off the backlight for a
particular framebuffer's blanking notification, it needs to be able to
check if a given framebuffer device corresponds to the backlight.
This plumbs the check_fb hook from core backlight through the
pwm_backlight helper to allow platform code to plug in a check_fb hook.
Originally reviewed on http://git-master/r/21716
Reviewed-on: http://git-master/r/23100
(cherry picked from commit c7831cb27fc6a2701b020676a6daf9c76e9470d9)
Change-Id: I32895d6f2c5988b09680a350e169f1f3c9b56da6
Reviewed-on: http://git-master/r/23725
Reviewed-by: Robert Morell <rmorell@nvidia.com>
Tested-by: Gaurav Sarode <gsarode@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
The intensity of the backlight can be varied from a range of
max_brightness to zero. Though most, if not all the pwm based backlight
devices start flickering at lower brightness value. And also for each
device there exists a brightness value below which the backlight appears
to be turned off though the value is not equal to zero.
If the range of brightness for a device is from zero to max_brightness. A
graph is plotted for brightness Vs intensity for the pwm based backlight
device has to be a linear graph.
intensity
| /
| /
| /
|/
---------
0 max_brightness
But pratically on measuring the above we note that the intensity of
backlight goes to zero(OFF) when the value in not zero almost nearing to
zero(some x%). so the graph looks like
intensity
| /
| /
| /
| |
------------
0 x max_brightness
In order to overcome this drawback knowing this x% i.e nothing but the low
threshold beyond which the backlight is off and will have no effect, the
brightness value is being offset by the low threshold value(retaining the
linearity of the graph). Now the graph becomes
intensity
| /
| /
| /
| /
-------------
0 max_brightness
With this for each and every digit increment in the brightness from zero
there is a change in the intensity of backlight. Devices having this
behaviour can set the low threshold brightness(lth_brightness) and pass
the same as platform data else can have it as zero.
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Arun Murthy <arun.murthy@stericsson.com>
Acked-by: Linus Walleij <linus.walleij@stericsson.com>
Acked-by: Richard Purdie <rpurdie@linux.intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Reviewed-on: http://git-master/r/23099
(cherry picked from commit 92db79791aa60cacb3fa90d1cb2e942420c29408)
Change-Id: Icbe49b593dfa6608934ff274b4c9281e43c30b5c
Reviewed-on: http://git-master/r/23724
Tested-by: Gaurav Sarode <gsarode@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@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.
Change-Id: Ia33433a677862b3d1e31d410aac7176d7a381a8f
Reviewed-on: http://git-master/r/22987
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
|
|
Make sure that the last byte has been received by the uart during
suspend after RTS is deasserted.
Change-Id: I3517ec058fdca912ff5ad8770d2b1c5015385385
Signed-off-by: Andrei Warkentin <andreiw@motorola.com>
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Change-Id: I48cccf5b0df768b9cfc774803f3945f4806a62ac
|
|
Updates the tegra_hsuart driver to match the changes in the Tegra
dma engine.
Change-Id: Iaaf8770166156c1a6d889a6a11bae517626781ee
Signed-off-by: Colin Cross <ccross@android.com>
|
|
Opening the Tegra WDT device from user space is causing the kernel
panic. It is found that the device file private data pointer is passing
incorrectly in the orignal code.
bug 786885
Change-Id: I4646b02c5a804c07d05ba01e35034408cc8e3e4e
Reviewed-on: http://git-master/r/23629
Reviewed-by: Xin Xie <xxie@nvidia.com>
Tested-by: Xin Xie <xxie@nvidia.com>
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
|
|
|
|
In debug prints for stuck WAITs differentiate WAIT_SYNCPT
vs. WAIT_SYNCPT_BASE and fix some build warnings.
Change-Id: Ia47375614c676a9f93216fbfaaf6856c3df42e2e
Signed-off-by: Chris Johnson <cwj@nvidia.com>
|
|
This reverts commit be7b9ce20d645c2c9293441830ee33a0a5fc489f.
|
|
Change-Id: I517760af5756279b41836062063bdcaa04e5bfef
|
|
video:tegra:nvmap: Clean whole L1 instead of cleaning by MVA
For large allocations, cleaning each page of the allocation can
take a significant amount of time. If an allocation that nvmap needs
to clean or invalidate out of the cache is significantly larger than
the cache, just flush the entire cache by set/ways.
bug 788967
Reviewed-on: http://git-master/r/19354
(cherry picked from commit c01c12e63b1476501204152356867aeb5091fb80)
tegra:video:nvmap: optimize cache_maint operation.
optimize cache_maint operation for carveout and heap memories.
flush carveout memory allocations on memory free.
Bug 761637
Reviewed-on: http://git-master/r/21205
Conflicts:
drivers/video/tegra/nvmap/nvmap_dev.c
drivers/video/tegra/nvmap/nvmap_heap.c
drivers/video/tegra/nvmap/nvmap_ioctl.c
(cherry picked from commit 731df4df5e895e1d4999359d6d5939fc2095f883)
tegra:video:nvmap: optimize cache flush for system heap pages.
optimize cache flush for pages allocated from system heap.
Bug 788187
Reviewed-on: http://git-master/r/21687
(cherry picked from commit 3f318911ad91410aed53c90494210e2b8f74308b)
Change-Id: Ia7b90ba0b50acfef1b88dd8095219c51733e027f
Reviewed-on: http://git-master/r/23465
Reviewed-by: Kirill Artamonov <kartamonov@nvidia.com>
Tested-by: Kirill Artamonov <kartamonov@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
I2C driver needs to be suspended late and resumed early than other drivers.
So, I2C driver uses the suspend_noirq/resume_noirq callbacks of struct dev_pm_ops
for early/late power management system.
Change-Id: Ie2f453b96fb9ab9b16cafec79644fe5d3b982dd3
Reviewed-on: http://git-master/r/23347
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Jinyoung Park <jinyoungp@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Implement functions needed in struct mmc_host_ops to support
enable/disable SDCLK dynamically.
Add SDHCI_QUIRK_RUNTIME_DISABLE to switch on/off this feature.
Bug 800655
Change-Id: I4c71ca4beb56df020381236ca8ec949647a0d333
Reviewed-on: http://git-master/r/23125
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Correct PRE_BYPASS (clock scaler 32kHz/1kHz select) bitfield.
Add platform data to tune RTC XTAL capacitance in board file.
Bug 798832, Tested on Ventana/wake via Alarm Clock
Change-Id: I82d67610a815866707fc1db934d7d4d7cf93d883
Reviewed-on: http://git-master/r/22402
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
Reviewed-by: David Schalig <dschalig@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|