linux-toradex.git/drivers, branch tegra-10.8.3 Linux kernel for Apalis and Colibri modules video: tegra: nvmap: disallow splitting when no spare blocks available 2010-09-02T13:22:41+00:00 Thomas Roell troell@nvidia.com 2010-09-01T12:13:47+00:00 3a7a9bcd117f8c0f09c6eb74e79b0996397bf486 The block realignment if a block wasn't split lead to a slow leak of carveout memory if the previous block was not a free block. Change-Id: I08bd89364932f2c4fc4faf1dec177dab03e82a9a Reviewed-on: http://git-master/r/5851 Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Thomas Roell <troell@nvidia.com> 
The block realignment if a block wasn't split lead to a slow leak of carveout memory if the previous block was not a free block.

Change-Id: I08bd89364932f2c4fc4faf1dec177dab03e82a9a
Reviewed-on: http://git-master/r/5851
Reviewed-by: Gary King <gking@nvidia.com>
Tested-by: Thomas Roell <troell@nvidia.com>
tegra sdhci: Restore SDHCI interrupts on resume 2010-08-31T12:31:16+00:00 Rahul Bansal rbansal@nvidia.com 2010-08-20T12:52:12+00:00 30d90c8af0bb790e4ce2cf256dcb4ff87ad9e3a8 On resume restore SDHCI interrupts to the state which was before entering into suspend for SDIO (always_pwr_on) slot. Also, in suspend keep CARD_INT enabled if it was before going to suspend, so that it can be used as wake source. Broadcom wifi driver does not disable/enable SDIO_INT on early_suspend/late_resume, it requires SDIO INTs to be enabled on resume, as even before broadcom driver's late_resume is called which puts wifi is high_pwr, it needs to communicate with MAC for incoming IOCTLs from wpa_supplicant. Bug: 723708 Change-Id: Id1bfe67f415080eeb7563428322dbec3df0f27d2 Reviewed-on: http://git-master/r/5407 Reviewed-by: Rahul Bansal <rbansal@nvidia.com> Tested-by: Rahul Bansal <rbansal@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
On resume restore SDHCI interrupts to the state which
was before entering into suspend for SDIO (always_pwr_on)
slot. Also, in suspend keep CARD_INT enabled if it was
before going to suspend, so that it can be used as wake
source.

Broadcom wifi driver does not disable/enable SDIO_INT
on early_suspend/late_resume, it requires SDIO INTs to
be enabled on resume, as even before broadcom driver's
late_resume is called which puts wifi is high_pwr, it
needs to communicate with MAC for incoming IOCTLs from
wpa_supplicant.

Bug: 723708

Change-Id: Id1bfe67f415080eeb7563428322dbec3df0f27d2
Reviewed-on: http://git-master/r/5407
Reviewed-by: Rahul Bansal <rbansal@nvidia.com>
Tested-by: Rahul Bansal <rbansal@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
[driver/sensor] lm90: Adding suspend-resume for nct1008. 2010-08-29T21:45:54+00:00 Laxman Dewangan ldewangan@nvidia.com 2010-08-12T09:17:24+00:00 7741beea207d8c45514ebb27e71056a672efbd84 Suspending the device nct1008 before going to suspend and reconfiguring at the time of system resume. This is implemneted for the nct1008 which is adt7461 type device. Change-Id: Iecfb33819d0427e2ab2bb1f8eed0066222e5793f Reviewed-on: http://git-master/r/4800 Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Bitan Biswas <bbiswas@nvidia.com> Tested-by: Bitan Biswas <bbiswas@nvidia.com> Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com> Tested-by: Suresh Mangipudi <smangipudi@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Suspending the device nct1008 before going to suspend
and reconfiguring at the time of system resume.

This is implemneted for the nct1008 which is adt7461 type
device.

Change-Id: Iecfb33819d0427e2ab2bb1f8eed0066222e5793f
Reviewed-on: http://git-master/r/4800
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Bitan Biswas <bbiswas@nvidia.com>
Tested-by: Bitan Biswas <bbiswas@nvidia.com>
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
tegra-fb : fix the panning 2010-08-27T19:05:24+00:00 Daehyoung Ko dko@nvidia.com 2010-08-27T17:20:17+00:00 0896d785822fe22b1d5b968a4bbd8dbf43ad3de3 Address should be calculated based on pitch not width Bug 709201 Change-Id: Ic2a73a9f665d212595bf4b61eeb7ea2984df7548 Reviewed-on: http://git-master/r/5718 Reviewed-by: Daehyoung Ko <dko@nvidia.com> Tested-by: Daehyoung Ko <dko@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> 
Address should be  calculated based on pitch not width

Bug 709201

Change-Id: Ic2a73a9f665d212595bf4b61eeb7ea2984df7548
Reviewed-on: http://git-master/r/5718
Reviewed-by: Daehyoung Ko <dko@nvidia.com>
Tested-by: Daehyoung Ko <dko@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
[arm/tegra] serial: Using double buffering in receive path. 2010-08-27T18:50:38+00:00 Laxman Dewangan ldewangan@nvidia.com 2010-08-19T11:48:43+00:00 bccaf58c73b6b9bb726b87b18d6e3b5d2b6e1106 To improve the performance in receive path, the uart configures the dma in the continuous double buffering mode. The dma keep filling the same buffer in continuously and inform uart driver when half of buffer completes. Change-Id: Iff7c9433766f272384fc1a329ff1db8031987544 Reviewed-on: http://git-master/r/4419 Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> Tested-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com> 
To improve the performance in receive path, the uart configures
the dma in the continuous double buffering mode. The dma keep
filling the same buffer in continuously and inform uart driver
when half of buffer completes.

Change-Id: Iff7c9433766f272384fc1a329ff1db8031987544
Reviewed-on: http://git-master/r/4419
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Yu-Huan Hsu <yhsu@nvidia.com>
[tegra-ehci] Fix Usb device detection for config USB_SUSPEND 2010-08-24T23:53:56+00:00 Venkat Moganty vmoganty@nvidia.com 2010-08-12T11:38:14+00:00 04dbd92636bdf1e4652d00d03c7a5a6ebbad8a4c When CONFIG_USB_SUSPEND is enabled USB device detection is not working. This is due to the wrong API called to resume the hub and HUB resume funtionality not happening properly. Fixed this by calling the correct API to resume the HUB driver when auto suspend is called. Bug 713237 Bug 713966 Change-Id: Ia4d091fd29ea7ebfe5844cf5685fc5a86e66d12a Reviewed-on: http://git-master/r/4984 Reviewed-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
When CONFIG_USB_SUSPEND is enabled USB device detection is not working. This is
due to the wrong API called to resume the hub and HUB resume funtionality not
happening properly. Fixed this by calling the correct API to resume the HUB
driver when auto suspend is called.

Bug 713237
Bug 713966

Change-Id: Ia4d091fd29ea7ebfe5844cf5685fc5a86e66d12a
Reviewed-on: http://git-master/r/4984
Reviewed-by: Abhishek Aggarwal <aaggarwal@nvidia.com>
Tested-by: Abhishek Aggarwal <aaggarwal@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
[driver/hwmon] lm90: Adding nct1008 as supported list. 2010-08-19T20:41:58+00:00 Laxman Dewangan ldewangan@nvidia.com 2010-08-12T07:49:51+00:00 26fb5db1a0d0d75cb980c8070ea01d54a1a2a35b The ON semiconductor's temperature sensor NCT1008 is driver compatible with National semicondutor's LM90 driver. Adding NCT1008 as the list of lm90 driver id table. Change-Id: I3dcbe1cdd1441e5196239551265444ebb633a1a2 Reviewed-on: http://git-master.nvidia.com/r/5080 Tested-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
The ON semiconductor's temperature sensor NCT1008 is
driver compatible with National semicondutor's LM90
driver.
Adding NCT1008 as the list of lm90 driver id table.

Change-Id: I3dcbe1cdd1441e5196239551265444ebb633a1a2
Reviewed-on: http://git-master.nvidia.com/r/5080
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>
nvhost: Reimplement null kickoff functionality. 2010-08-19T13:09:18+00:00 Antoine Chauveau achauveau@nvidia.com 2010-08-11T07:55:17+00:00 d535635a14a7f5f82ab10456bd49e32c49285e00 For each channel submit where null kickoff is requested, we don't place the user's commands in the pushbuffer. All necessary context switches, syncpoint increments and waitbase increments do happen though. Bug 717235 Change-Id: I51c323729ea57993a5b52fb395ab90cb8608ee6b Reviewed-on: http://git-master/r/5091 Reviewed-by: Antoine Chauveau <achauveau@nvidia.com> Reviewed-by: Antti Hatala <ahatala@nvidia.com> Tested-by: Antti Hatala <ahatala@nvidia.com> 
For each channel submit where null kickoff is requested, we don't
place the user's commands in the pushbuffer. All necessary context
switches, syncpoint increments and waitbase increments do happen
though.

Bug 717235

Change-Id: I51c323729ea57993a5b52fb395ab90cb8608ee6b
Reviewed-on: http://git-master/r/5091
Reviewed-by: Antoine Chauveau <achauveau@nvidia.com>
Reviewed-by: Antti Hatala <ahatala@nvidia.com>
Tested-by: Antti Hatala <ahatala@nvidia.com>
tegra accelerometer: power management changes 2010-08-17T10:16:19+00:00 Venu Byravarasu vbyravarasu@nvidia.com 2010-08-10T04:42:05+00:00 a0dab997adbb9ee7163b07a06a87e670dd16e425 Added suspend and resume functionality to tegra accelerometer, for supporting LP0 on Ventana tested on Ventana-C bug 716080 Change-Id: Ib57b3f2f0d3bec77839f40226f79cd60e222a366 Reviewed-on: http://git-master/r/4836 Tested-by: Venu Byravarasu <vbyravarasu@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
Added suspend and resume functionality to tegra
accelerometer, for supporting LP0 on Ventana

tested on Ventana-C
bug 716080
Change-Id: Ib57b3f2f0d3bec77839f40226f79cd60e222a366
Reviewed-on: http://git-master/r/4836
Tested-by: Venu Byravarasu <vbyravarasu@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
[arm/tegra] Serial: Confirming configured baudrate. 2010-08-17T07:35:54+00:00 Laxman Dewangan ldewangan@nvidia.com 2010-08-10T11:51:20+00:00 6538f1285df4f8c0381b9995d8fd74b866119ebe Sometimes, in uart, the desired baudrate can not be configured in 5% error accuracy due to not finding the correct combination of clock source freq and integer divisor. In this case the driver should generate the error message. Change-Id: Iafe245876a2cb9810c1025c02a4b6a36eb26aa4c Reviewed-on: http://git-master/r/4974 Tested-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> 
Sometimes, in uart, the desired baudrate can not be configured
in 5% error accuracy due to not finding the correct combination
of clock source freq and integer divisor. In this case the driver
should generate the error message.

Change-Id: Iafe245876a2cb9810c1025c02a4b6a36eb26aa4c
Reviewed-on: http://git-master/r/4974
Tested-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Gary King <gking@nvidia.com>