Age | Commit message (Collapse) | Author |
|
fb_mmap maps current window so that content of screen is
accessible through mmap sys call to user space components.
BUG 832288
Change-Id: I10ccb0b70c951f6d43dbd8a7a1e59e86c0ee75e9
Reviewed-on: http://git-master/r/39204
Reviewed-by: Manish Tuteja <mtuteja@nvidia.com>
Tested-by: Manish Tuteja <mtuteja@nvidia.com>
|
|
Dvc I2C_DONE_INTR_EN interrupt bit is always enable into dvc
control register3.During normal transaction on dvc i2c bus
sometimes one transaction written two times in TX fifo buffer
because of triggered dvc interrupt.This is causing to corrupt
the next transaction header and send wrong address over dvc
i2c bus.To solve this issue dvc i2c interrupt has to disable
during filling of Tx fifo and enable after that.
Writing last packet into Tx Fifo is generating i2c interrupt
immediately if IE bit is enable in Packet header. Data shared
between isr and normal thread are not in sync. So alway update
these data before writing into Tx fifo.
Updated the following things in code:
(1) Add the code to mask/unmask I2C_DONE_INTR_EN into dvc control reg3
(2) Always updates the i2c driver required field structure data before
writing into Tx Fifo register.
(3) Add the code to handle tx fifo overflow condition also.
(4) Put delay before resetting the controller
BUG 839528
Change-Id: I7780411b474a20f985e1f7993e5ccccbab619bbc
Reviewed-on: http://git-master/r/39985
Reviewed-by: Alok Chauhan <alokc@nvidia.com>
Tested-by: Alok Chauhan <alokc@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
|
|
BUG_ON() function has wrong comparision.
the comparision should be '>='. (not '>')
Change-Id: I39453cc02615236b52aa04be076184da35df8e94
Reviewed-on: http://git-master/r/39503
Reviewed-by: BK Kim <bkk@nvidia.com>
Tested-by: BK Kim <bkk@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
-Setting the minimum clock at enabling clock
-Enabling controller clock before MMC_POWER_UP to ensure
proper register read/write
-Limit max sdio clk to 24MHz for wifi on whistler.
whistler only supports up to 24MHz.
bug 834281
bug 845180
Change-Id: I9993a8bd9ab99af21c81d42f91175279f91cf0e4
Reviewed-on: http://git-master/r/39525
Tested-by: Harry Hong <hhong@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@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 if usb hotplug is not enabled.
Bug 829628
Change-Id: I2ec96fedb2ed04a9c39f3c7d34cb86fdac821822
Reviewed-on: http://git-master/r/39354
Reviewed-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
|
|
Disable usb clock when no cable is connected.
Bug 829628
Change-Id: Idabe72093ae1fc1a236b0173da93813f07f3501c
Reviewed-on: http://git-master/r/39353
Reviewed-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
|
|
Added support for auto control of RTS.
Bug 825938
Change-Id: Id6f8a26f2178acb9dd8c54069fde4dd879e9d5f1
Reviewed-on: http://git-master/r/39363
Tested-by: Pradeep Goudagunta <pgoudagunta@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
|
|
Avoid Display Controller (DC) syncpoint increments if that instance of DC is
not enabled.
Bug 793874
(cherry picked from commit 5be1dd4dd04db4a4c4e8004e364d504bf9f56857)
Change-Id: I91f05694044bbefb15c3b92047be3be47b2ceacc
Reviewed-on: http://git-master/r/38464
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
|
|
dc lock is head while flush occurred, but functions called by workers need
take the dc lock to proceed.
Bug 807015
(cherry picked from commit 2e12d89ac51fe1358f0b01b9ff5cb4978fdcbe9d)
Change-Id: Ib358685c478c05a8f95c926e708de12b6a3556fb
Reviewed-on: http://git-master/r/38463
Reviewed-by: Linqiang Pu <dpu@nvidia.com>
Tested-by: Linqiang Pu <dpu@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|
|
Finding the best clock source for uart controller which can
generate the clock rate having minimum error between requested
baudrate and configured baudrate.
bug 842665
Change-Id: I9a750f578f7dfd7ea2138fdf1bcec30b0f3392d5
Reviewed-on: http://git-master/r/38426
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Pradeep Goudagunta <pgoudagunta@nvidia.com>
Reviewed-by: Bitan Biswas <bbiswas@nvidia.com>
|
|
HDMI connect/disconnect will not affect the suspended device.
bug 835157
Change-Id: Ie094a2dcebdca2e405f3e02b4de3d12d0cb665f0
Signed-off-by: Sanjay Singh Rawat <srawat@nvidia.com>
Reviewed-on: http://git-master/r/37174
(cherry picked from commit 31f69bbe2e832a7dfa7678bb965b3461f421e0f5)
Reviewed-on: http://git-master/r/38089
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|
|
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Change-Id: I32755368de7059a8aa08b114af84d952adf16a1d
Reviewed-on: http://git-master/r/37981
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
To support the 25.2MHz pixel clock frequency required for CEA-861-B format 1: 640x480p at 59.94Hz
bug 837571
Change-Id: I33d5c82bbc9c79fd43d86abf72d5b94b1c723dd5
Reviewed-on: http://git-master/r/37916
Reviewed-by: Joseph Lehrer <jlehrer@nvidia.com>
Tested-by: Joseph Lehrer <jlehrer@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|
|
Fix incorrect invocation of mutex_destroy that results in a compile
error if mutex debugging features are enabled.
Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Change-Id: I4f5ce4406e11b94d108f0e0b09b2d4a77d902ac6
Reviewed-on: http://git-master/r/37435
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Multiple GetPortStatus requests can be made while the
USB bus is resuming. All requests must be handled
properly to prevent incorrect disconnect detection
during Resume and improper indentification of
Resume signaling as a remote wakeup event.
Bug 817128
Signed-off-by: Nathan Connell <w14185@motorola.com>
Reviewed-on: http://git-master/r/36311
(cherry picked from commit f4cd754c1af2bbc2101dd208fd4d3d0bf6368d26)
Change-Id: I5e4a7aeaef97f0416ff8ea32e6391fe8450e4c26
Reviewed-on: http://git-master/r/37413
Reviewed-by: Manish Tuteja <mtuteja@nvidia.com>
Tested-by: Manish Tuteja <mtuteja@nvidia.com>
|
|
This incorrect condition adds sleep to i2c read & write
functions even though they are executed successfully.
Bug 831891
Change-Id: If029b16c724516e96bf75458c60ca6b411ab5a96
Reviewed-on: http://git-master/r/37463
Reviewed-on: http://git-master/r/37472
Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com>
Tested-by: Pritesh Raithatha <praithatha@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
usbcore will reenable usb interrupts later once the bus has been
resumed.
bug 835193
Signed-off-by: Benoit Goby <benoit@android.com>
Reviewed-on: http://git-master/r/36145
(cherry picked from commit 1ffaaac2463f94ad1056abfa345f6e50249ec1c4)
Change-Id: Iee7f29ad5ec409fa563742c505b448f5cbdf3c81
Reviewed-on: http://git-master/r/37412
Tested-by: Cho-Che Cheng <jacheng@nvidia.com>
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
usbcore will change it once the bus has been resumed. This fixes
the "hub 3-0:1.0: activate --> -22" error on resume.
bug 835193
Signed-off-by: Benoit Goby <benoit@android.com>
Reviewed-on: http://git-master/r/36144
(cherry picked from commit bce8ee9ee177c2c4af21f3275b6472e68a13850e)
Change-Id: I08b7485f68e4e9a1e91c37e35a65d037a4e30879
Reviewed-on: http://git-master/r/37411
Tested-by: Cho-Che Cheng <jacheng@nvidia.com>
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
The prefetcher fetches a total of 128 bytes, and then responding to
sequential reads with this prefetched data. To avoid coherency issues,
it discards the prefetched data if a non sequential read occurs.
Allocate dtd with 128 bytes boundary to make 2 consecutive dtd 128 bytes
apart.
bug 825970
Reviewed-on: http://git-master/r/36157
(cherry picked from commit bf623c5edbc8f0f5b23d5580aea1038418893792)
Change-Id: I6cc977545aee1bec1c91e4085cc2b3b55acccdb5
Reviewed-on: http://git-master/r/37410
Tested-by: Cho-Che Cheng <jacheng@nvidia.com>
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
HDMI clock is not auto dvfs, so we need set the clock rate to 0 if HDMI
is disabled. Otherwise the Vdd core voltage will be always 1.2v even
after HDMI cable unplugged.
BUG 828306
Reviewed-on: http://git-master/r/34379
(cherry picked from commit 58ddd144a6c2dd9bbc9d2f3c8b1e025364d88c22)
Change-Id: I5b455a7a945d4834fb162b2986639df5a26b112c
Reviewed-on: http://git-master/r/37176
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
|
|
Defer the SET_CONFIG and SET_INTERFACE control transfer's data/status
stages till we are ready to process new CBW from the host. This way we
ensure that we don't loose any CBW during MSC compliance tests and cause
lock up.
(cherry picked from commit 95ed32366748e2034e82c9e738c312df8fb3d3a9)
Change-Id: Ib8c7140d11f558c969802558476ff6013aae3269
Reviewed-on: http://git-master/r/36275
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
|
|
If defered SD card resume (CONFIG_MMC_BLOCK_DEFERRED_RESUME) is enabled,
PM_POST_SUSPEND handler will never set host->rescan_disable back to 0,
and card detect logic will be disabled forever.
fix missing break
fix incorrect cleanup sequences
Bug 833034
http://git-master/r/#change,36251
(cherry picked from commit 31d509d8e2e2b7c35da69029f932d35c3995fe36)
Change-Id: I3e513359af68e92476d693f4d1751b4b0d883569
Reviewed-on: http://git-master/r/36429
Reviewed-by: David Schalig <dschalig@nvidia.com>
Tested-by: David Schalig <dschalig@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Some USB function drivers (e.g. f_mass_storage.c) need to delay or defer the
data/status stages of standard control requests like SET_CONFIGURATION or
SET_INTERFACE till they are done with their bookkeeping and are actually ready
for accepting new commands to their interface.
They can now achieve this functionality by returning USB_GADGET_DELAYED_STATUS
in their setup handlers (e.g. set_alt()). The composite framework will then
defer completion of the control transfer by not completing the data/status stages.
This ensures that the host does not send new packets to the interface till the
function driver is ready to take them.
When the function driver that requested for USB_GADGET_DELAYED_STATUS is done
with its bookkeeping, it should signal the composite framework to continue with
the data/status stages of the control transfer. It can do so by invoking
the new API usb_composite_setup_continue(). This is where the control transfer's
data/status stages are completed and host can initiate new transfers.
The DELAYED_STATUS mechanism is currently only supported if the expected data phase
is 0 bytes (i.e. w_length == 0). Since SET_CONFIGURATION and SET_INTERFACE are the
only cases that will use this mechanism, this is not a limitation.
(cherry picked from commit 1b9ba000177ee47bcc5b44c7c34e48e735f5f9b1)
Change-Id: I4aaf702e03898573f92e58223a29eafbc9612219
Reviewed-on: http://git-master/r/36273
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
|
|
The ep0 request tag was not recorded thus resulting in phase
problems while sending status/response in handle_execption() handler.
This was resulting in MSC compliance test failures with USBCV tool.
With this patch, the Bulk-Only Mass storage RESET request is
handled correctly and the MSC compliance tests pass.
(cherry picked from commit 73ee4da994e7b97bd8241e39099cf3dd94675d79)
Change-Id: Ia5beffe1e38b518b63b80dda36faf06b86f7a6cb
Reviewed-on: http://git-master/r/36274
Tested-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
|
|
during system suspend if wifi is on but not connected, android
sets RTC alarm to wake up system after 2 mins of system suspend
to turn off wifi. during turning off wifi it was observed that
BCM4329 MAC is giving spurious sdio interrupts which was causing
lockup issue (mmc_lock) between sdio interrupt handling process
and wifi stop process, to fix this issue sdio interrupts are
disabled before giving MAC reset from host.
Bug 834444
Bug 798783
Bug 796147
Bug 797230
Bug 780047
Bug 818687
Change-Id: I98ac26ca8951bb9f32dcff06e096d1ac9c9e3788
Reviewed-on: http://git-master/r/36755
Reviewed-by: Rahul Bansal <rbansal@nvidia.com>
Tested-by: Rahul Bansal <rbansal@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Initialize avp.sclk to minimum. H/W statistics monitor adjusts
avp.sclk dynamically depending on load.
Bug 831892
Change-Id: Ib540cc1de4f2e05f335d89fa145f984a581762d6
Reviewed-on: http://git-master/r/36064
Reviewed-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
There was no code to clear interrupt registers for AVP. First run
of AVP was OK because those registers start from reset value.
But because those registers were not cleared, when the second
time AVP was started, some interrupts were enabled too early.
That caused interrupts coming before handlers were ready.
This change also removes the workaroud for the bug.
bug 827353
bug 826234
Change-Id: Ia45efe1d5f2c48d8d372a2442a614d52f1a766c0
Reviewed-on: http://git-master/r/33083
Reviewed-on: http://git-master/r/35357
Reviewed-by: Kaz Fukuoka <kfukuoka@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
hdcp worker could be in sleep during modeset.
The front part of the video could be lost because of it.
This change makes hdcp respond quickly to shorten the delay.
bug 826468
Reviewed-on: http://git-master/r/#change,35449
Change-Id: I4e0105b1bc5815b223810d23ca8595747e541ee6
Reviewed-on: http://git-master/r/36417
Tested-by: Seongho Joo <sjoo@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
1. fix dc hang during dc reset
2. do dc reset after dc clk enabling
in reset worker function
3. remove a few build warnings
Bug 801463
Change-Id: Icc85b09ae5cf5ab97839ae8625224ea2b163adb4
Reviewed-on: http://git-master/r/33112
Reviewed-on: http://git-master/r/36235
Reviewed-by: Min-wuk Lee <mlee@nvidia.com>
Tested-by: Min-wuk Lee <mlee@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Hyong Bin Kim <hyongbink@nvidia.com>
|
|
Some windows host drivers require this small delay in order to properly
detect the tegra device. This patch ensures correct detection in all
cases.
Workaround for bug 814907
(cherry picked from commit 53c4f00605677c8de4311586c4f75903978cbd94)
Change-Id: Ib950c39bc6f28e28793ef655e0bb9e04ebb39942
Reviewed-on: http://git-master/r/35613
Reviewed-by: Alex Courbot <acourbot@nvidia.com>
Tested-by: Alex Courbot <acourbot@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Signed-off-by: Mike Lockwood <lockwood@android.com>
(cherry picked from commit 663abba4c6d83e798d1479298130f34a28dacd8b)
Change-Id: I5d1b01fa6e8856c929d13abfa38db732115e9ddc
Reviewed-on: http://git-master/r/32892
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Signed-off-by: Mike Lockwood <lockwood@android.com>
(cherry picked from commit 99b7fdff26bdaa2dbdecd45db18834f9d7447632)
Change-Id: Ic4e663abf1a3c6d0ea21983f5e2171a34c0e6641
Reviewed-on: http://git-master/r/32891
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Fixes a race condition that can occur when entering accessory mode.
Signed-off-by: Mike Lockwood <lockwood@android.com>
(cherry picked from commit 2fc14f8dab1032958d2522576607f4a92abc3e3d)
Change-Id: I3918f9351a7725783df7e7726d53fdbc0aff5b6c
Reviewed-on: http://git-master/r/32890
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Clearing strings on disconnect does not work since we may receive
a disconnect on some devices when transitioning into accessory mode.
We require an accessory to send ACCESSORY_GET_PROTOCOL before
sending any strings, so any strings from a previous session will be cleared.
Signed-off-by: Mike Lockwood <lockwood@android.com>
(cherry picked from commit 30e18b848c25d4a90e3b6282cd32e19a2f0cd4dc)
Change-Id: I4c7575508fba294cfe1ce86148ed6c09f98cc03c
Reviewed-on: http://git-master/r/32889
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Signed-off-by: Mike Lockwood <lockwood@android.com>
(cherry picked from commit 6c778587651da91039ad09dea4a93988f1736843)
Change-Id: Ib5acd2ced156417b97d956e5baa11e801e14a491
Reviewed-on: http://git-master/r/32888
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
- Add URI string
- Replace type string with a description string
- Add a control call to retrieve accessory protocol version (currently 1)
- Driver read() and write() calls now fail after USB disconnect until
driver file is closed and reopened.
- Misc cleanup work
Signed-off-by: Mike Lockwood <lockwood@android.com>
(cherry picked from commit 5dcd55b2e98ffdaf54a5cdd67a3101e1e5dd3aa1)
Change-Id: I5b45ee76d5f83b626555e42d34f450db9b69f47b
Reviewed-on: http://git-master/r/32887
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Signed-off-by: Mike Lockwood <lockwood@android.com>
(cherry picked from commit 5826bb3c467116287087703472261f51f71ca090)
Change-Id: I6d66f0e6ff137467f8656d28f1107d7478a22720
Reviewed-on: http://git-master/r/32886
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Based on the polarity of the card detect gpio,
update the card present status for sd cards to
be properly detected and enumerated.
Bug 831409
Change-Id: I7d0514ba61a1f418ecf2603e12fa99fb9d748dbe
Reviewed-on: http://git-master/r/33124
Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Tested-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Joseph Lehrer <jlehrer@nvidia.com>
Tested-by: Joseph Lehrer <jlehrer@nvidia.com>
|
|
uart_update_termios is called on console resume and restores the line
parameters using cons->cflag before resetting it. However code in
uart_resume_port does the same afterwards, applying a 0 value to the
port's cflag and erasing the correct setting. This patch preserves the
value of cflag in uart_update_termios to prevent this and allow the
serial console to restore properly even if there is no program using it
on user side.
Serial code has been largely refactored upstream in the upstream kernel
and faulty code apparently removed.
Fixes bug 831077
Change-Id: Ia894f971d9b6bb0c6103dbca9d169dc2a2148f84
Reviewed-on: http://git-master/r/33098
Reviewed-by: Alex Courbot <acourbot@nvidia.com>
Tested-by: Alex Courbot <acourbot@nvidia.com>
Reviewed-by: David Schalig <dschalig@nvidia.com>
Reviewed-by: Janne Hellsten <jhellsten@nvidia.com>
|
|
Change-Id: I035a6cd254342fe11f074cb85439f378a7675943
Signed-off-by: Michael I. Gold <gold@nvidia.com>
Reviewed-on: http://git-master/r/33038
Reviewed-by: Brian Anderson <branderson@nvidia.com>
|
|
Change-Id: I6ec62abdaf3a8ec2e59e2a533b36b280d69538e1
Signed-off-by: Ari Hirvonen <ahirvonen@nvidia.com>
Reviewed-on: http://git-master/r/33037
Reviewed-by: Michael I Gold <gold@nvidia.com>
Tested-by: Michael I Gold <gold@nvidia.com>
|
|
PortConnectionDetect to be cleared if the usbphy clock interrupt is set.
The USB plugin detection is done appropriately without missing
cableconnect event.
Bug 825920
Change-Id: I4400f208f405a110fff48f1fea777b472aacce62
Reviewed-on: http://git-master/r/32599
Tested-by: Alex Courbot <acourbot@nvidia.com>
Reviewed-by: Alex Courbot <acourbot@nvidia.com>
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
|
|
unlock mutex if reset worker finds the display disabled.
Bug 801463
Reviewed-on: http://git-master/r/29898
(cherry picked from commit 672459efb81140b496e3749f1b1b14dcf84af74d)
Change-Id: I94254fca387cddcd58166757e46422167ed9262d
Reviewed-on: http://git-master/r/32758
Reviewed-by: Min-wuk Lee <mlee@nvidia.com>
Tested-by: Min-wuk Lee <mlee@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|
|
Enabling SDHCI_QUIRK_BROKEN_CARD_DETECTION. For non-
removable cards, always set card_present as true.
Bug 827470
Change-Id: I1148984e4dff314173b88373e1494379abce31f3
Reviewed-on: http://git-master/r/31990
Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Tested-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Added card_detect callback in sdhci_ops. When
SDHCI_QUIRK_BROKEN_CARD_DETECTION is enabled,
get the card present status from this callback.
Bug 827470
Change-Id: Ifdd9576ff4e33a4be4c32a57e2d49d692ec95f36
Reviewed-on: http://git-master/r/31987
Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Tested-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Removes changes to DC reset flow introduced in commit e9f069bc2c9e0a9e3d7dfd30b66367667ab82dee.
Fixes the issue of HDMI output after playing 1080p stream.
bug 820455
bug 826061
Change-Id: I9c0802c4c39d4f899e948e8020a721699634d84c
Reviewed-on: http://git-master/r/31959
Reviewed-by: Niket Sirsi <nsirsi@nvidia.com>
Tested-by: Niket Sirsi <nsirsi@nvidia.com>
|
|
use smaller h_ref_to_sync values.
removed old debug printks
Bug 806009
(cherry picked from commit 8292b4988e6aa75c71f14cbf96dad8b5e931e681)
Change-Id: Iae3e84ddd8c02be1a83f9ac255fc1152dc867f0b
Reviewed-on: http://git-master/r/30585
Reviewed-by: Niket Sirsi <nsirsi@nvidia.com>
Tested-by: Niket Sirsi <nsirsi@nvidia.com>
|
|
Change-Id: I8ee718e0d56ff8dc2f2c2e1b5215d195f317f0e2
Reviewed-on: http://git-master/r/31084
Reviewed-by: Niket Sirsi <nsirsi@nvidia.com>
Tested-by: Niket Sirsi <nsirsi@nvidia.com>
|
|
Return last requested position if the motor settled or timeout occurs.
Reviewed-on: http://git-master/r/27978
(cherry picked from commit edb393adc0317a097858edeb4b9f5477d164b955)
Change-Id: I54572b180bf151785d55edde9060876ed0393ee3
Reviewed-on: http://git-master/r/31741
Reviewed-by: Frank Chen <frankc@nvidia.com>
Tested-by: Gary Zhang <garyz@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Gary Zhang <garyz@nvidia.com>
|
|
tegra_dc_hdmi_equal doesn't check pixclock. some devices doesn't
support 14.85Mhz pixclock so 1080p@60 cannot be used. However,
1080p@30 is supported. Therefore, adding a max pixclock prevents
1080p@60 mode is falsely used for those devices
Bug: 815409
Change-Id: Ia2d8dcf360afa51e160d0e997986fe1714254a6b
Reviewed-on: http://git-master/r/31663
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Tested-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|