linux-toradex.git/include/linux, branch tegra-10.11.7 Linux kernel for Apalis and Colibri modules arm: tegra: Remove executable bit from source files 2011-04-06T19:26:35+00:00 Robert Morell rmorell@nvidia.com 2011-04-05T22:42:10+00:00 b4e34f814e34a734dddc96b8919dc256dcd41f60 Generated with the script: find \( -name "*.c" -or -name "*.h" -or -name "*akefile" -or \ -name "*\.mk" \) -type f -perm /+x | xargs chmod -x Change-Id: Iabae1aa20fd49a1c8db439fc132182d0f629deab Reviewed-on: http://git-master/r/26806 Reviewed-by: Robert Morell <rmorell@nvidia.com> Tested-by: Robert Morell <rmorell@nvidia.com> Reviewed-by: Janne Hellsten <jhellsten@nvidia.com> 
Generated with the script:
find \( -name "*.c" -or -name "*.h" -or -name "*akefile" -or \
    -name "*\.mk" \) -type f -perm /+x | xargs chmod -x

Change-Id: Iabae1aa20fd49a1c8db439fc132182d0f629deab
Reviewed-on: http://git-master/r/26806
Reviewed-by: Robert Morell <rmorell@nvidia.com>
Tested-by: Robert Morell <rmorell@nvidia.com>
Reviewed-by: Janne Hellsten <jhellsten@nvidia.com>
i2c: buses: tegra: assign unused address to i2c slave 2011-04-05T00:59:06+00:00 Nitin Kumbhar nkumbhar@nvidia.com 2011-04-01T14:08:30+00:00 bdf0b4ce59907edd0523c5fb29a02e53a8e66a13 New i2c slave should be configured with a non-zero i2c address. Configure i2c slave with an i2c address assigned by platform data for an i2c dev. BUG 788286 Reviewed-on: http://git-master/r/25100 (cherry picked from commit e6e0610c72ffce3b734e079faf88fad3f0468d07) Change-Id: I440aa2cc72007d2835b2027c0b26089d0aad9263 Reviewed-on: http://git-master/r/25223 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com> 
New i2c slave should be configured with a non-zero i2c address.
Configure i2c slave with an i2c address assigned by platform
data for an i2c dev.

BUG 788286

Reviewed-on: http://git-master/r/25100
(cherry picked from commit e6e0610c72ffce3b734e079faf88fad3f0468d07)

Change-Id: I440aa2cc72007d2835b2027c0b26089d0aad9263
Reviewed-on: http://git-master/r/25223
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
serial: 8250: support auto control of RTSCTS on tegra type 2011-03-29T06:49:40+00:00 Pradeep Goudagunta pgoudagunta@nvidia.com 2011-03-28T11:02:40+00:00 66fa9abefccdc75f6feb283ac60acacd257dcc99 Add UART_CAP_HW_CTSRTS flag to tegra type for supporting auto control of RTSCTS. Bug 803910 Change-Id: I7b69e4b203e66903ba5755338fcb55f4a87b9a43 Reviewed-on: http://git-master/r/24463 Tested-by: Pradeep Goudagunta <pgoudagunta@nvidia.com> Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
Add UART_CAP_HW_CTSRTS flag to tegra type for supporting auto control
of RTSCTS.

Bug 803910

Change-Id: I7b69e4b203e66903ba5755338fcb55f4a87b9a43
Reviewed-on: http://git-master/r/24463
Tested-by: Pradeep Goudagunta <pgoudagunta@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
video: pwm_backlight: Add check_fb hook 2011-03-23T00:34:50+00:00 Robert Morell rmorell@nvidia.com 2011-03-04T03:33:42+00:00 b334e8443ed875a89854f9f8639f1f17f030cb5c In systems with multiple framebuffer devices, one of the devices might be blanked while another is unblanked. In order for the backlight blanking logic to know whether to turn off the backlight for a particular framebuffer's blanking notification, it needs to be able to check if a given framebuffer device corresponds to the backlight. This plumbs the check_fb hook from core backlight through the pwm_backlight helper to allow platform code to plug in a check_fb hook. Originally reviewed on http://git-master/r/21716 Reviewed-on: http://git-master/r/23100 (cherry picked from commit c7831cb27fc6a2701b020676a6daf9c76e9470d9) Change-Id: I32895d6f2c5988b09680a350e169f1f3c9b56da6 Reviewed-on: http://git-master/r/23725 Reviewed-by: Robert Morell <rmorell@nvidia.com> Tested-by: Gaurav Sarode <gsarode@nvidia.com> Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
In systems with multiple framebuffer devices, one of the devices might
be blanked while another is unblanked.  In order for the backlight
blanking logic to know whether to turn off the backlight for a
particular framebuffer's blanking notification, it needs to be able to
check if a given framebuffer device corresponds to the backlight.

This plumbs the check_fb hook from core backlight through the
pwm_backlight helper to allow platform code to plug in a check_fb hook.

Originally reviewed on http://git-master/r/21716

Reviewed-on: http://git-master/r/23100
(cherry picked from commit c7831cb27fc6a2701b020676a6daf9c76e9470d9)

Change-Id: I32895d6f2c5988b09680a350e169f1f3c9b56da6
Reviewed-on: http://git-master/r/23725
Reviewed-by: Robert Morell <rmorell@nvidia.com>
Tested-by: Gaurav Sarode <gsarode@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
backlight: add low threshold to pwm backlight 2011-03-23T00:34:34+00:00 Arun Murthy arun.murthy@stericsson.com 2010-11-11T22:05:28+00:00 503bdb0afcc819d79b18d6786127bd8c988cfae4 The intensity of the backlight can be varied from a range of max_brightness to zero. Though most, if not all the pwm based backlight devices start flickering at lower brightness value. And also for each device there exists a brightness value below which the backlight appears to be turned off though the value is not equal to zero. If the range of brightness for a device is from zero to max_brightness. A graph is plotted for brightness Vs intensity for the pwm based backlight device has to be a linear graph. intensity | / | / | / |/ --------- 0 max_brightness But pratically on measuring the above we note that the intensity of backlight goes to zero(OFF) when the value in not zero almost nearing to zero(some x%). so the graph looks like intensity | / | / | / | | ------------ 0 x max_brightness In order to overcome this drawback knowing this x% i.e nothing but the low threshold beyond which the backlight is off and will have no effect, the brightness value is being offset by the low threshold value(retaining the linearity of the graph). Now the graph becomes intensity | / | / | / | / ------------- 0 max_brightness With this for each and every digit increment in the brightness from zero there is a change in the intensity of backlight. Devices having this behaviour can set the low threshold brightness(lth_brightness) and pass the same as platform data else can have it as zero. [akpm@linux-foundation.org: coding-style fixes] Signed-off-by: Arun Murthy <arun.murthy@stericsson.com> Acked-by: Linus Walleij <linus.walleij@stericsson.com> Acked-by: Richard Purdie <rpurdie@linux.intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Reviewed-on: http://git-master/r/23099 (cherry picked from commit 92db79791aa60cacb3fa90d1cb2e942420c29408) Change-Id: Icbe49b593dfa6608934ff274b4c9281e43c30b5c Reviewed-on: http://git-master/r/23724 Tested-by: Gaurav Sarode <gsarode@nvidia.com> Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
The intensity of the backlight can be varied from a range of
max_brightness to zero.  Though most, if not all the pwm based backlight
devices start flickering at lower brightness value.  And also for each
device there exists a brightness value below which the backlight appears
to be turned off though the value is not equal to zero.

If the range of brightness for a device is from zero to max_brightness.  A
graph is plotted for brightness Vs intensity for the pwm based backlight
device has to be a linear graph.

intensity
	  |   /
	  |  /
	  | /
	  |/
	  ---------
	 0	max_brightness

But pratically on measuring the above we note that the intensity of
backlight goes to zero(OFF) when the value in not zero almost nearing to
zero(some x%).  so the graph looks like

intensity
	  |    /
	  |   /
	  |  /
	  |  |
	  ------------
	 0   x	 max_brightness

In order to overcome this drawback knowing this x% i.e nothing but the low
threshold beyond which the backlight is off and will have no effect, the
brightness value is being offset by the low threshold value(retaining the
linearity of the graph).  Now the graph becomes

intensity
	  |     /
	  |    /
	  |   /
	  |  /
	  -------------
	   0	  max_brightness

With this for each and every digit increment in the brightness from zero
there is a change in the intensity of backlight.  Devices having this
behaviour can set the low threshold brightness(lth_brightness) and pass
the same as platform data else can have it as zero.

[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Arun Murthy <arun.murthy@stericsson.com>
Acked-by: Linus Walleij <linus.walleij@stericsson.com>
Acked-by: Richard Purdie <rpurdie@linux.intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Reviewed-on: http://git-master/r/23099
(cherry picked from commit 92db79791aa60cacb3fa90d1cb2e942420c29408)

Change-Id: Icbe49b593dfa6608934ff274b4c9281e43c30b5c
Reviewed-on: http://git-master/r/23724
Tested-by: Gaurav Sarode <gsarode@nvidia.com>
Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
misc: mpu3050: Invensense MPU code update v3.3.3 2011-03-22T23:56:00+00:00 vsalve vsalve@nvidia.com 2011-03-15T09:59:43+00:00 6c0a2b4e0a1439a15d44ff6e24c286277dc489f0 Update Invensense Motion Library (MPL) to production version v3.3.3. Previous version was engineering release and is not suitable for mass production. This version of the MPL most notably fixes problems with suspend/resume where touch screen would quit working during a suspend/resume cycle. Change-Id: Ia33433a677862b3d1e31d410aac7176d7a381a8f Reviewed-on: http://git-master/r/22987 Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com> 
Update Invensense Motion Library (MPL) to production version
v3.3.3. Previous version was engineering release and is not
suitable for mass production. This version of the MPL most
notably fixes problems with suspend/resume where touch screen
would quit working during a suspend/resume cycle.

Change-Id: Ia33433a677862b3d1e31d410aac7176d7a381a8f
Reviewed-on: http://git-master/r/22987
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
[TPS658x RTC] Correct reg RTC_CTRL usage 2011-03-18T05:20:32+00:00 David Schalig dschalig@nvidia.com 2011-03-10T12:49:33+00:00 3da45a03a1af70e308592727ac134ce9d30d6b0f Correct PRE_BYPASS (clock scaler 32kHz/1kHz select) bitfield. Add platform data to tune RTC XTAL capacitance in board file. Bug 798832, Tested on Ventana/wake via Alarm Clock Change-Id: I82d67610a815866707fc1db934d7d4d7cf93d883 Reviewed-on: http://git-master/r/22402 Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com> Reviewed-by: David Schalig <dschalig@nvidia.com> Reviewed-by: Jonathan Mayo <jmayo@nvidia.com> 
Correct PRE_BYPASS (clock scaler 32kHz/1kHz select) bitfield.

Add platform data to tune RTC XTAL capacitance in board file.

Bug 798832, Tested on Ventana/wake via Alarm Clock

Change-Id: I82d67610a815866707fc1db934d7d4d7cf93d883
Reviewed-on: http://git-master/r/22402
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
Reviewed-by: David Schalig <dschalig@nvidia.com>
Reviewed-by: Jonathan Mayo <jmayo@nvidia.com>
regulator: tps6586x: add PFM/PWM options on SMs supply 2011-03-18T05:17:30+00:00 Xin Xie xxie@nvidia.com 2011-03-12T03:04:15+00:00 52874d785a2a9e2a8f819635faac36942596375f TPS6586x SM0, SM1 and SM2 port have 2 power switching modes: - PWM only, or - PMW-PFM auto mode Some of TPS6586x have voltage spike in PFM-to-FWM transition can lockup the CPU if choose PWM-PFM auto mode. This patch enables such mode selection on SMs ports from the board level power configuration file. BUG 796364 Change-Id: I7015798151d6753ff5dcc329703338fde105e2b0 Reviewed-on: http://git-master/r/22701 Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com> Reviewed-by: Xin Xie <xxie@nvidia.com> Tested-by: Xin Xie <xxie@nvidia.com> 
TPS6586x SM0, SM1 and SM2 port have 2 power switching modes:
 - PWM only, or
 - PMW-PFM auto mode

Some of TPS6586x have voltage spike in PFM-to-FWM transition can lockup
the CPU if choose PWM-PFM auto mode.

This patch enables such mode selection on SMs ports from the board level
power configuration file.

BUG 796364

Change-Id: I7015798151d6753ff5dcc329703338fde105e2b0
Reviewed-on: http://git-master/r/22701
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
Reviewed-by: Xin Xie <xxie@nvidia.com>
Tested-by: Xin Xie <xxie@nvidia.com>
mfd: max8907c: Add api to power off max8907c 2011-03-11T05:42:10+00:00 Prashant Gaikwad pgaikwad@nvidia.com 2011-03-10T10:53:37+00:00 8bb77ffa20e159e611ac3c629cce6fdc3db26f00 Add an api to power off max8907c by setting power off bit in RESET_CNFG reg. Bug 799957 Bug 800602 (Cold boot) Change-Id: Ie0206d684a86fecc75273c1d3b087bb2d47b4c56 Reviewed-on: http://git-master/r/22385 Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
Add an api to power off max8907c by setting power off bit in RESET_CNFG reg.

Bug 799957
Bug 800602 (Cold boot)

Change-Id: Ie0206d684a86fecc75273c1d3b087bb2d47b4c56
Reviewed-on: http://git-master/r/22385
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
merge: trivial updates resolved from upstream 2011-03-10T02:58:05+00:00 Dan Willemsen dwillemsen@nvidia.com 2011-03-08T08:21:01+00:00 13b02f59ca1c86f3fec3c994d2c03ff52f7d8e7f * Move include/linux/tegra_usb.h to include/linux/platform_data/tegra_usb.h Change-Id: I5b7799c5af8029b15ad206978718b337afac8814 Reviewed-on: http://git-master/r/22165 Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com> Tested-by: Daniel Willemsen <dwillemsen@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Nitin Kumbhar <nkumbhar@nvidia.com> 
* Move include/linux/tegra_usb.h to
  include/linux/platform_data/tegra_usb.h

Change-Id: I5b7799c5af8029b15ad206978718b337afac8814
Reviewed-on: http://git-master/r/22165
Reviewed-by: Daniel Willemsen <dwillemsen@nvidia.com>
Tested-by: Daniel Willemsen <dwillemsen@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Nitin Kumbhar <nkumbhar@nvidia.com>