Age | Commit message (Collapse) | Author |
|
Change-Id: I50cb153fd240818ca876dda53a58809740a272d2
Reviewed-on: http://git-master/r/1141
Tested-by: Aleksandr Frid <afrid@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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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 this change, display comes up with a single key press; but the catch is
that it only works with "Windows" and "F3" keys. This limitation is posed by
Android and not EC.
NOTE that for other than "Windows" and "F3" key presses, the system does wake up,
but an additional "Windows"/"F3" key press is still required to get the display up.
Also, explicitly letting EC know that it should allow any keyboard/mouse event
for wake-up. This is the default behavior, but still wanted to explicitly
specify.
Change-Id: I2a1e7d90fbbfd810f2334ee3832e193bfb5e45b1
Reviewed-on: http://git-master/r/986
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Tested-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Change-Id: Ie798a5dac7b450fd987f90d839549015c24ba2ce
Reviewed-on: http://git-master/r/875
Tested-by: Sheshagiri Shenoy <sshenoy@nvidia.com>
Reviewed-by: Scott Williams <scwilliams@nvidia.com>
Reviewed-by: Michael Hsu <mhsu@nvidia.com>
Tested-by: Michael Hsu <mhsu@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
1. Making Battery and AC present as a wakeup source
2. Registering battery events:present, charging, remaining capacity
3. Handling battery odm flags and events in nvec_battery.c
Change-Id: I814960ab5f065e6aaad72ea1c403ad9c8d6a1af8
Reviewed-on: http://git-master/r/907
Reviewed-by: Sachin Nikam <snikam@nvidia.com>
Tested-by: Sachin Nikam <snikam@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
Currenttly to check the board type E1108 in nvodm_query.c, function
NvOdmIsE1108Hynix() is used. That is EMC DFS specific, so it is
replaced with the generic check
"NvOdmPeripheralGetBoardInfo(BOARD_ID_WHISTLER_E1108, &BoardInfo)".
Bug 666427 : [whistler/android/power] - suspend power has increased
by 4mW
Tested on :Whistler E1108
Change-Id: I7c8cdb9da2891d3b8ade738509024a78f6f6d38b
Reviewed-on: http://git-master/r/943
Reviewed-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Since CONFIG_TEGRA_OTG is not defined in the whistler linux def config file
OTG driver is not getting loaded and causing the USB core to malfunction.
This is fixed by enabling the usb odm property mode as OTG only based on the
CONFIG_TEGRA_OTG. If OTG is not enabled then USB1 port behaves as device by
default.
Bug 664864:[Mobile LDK\LP1] unable to run LP1
Tested on ap20/whistler/android
Change-Id: I0e97596b1341a82652b57afb003c715dd0b7724b
Reviewed-on: http://git-master/r/944
Reviewed-by: Ramachandrudu Kandhala <rkandhala@nvidia.com>
Tested-by: Hanumanth Venkateswa Moganty <vmoganty@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
fix broken build of nvodm_kbc.c caused by path changes during initial
p4 to git merge
keyboard should be a wake event when the KEYBOARD_TEGRA driver is
compiled into the kernel
reduce the repeat and debouce times; the keyboard was nearly
unusable with a repeat ping time of 100ms
fix the row and column numbers for the select wakeup keys: the values
need to be absolute row & column offsets, not the harmony-local GPIO
enumerants (in which columns have numbers above rows), and the values
previously defined ([0,0] and [1,1]) aren't actually keys on the
satellite keyboard; change the values to the ESC and Windows keys.
Change-Id: I50bca7eee5c9101163b01e08457606cb4a5f32de
Reviewed-on: http://git-master/r/932
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Added mechanism to reconfigure Maxim PMU power enable (PWREN)
input on Whistler necessary for LP0 core voltage control.
Change-Id: If7ee20956b39a96093da4094eda9ab64bce54503
Reviewed-on: http://git-master/r/923
Reviewed-by: Trivikram Kasivajhula <tkasivajhula@nvidia.com>
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
NvRm Gpio driver will be wrapper on the native gpio driver such that it
will provide the same existing api and implementation will be use the
native gpio driver. In this approach, it does not need to change the
existing gpio client driver.
Tested on whistler with sdcard insert/remove, touch panel and scroll wheel.
Tested on harmony with the suspend/resume.
Change-Id: I2fa98f8f62a111a1463c1e5b1034e145eaae42a3
Reviewed-on: http://git-master/r/851
Tested-by: Ramachandrudu Kandhala <rkandhala@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
AP20 pop chip is not having USB3 ID pin. Currently both pop and
non-pop whistler are using same odm query with Idpin type
as "Cable Id". Since, it is not reflecting correct Id pin type for
pop, causing the issue.
With this change based on the board type, proper id pin type is
returned as part of usb odm query for USB3. Without ID pin dynamic
detection of devices is not possible, so host functionality is
disabled for USB3 on pop boards. With this change USB3 host is
working for non-pop modules and no hang is seen with pop modules.
Bug 655520 : [AP20/Android/Whistler]: Device hangs after connecting
USB devices(mouse/keyboard).
Tested on : whistler E1109 and whistlerE1008
Change-Id: I5cd67c54756666e58cbc778da2b1015df27c14c6
Reviewed-on: http://git-master/r/795
Reviewed-by: Narendra Damahe <ndamahe@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
adding multi-touch support to the touch screen driver.
Tested with Gallery3D, Multitouch Visualizer and Multitouch Visualise test apps.
Fod Bug 653317
Change-Id: I2976ab91c06a54de4772d88c3d96d72a753205ed
Reviewed-on: http://git-master/r/834
Tested-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Harry Hong <hhong@nvidia.com>
Tested-by: Harry Hong <hhong@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
The power numbers were high on the VDDIO_NAND rail, when the Nand module
was not present in EMMC boot. Doing a Pullup of the unused pin groups
and tristating the pad groups in the VDDIO_NAND rail, brings down the
power from 9mW to 2mW.
Bug 630271
Tested Nand and EMMC boot up on whistler.
Change-Id: I98ac3c0ae237093b0f17552799e0beb956c735e9
Reviewed-on: http://git-master/r/822
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
The usb ddk will use these trimmer values if they are specified in the
NvOdmUsbProperty. Otherwise, it will use the default values specified inside
NvDDK.
Bug 657479: USB trimmer values should not be hardcoded in the DDK
Change-Id: Idd819dc6faba63831ba5164c6c2ebd1a99567a1c
Reviewed-on: http://git-master/r/786
Tested-by: Szming Lin <stlin@nvidia.com>
Reviewed-by: Seshendra Gadagottu <sgadagottu@nvidia.com>
Reviewed-by: Udaykumar Rameshchan Raval <uraval@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
This condition check width[0] == 0xf is not need based on spec
and it is causing second finger samples are ignored many times.
Fixes bug 653317
Change-Id: I2ada2732f0c4965817a0ed1dca1b6351e01d256a
Reviewed-on: http://git-master/r/769
Reviewed-by: Gary King <gking@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Tested-by: Varun Wadekar <vwadekar@nvidia.com>
|
|
Added support for the new Whistler PMU revision that preserves CPU
voltage across LP2 (it will allow to enable core voltage scaling on
E1109 processor boards).
Change-Id: I0724414c5148f39b3c6fa4f0d3f84963231d2520
Reviewed-on: http://git-master/r/726
Tested-by: Aleksandr Frid <afrid@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
|
|
The sizeof parameter provided to NvOdmOsMemset() was having
the wrong value.
It can create unpredictable results if NvEcOpen() fails.
Change-Id: I19a6adabc1b8d780160a017df7b3fb03ac8c8a60
Reviewed-on: http://git-master/r/760
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
Adding new GUID for EMP M570 ULPI modem and the GUID filter in
nvodm_query_discovery. The GUID will be filtered out according to the RIL
option in odmdata.
Change-Id: I6bb2093e35d89c7945c82829f0283cf5a36b804a
Reviewed-on: http://git-master/r/713
Reviewed-by: Udaykumar Rameshchan Raval <uraval@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Gary King <gking@nvidia.com>
|
|
android-tegra-2.6.29
|
|
Disabled SDIO card detection wake on Whistler, since it is triggering
immediately after LP1 entry (bug 657116).
Change-Id: Ib9a18680864d58bf026b097cdec9e84fb644f159
|
|
Register the gpio to which EC wake up is connected as input
and register it's interrupt with RM.
Device wakes up properly but display does not turn on. This is
probably because, the above gpio only wakes up AP but does not
send the key-code packet to AP. Subsequent key press sends the
key-code and hence turns on the display.
Tested on harmony + r04 firmware of EC.
Reviewed by bnihlani and nmalwade.
Change-Id: I1befd95f0799098f2ada12772b5321c190fffe0e
|
|
device" into android-tegra-2.6.29
|
|
the top-level interrupt for the GPIO controller (i.e., at the GIC) must
be enabled in order to detect any enabled GPIO interrupts in the LP1
suspend state.
this change still has a problem that if a GPIO interrupt is only used
as a wakeup source, and is never configured through the ODM kit, the
system is unlikely to go into suspend at all because the interrupt
will never be cleared (so after it fires once, it will continue firing
every time the system attempts to suspend).
enable SD card insert / removal as a wakeup source on harmony to test
GPIO wakeups
Change-Id: I66293cbd3fcf0667ee5c965d002c8722f0fc0811
|
|
When the null phy host connects to an OTG device, the ID pin must set to 1 which
indicates the AP is the host. Otherwise, the device may act as host and AP will
not able to recognize the device. Also configure the pinmux according to the odmdata.
Bug 625086: [AP20 \ Whistler \ Android] ULPI Null phy doesn't work with linux
ehci driver
Change-Id: I5f1c53cbcf91a8978eab8be63431794df6e57e3a
|
|
This changes is applicable to harmony odm.
Change-Id: I85d744a80b71533576c3896ebd21f0b34ea5de91
|
|
Change-Id: I82dbf8c0a0aefcbb77b9596e46858f7c79376b9c
|
|
Presently, NvOdmQueryLowestSocPowerState() for harmony returns state
as active. Changing this to suspend.
This is required when we will enable the RM power management.
Change-Id: I85112372a27ba9f176108fd18108af8507ac6e43
|
|
|
|
Change-Id: Ie35fa84abe09c260827052a0facdee2e220334d4
|
|
Added settling time delays to MAXIM8907 PMU adaptation
on Whistler (bug 649448).
Change-Id: I339d7534f6664a963dbfca797718bb0ffb20c84d
|
|
Change-Id: I29b148aad0036239e3115f7f80e1b5e6eccd9b58
|
|
android-tegra-2.6.29
|
|
Added support for doing readbyte, writebyte and reset Presence pulse
added new enum for supporting these operations.
By default made the ByteMode to FALSE
Addresses Bug 509729
Change-Id: Ib9bdc983eadeda97592213dec7480ad4117dbcf6
|
|
Updated MAX8907B power enable (PWREN) input configuration for the new
silicon revision.
Change-Id: Ia13f518d34084ba5c1554c02d8da3d3c8fe4fd70
|
|
into android-tegra-2.6.29
|
|
Bug 631316: USB charging support in Android Eclair
- Added code in Max8907bSetChargingCurrent().
- Cleaned up end-of-line spaces.
Change-Id: I8aaee731d74713d29ecd167da29a321abadc20fc
|
|
The Offset calculation was done wrong while doing a read operation.
This has been fixed now.
The total size of the EPROM is being retrieved from the odm query, this
value may vary for vendors.
Addresses Bug 509729
|
|
* changes:
tegra RM: adjusted DVFS thresholds.
|
|
Multi-stage Changes are as follows:
Change1:
1) TPS6586x PMU RTC(harmony) cannot store more than 34 years duration.
Hence, RTC driver has been modified to use year 2009 as reference
instead of the year 1970(used in linux by default). Change in
tps6586x rtc implementation.
Issue was Fixed in Bug 621031 earlier and checked into p4 by modifying
tegra rtc driver. We are using a different approach now by only
modifying tps6586x rtc driver. This way rtc drivers for other PMU
like max8907b which can store as much 9999 years in RTC do not need
to change.
2) MAX8907B PMU RTC(whistler) driver was not storing day/month/year data
earlier. Further, on every boot the RTC was being cleared. Fixed this
in file max8907b_rtc.c
Implementation specific to linux as uses library functions: mktime and
rtc_time_to_tm
3) MAX8907B PMU I2C read API implementation was not reading 4th byte.
Changed this as DD, MM, YY1, YY2 information is being read now.
Changed max8907b_i2c.c Further, changes are as follows:
Change2:
1) TPS6586x PMU RTC(harmony) driver modified to select crystal oscillator
as source for RTC. After this change find that RTC counts even when
harmony is powered off.
2) MAX8907B PMU RTC(whistler) driver modified to incorporate review
comments
a) renamed macro SHIFT_TO_2009 as OFFSET_BASE_YEAR
b) used a macro for BCD to decimal conversion for better readability.
Change set 1 was committed but was reverted because of bugs 645312
and 645286. Further tests showed that if the date is set before
testing gallery app the issue is not seen. Trying to re-submit
reverted checkin for change1 along with change2 as a new change.
Change3:
a) decimal to bcd expresssion converted to macro
b) corrected spelling
Bug 625990 : [Firefly2/Harmony] Date & Time is not persisting after reboot
Tested on : Harmony + whistler. Date/time persists.
Note: Whistler rechargable battery needs to be charged to 2.4V for
RTC data to persist. Harmony has non-rechargable battery.
Change-Id: Icc543261096ee4c89cc1e394e2b3868ac370f8e9
|
|
Adjusted DVFS thresholds to better fit process variation space.
Change-Id: I5f44277d2486505c6740406e5818dbd615bcd68f
|
|
TPS6586xPmuSupply_SoC is present only on harmony not on whistler.
Change-Id: Ifc37c9682fb7556a7635e0dfe0849518c57266ff
|
|
Pressing F4 on harmony and selecting shutdown now really shuts down the
system. Initialized the refcount of the SOC rail, which is ON by default, to 1.
Change-Id: I7b93f067f7f2400e2f01fe6f40f523a8d6d76672
|
|
This reverts commit 7b29cc4a7bcee5f0ca927baaa45a90931b45d88c.
Certain Harmony systems exhibit boot instability with this change
enabled
|