linux-toradex.git/include, branch T20_LinuxImageV2.0_20130305

fbcon: logo: allow easy integration of a custom Linux boot logo

2013-01-25T15:10:50+00:00

This patch allows for easy integration of a custom Linux boot logo to
replace the Tux' being shown by default.

Use gimp or the like to create a raw PPM in your desired resolution.

Reduce the number of colours in the image to 224:

  user@host:~$ ppmquant 224 Toradex-640x480.ppm > \
    Toradex-640x480-224.ppm
  ppmquant: making histogram...
  ppmquant: 370 colors found
  ppmquant: choosing 224 colors...
  ppmquant: mapping image to new colors...

Convert it from raw PPM to ASCII format:

  user@host:~$ pnmnoraw Toradex-640x480-224.ppm > \
    Toradex-640x480-ascii-224.ppm

Copy it into the Linux sources:

  cp Toradex-640x480-ascii-224.ppm linux-toradex/drivers/video/logo/\
    logo_custom_clut224.ppm

Activate exclusively custom Linux logo in the kernel configuration:

  Device Drivers -> Graphics support -> Bootup logo ->
    Custom 224-color Linux logo

And re-compile the kernel.

hwmon: lm95245: add local temp and remote critical shutdown temp hooks

2013-01-09T15:36:16+00:00

In order to allow tighter integration with external thermal throttling
code add local temperature and remote critical shutdown temperature
hooks. Rename the existing hooks for clarity.

hwmon: lm95245: add probe callback and remote OS hooks

2013-01-07T13:22:20+00:00

In order to allow integrating with external thermal throttling code add
a probe callback and remote over-temperature shutdown hooks.

hwmon: lm95245: implement remote over-temperature shutdown alarm limit

2013-01-07T07:18:12+00:00

In addition to the critical temperature alarm limit this chip features
a second alarm limit called remote over-temperature shutdown ROS with
a separate pin configurable as trigger output. Implement this feature
and add platform data to allow configuring respective pin as output.

Merge branch 'l4t/l4t-r16-r2' into colibri

2012-11-12T14:28:39+00:00

Conflicts:
	arch/arm/mach-tegra/tegra3_usb_phy.c
	arch/arm/mach-tegra/usb_phy.c
	drivers/usb/gadget/tegra_udc.c
	drivers/usb/otg/Makefile
	drivers/video/tegra/fb.c
	sound/soc/tegra/tegra_pcm.c

WAR: gr3d: limit 3d clock when camera is on

2012-09-10T21:29:24+00:00

As WAR, limit 3d clock frequency and emc clock frequency
when camera is on and chip is AP37. 3d clock is set to
361MHz and 437MHz is requested for emc clock with this
change. This change allows 3d to request 1.1V in Core
instead of 1.3V in AP37.

Bug 1001262
Bug 1019309

Change-Id: I9f46f93d8da0fcf5afe05839177bf0d6e43a5840
Signed-off-by: Jihoon Bang 
Reviewed-on: http://git-master/r/130945
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Bharat Nihalani 
Tested-by: Bharat Nihalani

Merge branch 'l4t/l4t-r16' into colibri

2012-09-10T13:04:19+00:00

Merge with latest NVIDIA L4T R16.

Only real conflict concerning inverted VBUS gpio support.

usbnet: fix skb traversing races during unlink(v2)

2012-09-05T00:10:35+00:00

Commit 4231d47e6fe69f061f96c98c30eaf9fb4c14b96d(net/usbnet: avoid
recursive locking in usbnet_stop()) fixes the recursive locking
problem by releasing the skb queue lock before unlink, but may
cause skb traversing races:
	- after URB is unlinked and the queue lock is released,
	the refered skb and skb->next may be moved to done queue,
	even be released
	- in skb_queue_walk_safe, the next skb is still obtained
	by next pointer of the last skb
	- so maybe trigger oops or other problems

This patch extends the usage of entry->state to describe 'start_unlink'
state, so always holding the queue(rx/tx) lock to change the state if
the referd skb is in rx or tx queue because we need to know if the
refered urb has been started unlinking in unlink_urbs.

The other part of this patch is based on Huajun's patch:
always traverse from head of the tx/rx queue to get skb which is
to be unlinked but not been started unlinking.

Signed-off-by: Huajun Li 
Signed-off-by: Ming Lei 
Cc: Oliver Neukum 
Cc: stable@kernel.org
Signed-off-by: David S. Miller 
(cherry picked from commit 5b6e9bcdeb65634b4ad604eb4536404bbfc62cfa)

Bug 1040642

Change-Id: I1a8c248016529bebf71d540738ad4726cf3f59b7
Signed-off-by: Steve Lin 
Reviewed-on: http://git-master/r/128693
GVS: Gerrit_Virtual_Submit

ASoC: dapm: Use DAPM mutex for DAPM ops instead of codec mutex

2012-09-04T12:16:10+00:00

It has now become necessary to use a DAPM mutex instead of the codec
mutex to lock the DAPM operations. This is due to the recent multi
component support and forth coming Dynamic PCM updates.

Currently we lock DAPM operations with the codec mutex of the calling
RTD context. However, DAPM operations can span the whole card context
and all components.

This patch updates the DAPM operations that use the codec mutex to
now use the DAPM mutex PCM subclass for all DAPM ops.

We also add a mutex subclass for DAPM init and PCM operations.

Signed-off-by: Liam Girdwood 
Signed-off-by: Mark Brown 
(cherry picked from commit a73fb2df01866b772a48fab93401fe3edbe0b38d)

Updated call sequences

Bug 1039523

Change-Id: If079bbe5032971251d6b5426c752cbcc6ad6bcf5
Signed-off-by: Sang-Hun Lee 
Reviewed-on: http://git-master/r/128937
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Bharat Nihalani

video: tegra: host: Disable irq when clock gating

2012-08-29T14:23:54+00:00

Disable host1x interrupts when clock gating host1x. This fixes a race
where host1x interrupt was raised at the same time when host1x clock
is turned off.

Bug 1031724

Change-Id: I169cd5796608b8888a6b48ed99bb5da754559b2c
Signed-off-by: Terje Bergstrom 
Reviewed-on: http://git-master/r/125129
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Juha Tukkinen