Age | Commit message (Collapse) | Author |
|
Bug 651676, this is causing failure while entering system suspend when lp0 is lowest power state
Change-Id: I4337fc00571e21f9a6d39706b74ec62522cb6d46
Change-Id: I4337fc00571e21f9a6d39706b74ec62522cb6d46
Reviewed-on: http://git-master/r/1166
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
CPU power request line needs to be explicitly enabled so that PMUs with
separate request lines for CPU and core rails will shutdown the CPU power
rail as expected.
Change-Id: I95bc048b6e1df9029e900d33c4c0f5aa63c008a7
Reviewed-on: http://git-master/r/1156
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Venkata (Muni) Anda <vanda@nvidia.com>
|
|
Change-Id: I50cb153fd240818ca876dda53a58809740a272d2
Reviewed-on: http://git-master/r/1141
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Bug 671189, 663161
Tested on Nand + android.
Change-Id: I518d8a1b57a9766dc69a115b1189789f054c2d0e
Reviewed-on: http://git-master/r/1088
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Change-Id: Ia2b5576672ad65e0cf730ca1a243c2efddbea906
Reviewed-on: http://git-master/r/1162
Reviewed-by: Antti Hatala <ahatala@nvidia.com>
Tested-by: Antti Hatala <ahatala@nvidia.com>
|
|
It seems that after writing SYSCLK_OE bit in APBDEV_PMC_CNTRL_0,
a delay needs to be added for stabilization.
Reviewed by Bharat. Tested on Harmony (A02, R04 EC firmware) for
multiple flash and reboot.
Bug 676490 - [T20/Harmony] Bootup failure on harmony-inconsistent (3/5 times)
Change-Id: I1f45a86aa23ac00b43f0103285cceda970ee5b39
Reviewed-on: http://git-master/r/1160
Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
In order to keep sndfx file in sync with audiofx header
file updating tegra_sndfx.h with structures and
definitions, made the corresponding changes in code.
Verified both playback and record are working fine.
For bug 676616
synopsis: ALSA is Broken
Change-Id: Ic3eca9e88c861169bcbcc829a621adc40ea2bea7
Reviewed-on: http://git-master/r/1158
Reviewed-by: Vijay Mali <vmali@nvidia.com>
Tested-by: Vijay Mali <vmali@nvidia.com>
Reviewed-by: Manjula Gupta <magupta@nvidia.com>
Tested-by: Manjula Gupta <magupta@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
The interrupt flag in the 32KHz domain might not be getting cleared correctly.
Clear the kbc interrupt explicitly prior to LP0 to fix this.
Change-Id: I68c93cb3130fd123e28f1c697b9314b1bbcf4c6e
Reviewed-on: http://git-master/r/1154
Reviewed-by: Gary King <gking@nvidia.com>
Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Tested-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
|
|
Bug 663285
Enable nvmap to reclaim unpinned I/O virtual memory after it has been
unpinned and re-use it for other objects.
Checking in on behalf of yhsu.
Change-Id: I27304b45a80ae0d2fcad9f126672fe6ff5ded2af
Reviewed-on: http://git-master/r/1144
Reviewed-by: Krishna Reddy <vdumpa@nvidia.com>
Tested-by: Krishna Reddy <vdumpa@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
Tested-by: Yu-Huan Hsu <yhsu@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Change-Id: I6969716342df0b28db1167df9bca50a5c03ffb2f
Reviewed-on: http://git-master/r/1138
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
LP0 turns off core voltage. As a result, the L2 rams
need to be flushed prior to shutdown. The L2 cache
will be re-enabled after returning from LP0.
Change-Id: Ie6e69a3e5615393c5c6e7189b4d7e3559304e7f9
Reviewed-on: http://git-master/r/1036
Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Tested-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
As we know that android doesn't polls for the battery status.
In order to update the battery and power supply related info
created a timer func which polls for every 30Sec and updates
the battery and power supply info.
Also, there is a sysfs attribure "status_poll_period" using
which this polling interval can be altered.
Already, we have these changes in nvec_battery.c which are
wokring and verified. Porting the same changes to
tegra_odm_battery.
Change-Id: I19f8e3f24c333745b7d90084a7e8c320ac8a1d6b
Reviewed-on: http://git-master/r/1064
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Sachin Nikam <snikam@nvidia.com>
|
|
To enhance the USB MSD performance, the busy hints for cpu clock have
been enabled on cable connect and its frequency is being boosted to
300 MHz.
Bug 654486: [whistler/android] - Large difference in USB MSD perf with
DFS OFF
Change-Id: I4471665bd02b7b49b368aec4aac5f1b89038c309
Reviewed-on: http://git-master/r/1114
Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com>
Reviewed-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
Tested-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Set the GPIO in a reasonable state before calling NvRmGpioConfigPins(Output) to
avoid 5us~1ms low-pulse, since the low-pulse causes some EC firmwares to crash.
reviewed by Artiste-Hsu
tested on Harmony
Change-Id: Ia30dfd10dfd16eec979f2a8e6ffc8286121a2eeb
Reviewed-on: http://git-master/r/1126
Tested-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Phillip Smith <psmith@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Change-Id: Ied68fde9cc9556088837ccaabfdd93c396777218
Reviewed-on: http://git-master/r/1130
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
On Whistler enabled CONFIG_CGROUP_SCHED instead of CONFIG_USER_SCHED
to be in sync with Harmony kernel config. Enables cgroup file system.
Bug 669840
Change-Id: I4366b0ad0af5cb57fb7adc373347e081811d0590
Reviewed-on: http://git-master/r/1111
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
In OTG mode, when USB cable is removed cable disconnect notification is not
sent to the client driver. Hence at application layer, UI shows up USB cable
connection notification even USB cable is removed.
With this fix disconnect notification is going to the client driver and
UI removes the USB notification on USB cable removal.
Tested on android/whistler
Bug 668692: USB cable is removed, but does not appear in notification.
Change-Id: I06d5a288873a2a8d7d109c5109b9dfd0c08fd1ee
Reviewed-on: http://git-master/r/1112
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
the spi clock, chip select and bits per word need to be applied
from the spi slave device specified in the transaction
previously, the values were constant for each master, and corresponded
to the last device registered on the bus
issue originally reported by Mike Corrigan
Change-Id: I047b6aa6d92f2c9e134311d3d32bcb75d5f689f5
Reviewed-on: http://git-master/r/1102
Reviewed-by: Venkata (Muni) Anda <vanda@nvidia.com>
Tested-by: Venkata (Muni) Anda <vanda@nvidia.com>
|
|
Added PMU low power state configuration to RM kernel suspend/resume.
Included PMU interrupt control, and core rail control on platforms
with combined cpu/core power request.
Restricted core power groups gating to LP1 entry (core domain is down
in LP0, anyway).
Change-Id: If37ddfd42bd861b2cbc31767775583bd13549da8
Reviewed-on: http://git-master/r/1086
Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Tested-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Updated EMC DVFS table on Whistler:
- made sure RFC settings are above 5 for all entries
- disabled DQS_PULLD for 150MHz entry and below
- lowered operational voltage for 18MHz and 27MHz entries from 1.0V to 0.95V
Change-Id: I682ed68bb5bfd4497a214065007159ab2fe042b7
Reviewed-on: http://git-master/r/1089
Reviewed-by: Sharad Ranjan <shranjan@nvidia.com>
Tested-by: Sharad Ranjan <shranjan@nvidia.com>
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
In LDK, no gadget driver gets registered with the udc driver and thus
udc->driver is not initialized and is NULL. Accessing members of
udc->driver in the execution path of fsl_udc_irq() results in NULL
pointer dereference exception.
Fixing it by implementing NULL value checks for udc->driver at
appropriate places.
Bug 671801: [Mobile LDK\Harmony] wake up from LP1 freezes the device
Bug 671807: [Mobile LDK\Harmony\LP1] Wake-up by USB mini-b cable is not
working
Change-Id: I502ad8b4ba804bc82ec95af739e71ccfb11493d7
Reviewed-on: http://git-master/r/1110
Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com>
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Disabled NOR clock in RM ("orphan" boot clock). If/when NOR driver is
added it will re-enable it as necessary.
Change-Id: I5f9b15a5be86c594b6638c3110d9f1d8ba5db694
Reviewed-on: http://git-master/r/1116
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
After debugging this issue - I found that the issue was fixed in
linux-2.6.32. back porting the fix to present kernel.
The routine bcsp_pkt_cull() displays the false error message
"Removed only %u out of %u pkts" when multiple to be acked
packets are queued.
As if (i++ >= pkts_to_be_removed)
break;
will breaks the loop and increase the counter i
when i==pkts_to_be_removed, the loop ends up with i=pkts_to_be_removed+1.
The following line:
if (i != pkts_to_be_removed) {
BT_ERR("Removed only %u out of %u pkts", i, pkts_to_be_removed);
}
will display the false message.
The counter i must not increase on the same line.
Change-Id: I0ca08003a4ec7d1b8ed105f219964934afad1a50
Reviewed-on: http://git-master/r/1098
Reviewed-by: Udaykumar Rameshchan Raval <uraval@nvidia.com>
Tested-by: Udaykumar Rameshchan Raval <uraval@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Following issue has been fixed:
- Blocking write was returning immediatly if data request is multiple of 4.
- Blocking write was not able to complete if data length is nonmultiple of 4
and more than 4.
- The close was taking too much time because proper timeout and fifo size was
not configured.
- Tx dma path optimized to fill more data to dma buffer if there is more
pending chars in the buffer.
- Tx path is fixed to properly signal the wakup event to tty layer.
- RTS flow control is not getting set from second open even cflag is
requested for that.
- Rx dma was not receiving the correct data after second open. The multiple
request was
getting queued for the receive path at the time of closing.
- Rx dma was started before uart controller is configured and it is creating
to misbehave the dma.
- Transfer count was not getting calculated in the dma driver.
Pending issue:
- Loosing the data id more than 32K of data was sennt is single shot. Debugging
this.
Tested on harmony with different testcase developed for testing the linux serial
driver.
Change-Id: I6ed9095dd6340d2b5e7ef036823d2e4e5a61abcc
Reviewed-on: http://git-master/r/1065
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Udaykumar Rameshchan Raval <uraval@nvidia.com>
Tested-by: Udaykumar Rameshchan Raval <uraval@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
patch: removing extra spaces
Change-Id: Icc7fa7d5744134c0846b99c77b90cd76f9f938fc
Reviewed-on: http://git-master/r/1068
Tested-by: Sharad Ranjan <shranjan@nvidia.com>
Reviewed-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
In order to keep sndfx file in sync with audiofx header
file updating tegra_sndfx.h with structures and
definitions, made the corresponding changes in code.
Verified both playback and record are working fine.
Change-Id: Ibfa400fcf1b62c55f169d427ae40aa9467d13f82
Reviewed-on: http://git-master/r/1079
Reviewed-by: Vijay Mali <vmali@nvidia.com>
Tested-by: Vijay Mali <vmali@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Adjusted LP2 time padding factor to reduce LP2 entry threshold back to 5ms
(commit ad159fa937e9d917737956d12d530b723cba2b13 set it to 12.5ms as a side
effect of adding power good delay to LP2 turnaround time)
Change-Id: I1f00803e5d043cc6e99aeb7b373c0bdbda56e0ed
Reviewed-on: http://git-master/r/1087
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
by the time that the slave processors' page table pointers are written
to memory, the L1 and L2 caches may already be enabled on the master,
so the writes need to be forcefully cleaned to memory to ensure that
the slave will be able to read it.
patch originally submitted to 2.6.34 by RMK
Change-Id: Id9952149ce17c693775ec2b21e9a0425465fb770
Reviewed-on: http://git-master/r/1067
Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Bug 670448
nvmap_grow_blocks() is exceeding the array bounds. This is
causing the crash issues during system boot up.
Fixed it by removing the erroneous two lines that are exceeding
array bounds.
Change-Id: Ie7fd72c3a0f79015114dc1d1c8cbf31e3a50f0b6
Reviewed-on: http://git-master/r/1080
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
tegra_secondary_startup was not invalidating the entire CPU state when
bringing up a slave CPU. This change adds invalidation of the I-cache,
TLB, and BTAC, and also enables the I-cache and branch prediction to speed
up D-cache invalidation.
Change-Id: I82b21dde7befb5ae634a72418b06892a30ec1ebf
Reviewed-on: http://git-master/r/1069
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Tested-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Adding the following DSI read response error codes.
DispDsiReadAckError, Acknowledge & Error read response.
DispDsiReadInvalidResp, invalid read response.
Bug 644992
Change-Id: Id629c05a0ce851a698d5028da138de942cedcc5c
Reviewed-on: http://git-master/r/1059
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Reduced EMC activity margin from 100% (2x) to 50% (1.5x) based on video
use case experiments.
Change-Id: I8467a52d00b62011516cefd040eb90f625f30d8d
Reviewed-on: http://git-master/r/1062
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Niranjan Wartikar <nwartikar@nvidia.com>
Tested-by: Niranjan Wartikar <nwartikar@nvidia.com>
Reviewed-by: Sharad Ranjan <shranjan@nvidia.com>
Tested-by: Sharad Ranjan <shranjan@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
The LDO0 power rail was enabled during bootup by default, thereby
increasing the ref count. This results in the rail remaining powered
ON even when we try to disable it from a driver.
Disabling the LDO0 by default, when there are no devices actively
using it, should result in power saving.
Change-Id: I19e478e9af2019de5e02ff9a31e7085e815ffaed
Reviewed-on: http://git-master/r/1058
Reviewed-by: Kenneth A Radtke <kradtke@nvidia.com>
Tested-by: Deepesh Subhash Gujarathi (Engrg-Mobile) <dgujarathi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Updated tegra idle loop timing:
- Added scheduler tick stop as a condition for LP2 entry; it made sure
that jiffies are updated by the kernel after tegra idle code exit;
hence, direct (unprotected) jiffies increment in idle code is removed
- Rounded down sleep time estimate to avoid over-sleeping next interrupt
in LP2
- Set more realistic LP2 turn-around time to take into account power rail
transition time
Change-Id: I7d97496b2f39d33a8150b51dfa152e72eb774fc0
Reviewed-on: http://git-master/r/1054
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
After a gcc update, compilation of mm/page-writeback.c with -O2 started
to fail.
Change-Id: I466bad143e005aa0abe11df5cc2fa7a92913aee0
Reviewed-on: http://git-master/r/1060
Reviewed-by: Antti Hatala <ahatala@nvidia.com>
Tested-by: Antti Hatala <ahatala@nvidia.com>
|
|
use inclusive addresses for the PCI memory aperture limits; otherwise,
transactions destined for root port 1 show up on root port 0.
originally reported by Ali Saidi (ali.saidi@arm.com)
Change-Id: I48181325f6164159713139d4868cb12f6563f1ab
Reviewed-on: http://git-master/r/1003
Reviewed-by: Jeremy Alves <jalves@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
When gpio client uses the direct linux api which is provided by
gpio lib of linux kernel driver, the pinmux and io power rail was
not getting configured.
Configuring the pinux and power rail so that client can use direct
gpio api of linux and need not to use the rm gpio wrapper api.
Tested on whistler.
Change-Id: I02b6782fd751543d064588288104a26caab7c848
Reviewed-on: http://git-master/r/1021
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
The native timer code to program the timer hardware for the next kernel
event was incorrectly rescaling the cycle count which was passed in by
the kernel. This would result in event periods 100000 times longer than
expected. This error would occur only when LOCAL_TIMERS were not configured.
Change-Id: I32a1593368510069afe1fb439465d6c9b696c4d3
Reviewed-on: http://git-master/r/1051
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Tested-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Power gated all core partitions (except L2C) when entering suspend. During
resume ungate those partitions that were powered before suspend.
Change-Id: I6559f7d314df5904acc8f639efe953d8382925ac
Reviewed-on: http://git-master/r/1046
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
1. nvec.h:Correcting enum ordering for NvEcBatterySubtype
as per ECI specs.
NvEcBatterySubtype_SetRemainingCapacityAlarm and
NvEcBatterySubtype_GetRemainingCapacityAlar
>> Verified
2. Registering interrupt for LOW_BAT# from T20 pinmux table:-
GPIO interrupt for Low battery on port w and pin 3
>> Already verified on Wince.
On Android when 0% power is left device
is shutdown. Harmony has this setting around 9.3V which is
less when the battery is at 0%.
3. Enabling LOW_BAT# as a wakeup source 11 from suspend
>> As point no. 2 is wokring this should also work.
This is not verfied as in suspend battery discharge
is slow.
4. Enabling Low capacity alarm as a wakeup source suspend
>> As remaining capacity alarm is working this should also
work.
This is not verfied as in suspend battery discharge
is slow.
5. Setting the 10% of Design capacit as threshold for
Remaining capacity alaram event.
>> Verified
6. Adding 4 functions which are needed for EC firmware validation
NvOdmBatterySetRemCapacityAlarm
NvOdmBatteryGetRemCapacityAlarm
NvOdmBatterySetConfiguration
NvOdmBatteryGetConfiguration
>> Verified
7. Calling kernel_power_off() when device is running on only battery
and it is ctitically low to gracefully shutdown the system.
>> Verified
Tested on harmony + eclair + battery
Change-Id: I6f4c8a1866ba63c293813b180cc5b74714aa23cd
Reviewed-on: http://git-master/r/976
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Tested-by: Sachin Nikam <snikam@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
This should enable accelerometer on Whistler.
Change-Id: I884ef704083c8d5e1fe07554301eb28a2c24db49
Reviewed-on: http://git-master/r/987
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Change-Id: I30872e9905b7bdf1cca56e53089e5cfde7586798
Reviewed-on: http://git-master/r/1026
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Change-Id: Iffad8a511bb6434b26e58d8dacf24a5751c23610
Reviewed-on: http://git-master/r/1028
Reviewed-by: Acorn Pooley <apooley@nvidia.com>
Tested-by: Acorn Pooley <apooley@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Normally, when the system goes into suspend, all the storage cards are
removed and later re-enumerated upon resume. During re-enumeration the
device name and number are not guaranteed to be the same as they were
during bootup. This can cause issues if rootfs falls on one such
device.
When the MMC_UNSAFE_RESUME config is enabled, it will prevent kernel
from unmounting the mmc cards before suspend. Upon resume the cards
will still be using the same device id as they were before suspend.
Change-Id: Ibc1511c5feb0391dc644df2d710e386ec0d353ce
Reviewed-on: http://git-master/r/994
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Updated VDE clock configuration policy - allowed to use high frequency
PLLC for VDE targets within 100MHz-200MHz range. This range was covered
by low frequency PLLP0, but better divider granularity achieved with PLLC
results in lower voltage requirements.
Change-Id: I922dbd8db19dc19339db5bfbf2651604e28e789d
Reviewed-on: http://git-master/r/1007
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Sharad Ranjan <shranjan@nvidia.com>
Tested-by: Sharad Ranjan <shranjan@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
As per the harmony power tree VDDIO_PEX_CLK is the T20's
3.3V PCIe supply. It is sourced from LDO0 of the PMU. By
default, LDO0 is off.
VDD_1V5 is the 1.5V supply for the PCI Express Mini Card
connectors. It turns on automatically in tandem with the
general-purpose 3.3V domain.
If there are no active pcie devices on the bus turn off
the VDD_1V5 power rail.
Change-Id: I518368937aa36e7c73fbb93c28a39706903a614d
Reviewed-on: http://git-master/r/1019
Reviewed-by: Kenneth A Radtke <kradtke@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
This fix corrects the pinmux configuration so UART-A is mapped to SDIO1 pins
when ULPI is used. AP will be able to communicate with the ULPI modem through
both UART and ULPI.
Change-Id: I268a76496bd5371c2b757b0133eb0f276234504f
Reviewed-on: http://git-master/r/1005
Tested-by: Szming Lin <stlin@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
With CL#5705540 USB host functionality on OTG port has broken
on Whistler.Also Device dis-connection and connection on root
port(USB3),makes host functionality broken. So this needs to
debugged further. However for Harmony both USB1 device and USB3
integrated hub are working fine with-out any issue. So reverting
the change for Whistler configuration only.
Bug 669288 :[AP20/Android/Whistler]: USB devices not working.
Tested on : Whistler and Harmony
Tested for USB host functionality on OTG port
Tested for USB host functionality on USB3 with
multiple connection/dis-conenction.
Change-Id: Id1c2157d796e095ff66e5002b5d00958a89a7bf7
Reviewed-on: http://git-master/r/1008
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Fixed an incorrect calculation for skipping to the next byte of bond-out
information. Bailing out of a byte early would result in an incorrect offset
being used for subsequent module ids resulting in incorrect modules being
marked as bonded out.
Change-Id: Ia5cb449006c2d3b825097c852c21f4e1346e6696
Reviewed-on: http://git-master/r/1024
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
- Don't signal the shutdown thread until the thread
process the SNDRV_PCM_TRIGGER_STOP call. The Kthread_stop()
call is a blocking call that waits until the kthread_should_stop()
returns.
- Set the prtd->state to SNDRV_PCM_TRIGGER_STOP in pcm_common_close
specifically to ensure proper clean-up and to handle the case
where application exits without triggering the STOP call.
- wait for the buffer done notification for the buffers queued in
before setting mixer state to stop.
- For Bug 667787 [LDK/Whistler/ALSA]"arecord" app hung
with DVD quality .raw audio recording (Mono/Stereo).
Change-Id: Id9c13bbd2dd0b5f90b3c545677eddfa05849c45f
Reviewed-on: http://git-master/r/997
Reviewed-by: Vijay Mali <vmali@nvidia.com>
Tested-by: Vijay Mali <vmali@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|