Age | Commit message (Collapse) | Author |
|
disable_irq() will do schedule() if threaded IRQ handler is running. But
suspend_cpu_complex() is called from IRQ disabled.
disable_irq_nosync() should be used here because it will not sleep.
BUG 841808
Change-Id: I5bc241e607ffb5cad34530185e308a9f9bbc6543
Reviewed-on: http://git-master/r/37505
Reviewed-on: http://git-master/r/38188
Reviewed-by: Xin Xie <xxie@nvidia.com>
Tested-by: Xin Xie <xxie@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Change-Id: I8af3d087b361b91c17ed7a8035670f7041f5544b
Reviewed-on: http://git-master/r/37983
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
- Initialized the read_words value.
- (tspi->irq < 0) is not valid
because tspi->irq is unsigned value.
Change-Id: I37973c863ecc770b9744737faf5d69cce7b97400
Reviewed-on: http://git-master/r/37868
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Change-Id: Ic46e7f16fdd90db6dc8d7c1e723f10c5d928f382
Reviewed-on: http://git-master/r/37866
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Sometimes avp_node_try_connect is failed.
It is the timing problem between CPU and AVP.
1) Added the retry routine for avp-connection.
2) Increased the time-out value of msg_wait_ack_locked function
from 200ms to 400ms.
Bug 822104, 797362
Change-Id: I92cbbf232ee30179480270f41caf13611c101157
Reviewed-on: http://git-master/r/36439
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Needs kfree function when error occurs.
Change-Id: Ie12fb975459e33c76c0b44d173be4ba2e0da1536
Reviewed-on: http://git-master/r/37859
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
- Changed the kzalloc param from node to block.
- 'CHECK_CONDITION((physical_address < 0), ...' is not valid,
because the physical_address value is unsigned value.
- Fixed uninitialized values
Change-Id: I4eb58b6793ee1ca39664439e5f6aed334e16aa87
Reviewed-on: http://git-master/r/37862
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Stephen Holmes <sholmes@nvidia.com>
|
|
Fix err_delete_wq and err_put_client of error handling.
Change-Id: Ibc86b018172db3df4eca12b5fdd01763679486d0
Reviewed-on: http://git-master/r/37870
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|
|
Changed dev_err to pr_err because 'dd' can be NULL.
Added NULL checking before clock disable of engine->pclk
Change-Id: Ib631ec0b5411d00c0646bc641053e27b2f064480
Reviewed-on: http://git-master/r/37857
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
|
|
Enabling cdev1 clk or DAP Mclk from board file instead of
codec soc file because Mclk needs to be enabled before
codec initialization. Also exposing set_parent() for cdev
clocks so that it is possible to enable them from board
file.
Bug 827709
Bug 839210
Bug 821178
Change-Id: I6e0e15be9f9a2da98ce2ba89e3390bef1e2b93a7
Reviewed-on: http://git-master/r/37631
Tested-by: Sumit Bhattacharya <sumitb@nvidia.com>
Reviewed-by: Scott Peterson <speterson@nvidia.com>
|
|
HDMI connect/disconnect will not affect the suspended device.
bug 835157
Change-Id: Ie4bf55ba556819e17c3738f76ba853f29f5b90cd
Signed-off-by: Sanjay Singh Rawat <srawat@nvidia.com>
Reviewed-on: http://git-master/r/37174
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
|
|
When suspend is called and usb1 is in host mode, tegra_hci_remove is
invoked to remove the device. However, at this time it is likely that
runtime PM will have powered off usb1. This patch ensures usb1 is
powered on if necessary within tegra_hci_remove so that ehci controller
registers can be manipulated.
Bug 835677.
Change-Id: Ida9585ecb4fcc9a88786131a1b629905efd1a07a
Reviewed-on: http://git-master/r/35592
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
|
|
Removed the semicolon after 'if'.
Change-Id: I91df7b367633e269116110b3469c1efcb2589a95
Reviewed-on: http://git-master/r/37459
Tested-by: Jubeom Kim <jubeomk@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@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: Ie4a7ba9dfc765ca3a9e4c443112364230338896c
Reviewed-on: http://git-master/r/37180
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
|
|
In nvmap_munmap(), remove_vm_area just remove the allocated memory
page information. It doesn't de-allocate vm_struct. kfree()
should be used to avoid memory leak in nvmap.
Bug: 833796
Change-Id: I90c9cd58ae40661188cf6d00475a8ad490374184
Reviewed-on: http://git-master/r/35630
Tested-by: Kai Chih (Kenji) Chen <kenjchen@nvidia.com>
Reviewed-by: Yu-Fong (Foster) Cho <ycho@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
If there are more than one hdmi modes that have same xres,
yres, and vmode, tegra_dc_hdmi_mode_equal can return true even
though pixclocks are way different from each other.
Now, tegra_dc_hdmi_mode_equal will retun false if pixclock has
more than 1Hz of difference. Also, tegra_fb_set_par will use
fb_find_nearest_mode instead of fb_find_best_mode to take
refresh rate into the consideration.
Bug: 815409
Change-Id: I2dd911fa337b91933f68801b636cbcc7ad6f8fea
Reviewed-on: http://git-master/r/36464
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Tested-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
|
|
Refresh rate nearness is not calculated or reset when nearest resolution
changes.
This patch resets the refresh rate differential measurement whenever a
new nearest resolution is discovered. This fixes two error cases;
first, wherein the first mode's refresh rate differential is never
calculated and second, when the closest refresh rate from a previous
nearest resolution is erroneously preserved.
back-ported from kernel.org
Change-Id: I9f1062153efbc546d4c97d627032f6ef48992387
Reviewed-on: http://git-master/r/36662
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Tested-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
- remove delay on i2c r/w success to fix hdcp test case 1b-03 failure
- do not turn on hdcp crypt before verifying repeater
bug 829599
(cherry picked from commit 44aa4eac6285e1b95865cc79b345999b1d3eab55)
Change-Id: I51ac55bf619821aa7af948799330ee11661bb6b7
Reviewed-on: http://git-master/r/36639
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
|
|
CONFIG_TEGRA_ENABLE_SUPPORT_FOR_1080p_30HZ define is not needed
anymore since this can be filtered from user space driver
Bug: 815409
Change-Id: I3fd37d2c3e737aaa056aea2af7b41ac5b93b9807
Reviewed-on: http://git-master/r/36435
Reviewed-by: Michael I Gold <gold@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Tested-by: Donghan Ryu <dryu@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: I9f1eb721cbbe91b4e9c10cc8aa64f335be111651
Reviewed-on: http://git-master/r/36215
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Seongho Joo <sjoo@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
(cherry-pick from 789333436de3878b2ea878d4c2c030af7ed481ce)
Change-Id: If1a01a5883051290bdaf09537f737e5797209936
Signed-off-by: Nathan Connell <w14185@motorola.com>
Reviewed-on: http://git-master/r/36311
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
|
|
MMC_BLOCK_DEFERRED_RESUME causes race conditions in the SD/MMC driver,
i.e. mmc_sd_detect() will be called from different threads causing
inconsistent state. Disabling feature for Tegra.
Bug 833034
Change-Id: I516272a5a0af44ba27122cc0c6476512cf5b617d
Reviewed-on: http://git-master/r/36254
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
Change-Id: I91c8f657ee510f25180dc733d6106697d0e4498f
Reviewed-on: http://git-master/r/36251
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@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: Idc94263084e8a3f83694b30efe09e563ffe64068
Reviewed-on: http://git-master/r/33112
Reviewed-on: http://git-master/r/36231
Reviewed-by: Min-wuk Lee <mlee@nvidia.com>
Tested-by: Min-wuk Lee <mlee@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
Change-Id: I5ab066d8535cf719b5ed830293a883609180b525
Reviewed-on: http://git-master/r/36157
Tested-by: Cho-Che Cheng <jacheng@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
|
|
usbcore will reenable usb interrupts later once the bus has been
resumed.
bug 835193
Change-Id: Idf36d34f2f08c469246e7329b088529f3d805b7d
Signed-off-by: Benoit Goby <benoit@android.com>
Reviewed-on: http://git-master/r/36145
Tested-by: Cho-Che Cheng <jacheng@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Rakesh Bodla <rbodla@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
Change-Id: I766ee27320a6cfa7cf8d937e3dbeb522a3fd19bd
Signed-off-by: Benoit Goby <benoit@android.com>
Reviewed-on: http://git-master/r/36144
Tested-by: Cho-Che Cheng <jacheng@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
|
|
Bug 820602
Change-Id: I6a5f116cc3c32f58a7404de24a073ddaf2c79227
Reviewed-on: http://git-master/r/35954
Tested-by: Cho-Che Cheng <jacheng@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: I21876a4d2a8d729def9f43a0f8879e1de3e84dde
Reviewed-on: http://git-master/r/33083
Reviewed-on: http://git-master/r/35355
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Kaz Fukuoka <kfukuoka@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
- reset intr_status if error occur while encrypt/decrypt
- rename iram variables to _phys and _virt
- use bsea for rng
- remove unwanted macros from the header file
Bug 833165
Bug 778258
Reviewed-on: http://git-master/r/#change,34552
(cherry picked from commit 4f2f0431fe196829c8ec61ab10ed5cb2ea6b5038)
Change-Id: I5b117313fe15cf1d4973d97353220f1855b82333
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/35830
Reviewed-by: Yuhao Ding <yding@nvidia.com>
Tested-by: Yuhao Ding <yding@nvidia.com>
|
|
Bug 814896, 820602
Change-Id: Ief590e49f995dd1da6502707ac329057a12f4f17
Reviewed-on: http://git-master/r/35948
Tested-by: Cho-Che Cheng <jacheng@nvidia.com>
Tested-by: Gerrit_Virtual_Submit
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
- handle scenarios when the number of fuses burnt
is a odd number
- wait for the fuse bock to be idle before issuing
any command
- burning of master_enb fuse is not required to be
done according to the guidelines
Bug 823552
Change-Id: I04477dcfae610aed3e2072adfc48ebd7212449ad
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/35883
Reviewed-by: Andy Carman <acarman@nvidia.com>
Tested-by: Andy Carman <acarman@nvidia.com>
Reviewed-by: Venkata (Muni) Anda <vanda@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
use FB_BLANK_POWERDOWN on hdmi device in earlysuspend to cause
tegra_dc_disable.
Fixes bug 835171
Change-Id: I112d05f271b9d12319186ff1b9bd2d0e0667a75e
Reviewed-on: http://git-master/r/35412
Tested-by: Gaurav Sarode <gsarode@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@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
Change-Id: I3ff294f9cbe3660964b9bd227c233f4e20115e80
Reviewed-on: http://git-master/r/35352
Reviewed-by: Alex Courbot <acourbot@nvidia.com>
Tested-by: Alex Courbot <acourbot@nvidia.com>
Reviewed-by: David Schalig <dschalig@nvidia.com>
Tested-by: David Schalig <dschalig@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
|
|
Added regulator vmic to use in soc-audio
Reviewed-on: http://git-master/r/33110
(cherry picked from commit 1b5f6d90219d6e3beeaeb2ec286949bc838d9bc4)
Change-Id: Iba33f5bf2bc5243ff13995005d1c182f6d120d55
Reviewed-on: http://git-master/r/35375
Tested-by: Viraj Karandikar <vkarandikar@nvidia.com>
Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com>
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
Tested-by: Rohan Somvanshi <rsomvanshi@nvidia.com>
|
|
Support recording with d-mic in audio only use case
Reviewed-on: http://git-master/r/34551
(cherry picked from commit 58ff88e8ef9b805381a1bef40be276224a43e175)
Change-Id: Iea9b509b805542f5089fb3399d7796d23d9270e5
Reviewed-on: http://git-master/r/35376
Tested-by: Viraj Karandikar <vkarandikar@nvidia.com>
Reviewed-by: Scott Peterson <speterson@nvidia.com>
|
|
instead of checking for NULL, IS_ERR() should
be used to check the validity of a clock handle
Change-Id: Ic0ef30c64f4bd95995dcde048cd7630e2d75cd92
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/35619
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
disabling ldo4 kills power to the board completely.
there is no way to power on the board again, other
than reinserting the power plug.
Change-Id: I1e03389cf26ad8de7a5d5fb518f85fa6c9427752
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/35620
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
This option adds support for ASIX AX88xxx Based USB 2.0
Ethernet Adapters and it works with TrendNet TU2-ET100 devices.
Bug 834417
Change-Id: I46d3990e72c66b6abc2821b7e70d039718bbf487
Reviewed-on: http://git-master/r/35699
Reviewed-by: Vandana Salve <vsalve@nvidia.com>
Tested-by: Vandana Salve <vsalve@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Split Headset to Headset Out and Headset In
Use IN1L for Int mic and Headset (for WM8903)
Remove unused variables and warning
Bug 816278
Bug 830213
Reviewed-on: http://git-master/r/30142
Cherry picked from commit 170ccc20d6227faaf196a920e7812792c305e2ff
Change-Id: I19cf5994d59b84c309473e094b706205d89b58af
Reviewed-on: http://git-master/r/35368
Tested-by: Viraj Karandikar <vkarandikar@nvidia.com>
Reviewed-by: Sumit Bhattacharya <sumitb@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Extend the wait interface to relay the actual resultant waited
point back.
Reviewed-on: http://git-master/r/23033
(cherry picked from commit bc22c56ecb54ec093262cee4b1105c2503e5497e)
Change-Id: I65224359f85d3f357e48eeacdf76c9bd97056a54
Reviewed-on: http://git-master/r/35919
Reviewed-by: Brian Anderson <branderson@nvidia.com>
Tested-by: Brian Anderson <branderson@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@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>
|
|
Passing card detect gpio polarity through platform data.
This is used in sd cards insertion/removal detection.
Bug 831409
Change-Id: I29c99696daf094d4f04789121ddfb681dccca12a
Reviewed-on: http://git-master/r/33123
Reviewed-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Tested-by: Pavan Kunapuli <pkunapuli@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Joseph Lehrer <jlehrer@nvidia.com>
Tested-by: Joseph Lehrer <jlehrer@nvidia.com>
|