linux-toradex.git/drivers, branch tegra-9.12.10

nvmap: relax iovmm over-commit check for kernel client

2010-04-20T21:12:12+00:00

Change-Id: Ia2b5576672ad65e0cf730ca1a243c2efddbea906
Reviewed-on: http://git-master/r/1162
Reviewed-by: Antti Hatala 
Tested-by: Antti Hatala

tegra_odm_battery:porting the battery polling timer changes.

2010-04-16T03:27:00+00:00

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 
Reviewed-by: Mayuresh Kulkarni 
Reviewed-by: Gary King 
Tested-by: Sachin Nikam

fsl udc:Fix USB disconnect notification in OTG

2010-04-15T21:06:37+00:00

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 
Tested-by: Gary King

[spi] update tegra driver to support multiple slaves

2010-04-15T20:42:00+00:00

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 
Tested-by: Venkata (Muni) Anda

usb gadget: Implementing checks to fix NULL pointer dereference exception

2010-04-15T01:10:35+00:00

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 
Reviewed-by: Hanumanth Venkateswa Moganty 
Tested-by: Hanumanth Venkateswa Moganty 
Reviewed-by: Gary King

bcsp: Fix BCSP Bug: bcsp_pkt_cull: Removed only x out of x-1 pkts errors.

2010-04-13T22:57:43+00:00

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 
Tested-by: Udaykumar Rameshchan Raval 
Reviewed-by: Gary King

tegra uart: Fixing the tx and rx dma path issue

2010-04-13T22:57:22+00:00

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 
Reviewed-by: Udaykumar Rameshchan Raval 
Tested-by: Udaykumar Rameshchan Raval 
Reviewed-by: Gary King

tegra nvmap:fixing memory corruption is nvmap.c.

2010-04-12T19:35:31+00:00

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 
Tested-by: Gary King

nvec_battery:Handling critical battery condition

2010-04-06T03:29:46+00:00

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 
Tested-by: Sachin Nikam 
Tested-by: Bharat Nihalani 
Reviewed-by: Gary King

tegra: Enabling Accelerometer Driver for whistler board.

2010-04-06T03:28:20+00:00

This should enable accelerometer on Whistler.

Change-Id: I884ef704083c8d5e1fe07554301eb28a2c24db49
Reviewed-on: http://git-master/r/987
Reviewed-by: Bharat Nihalani 
Tested-by: Bharat Nihalani 
Reviewed-by: Gary King