linux-toradex.git/include/linux, branch T20_LinuxImageV2.0_20130305 Linux kernel for Apalis and Colibri modules fbcon: logo: allow easy integration of a custom Linux boot logo 2013-01-25T15:10:50+00:00 Marcel Ziswiler marcel.ziswiler@toradex.com 2013-01-25T15:10:50+00:00 fa2371bff9ac03581881849d8f95678ef3992719 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. 
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 Marcel Ziswiler marcel.ziswiler@toradex.com 2013-01-09T15:36:16+00:00 4aa5a91d37aad0f186f0e5b4863340c7d640d083 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. 
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 Marcel Ziswiler marcel.ziswiler@toradex.com 2013-01-07T13:20:43+00:00 7cea39b9b7c6c82f74b5e624a534c4c2a3b5e317 In order to allow integrating with external thermal throttling code add a probe callback and remote over-temperature shutdown hooks. 
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 Marcel Ziswiler marcel.ziswiler@toradex.com 2013-01-07T07:18:12+00:00 5028e99a19fa01c9d1ed426e168fa6fd15feefb3 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. 
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 Marcel Ziswiler marcel.ziswiler@toradex.com 2012-11-12T14:28:39+00:00 f987e832a9e79d2ce8009a5ea9c7b677624b3b30 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 
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
Merge branch 'l4t/l4t-r16' into colibri 2012-09-10T13:04:19+00:00 Marcel Ziswiler marcel.ziswiler@toradex.com 2012-09-10T12:53:27+00:00 d5bbf34613a877dbe3da847fa0432da8c6721e73 Merge with latest NVIDIA L4T R16. Only real conflict concerning inverted VBUS gpio support. 
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 Ming Lei tom.leiming@gmail.com 2012-04-26T03:33:46+00:00 6f61e5baa83ef8c75746eabe90be0588f6d86b37 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 <huajun.li.lee@gmail.com> Signed-off-by: Ming Lei <tom.leiming@gmail.com> Cc: Oliver Neukum <oneukum@suse.de> Cc: stable@kernel.org Signed-off-by: David S. Miller <davem@davemloft.net> (cherry picked from commit 5b6e9bcdeb65634b4ad604eb4536404bbfc62cfa) Bug 1040642 Change-Id: I1a8c248016529bebf71d540738ad4726cf3f59b7 Signed-off-by: Steve Lin <stlin@nvidia.com> Reviewed-on: http://git-master/r/128693 GVS: Gerrit_Virtual_Submit 
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 <huajun.li.lee@gmail.com>
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Cc: Oliver Neukum <oneukum@suse.de>
Cc: stable@kernel.org
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit 5b6e9bcdeb65634b4ad604eb4536404bbfc62cfa)

Bug 1040642

Change-Id: I1a8c248016529bebf71d540738ad4726cf3f59b7
Signed-off-by: Steve Lin <stlin@nvidia.com>
Reviewed-on: http://git-master/r/128693
GVS: Gerrit_Virtual_Submit
video: tegra: host: Disable irq when clock gating 2012-08-29T14:23:54+00:00 Terje Bergstrom tbergstrom@nvidia.com 2012-08-22T06:16:51+00:00 63644abd0d4ed41c5f6894e273a41968ea09694e 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 <tbergstrom@nvidia.com> Reviewed-on: http://git-master/r/125129 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Juha Tukkinen <jtukkinen@nvidia.com> 
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 <tbergstrom@nvidia.com>
Reviewed-on: http://git-master/r/125129
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Juha Tukkinen <jtukkinen@nvidia.com>
E1853 BRINGUP Linux Snor: Micron Support 2012-08-29T01:11:35+00:00 Bob Johnston bjohnston@nvidia.com 2012-08-16T14:52:14+00:00 e3d92859c4351847a98e48746fb19d12fac16c6d Expanding NOR functionality to work with ADMUX and Burst mode for Micron Support in E1853. Bug 989919 Bug 966833 - Adding fields for picking MUX vs NONMUX and picking Async, Paging, Burst mode for reads - Added run time decision between them - 1853 specific settings for Async NOR - 1852 specific settings for NOR - 1853 NOR timings changed Reviewed-on: http://git-master/r/122286 (cherry picked from commit a242e7194c7de559d22fe5b275a8782086f10e50) Change-Id: I79de1d52d4c7199c83b380c2fa6d8cae6b35f09d Signed-off-by: Bob Johnston <BJohnston@nvidia.com> Reviewed-on: http://git-master/r/124946 Tested-by: Bob Johnston <bjohnston@nvidia.com> Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Sumeet Gupta <sumeetg@nvidia.com> Reviewed-by: Varun Wadekar <vwadekar@nvidia.com> 
Expanding NOR functionality to work with ADMUX and Burst mode for Micron
Support in E1853.

Bug 989919
Bug 966833
- Adding fields for picking MUX vs NONMUX and picking Async, Paging,
Burst mode for reads
- Added run time decision between them
- 1853 specific settings for Async NOR
- 1852 specific settings for NOR
- 1853 NOR timings changed

Reviewed-on: http://git-master/r/122286
(cherry picked from commit a242e7194c7de559d22fe5b275a8782086f10e50)
Change-Id: I79de1d52d4c7199c83b380c2fa6d8cae6b35f09d
Signed-off-by: Bob Johnston <BJohnston@nvidia.com>
Reviewed-on: http://git-master/r/124946
Tested-by: Bob Johnston <bjohnston@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Sumeet Gupta <sumeetg@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
drivers: mfd: Add support for TI aic3262 driver 2012-08-28T02:09:03+00:00 Manoj Gangwal mgangwal@nvidia.com 2012-08-22T10:15:42+00:00 838e65e50a1d0ad52b068ba26f178fac843a1dc3 Bug 1034241 Change-Id: I5607d53cf0bdd25c5e2b8447cd7e676b64cd32a2 Signed-off-by: Manoj Gangwal <mgangwal@nvidia.com> Reviewed-on: http://git-master/r/125169 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Lokesh Pathak <lpathak@nvidia.com> 
Bug 1034241

Change-Id: I5607d53cf0bdd25c5e2b8447cd7e676b64cd32a2
Signed-off-by: Manoj Gangwal <mgangwal@nvidia.com>
Reviewed-on: http://git-master/r/125169
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Lokesh Pathak <lpathak@nvidia.com>