linux-toradex.git/drivers, branch tegra-11.2.6 Linux kernel for Apalis and Colibri modules nvrm: move stale wait checking into the kernel 2011-05-16T22:15:20+00:00 Chris Johnson cwj@nvidia.com 2011-04-30T21:24:44+00:00 6d8d2c454e835f7cfe34371e07dac173f3153452 The kernel now receives wait tracking data (similar to gathers and relocs) and compares the current syncpt with the threshold value. If it's old, it gets a kernel mapping and rewrites the method data to use a kernel reserved syncpt that is always 0 (so trivially pops when seen by the HW). Bug 519650 Bug 785525 Bug 803452 Note: reset the author in this commit to fix a email addr problem and since from the latest/last cherry pick there was a reworking of the code to be compatible with different user space versions it also seemed reasonable. (cherry picked from commit 4069d8e67665624ad3dceb628e572980dd57acd0) (cherry picked from commit 6e4336408588e348804a62e53386acc9abc06823) (cherry picked from commit 87a9efe751716ca741caac72b9061fdfdcec540a) Change-Id: I9c6076da2384f373d5f402bee4406b09b4ebc4ff Reviewed-on: http://git-master/r/23159 Reviewed-on: http://git-master/r/30281 Tested-by: Chris Johnson <cwj@nvidia.com> Reviewed-by: Ken Adams <kadams@nvidia.com> Reviewed-by: Prajakta Gudadhe <pgudadhe@nvidia.com> 
The kernel now receives wait tracking data (similar to gathers and
relocs) and compares the current syncpt with the threshold value.

If it's old, it gets a kernel mapping and rewrites the method data
to use a kernel reserved syncpt that is always 0 (so trivially pops
when seen by the HW).

Bug 519650
Bug 785525
Bug 803452

Note: reset the author in this commit to fix a email addr problem
and since from the latest/last cherry pick there was a reworking
of the code to be compatible with different user space versions
it also seemed reasonable.

(cherry picked from commit 4069d8e67665624ad3dceb628e572980dd57acd0)
(cherry picked from commit 6e4336408588e348804a62e53386acc9abc06823)
(cherry picked from commit 87a9efe751716ca741caac72b9061fdfdcec540a)

Change-Id: I9c6076da2384f373d5f402bee4406b09b4ebc4ff
Reviewed-on: http://git-master/r/23159
Reviewed-on: http://git-master/r/30281
Tested-by: Chris Johnson <cwj@nvidia.com>
Reviewed-by: Ken Adams <kadams@nvidia.com>
Reviewed-by: Prajakta Gudadhe <pgudadhe@nvidia.com>
ARM: tegra: dc: clip invalid windows to screen res 2011-05-10T23:09:01+00:00 Jon Mayo jmayo@nvidia.com 2011-04-29T03:25:13+00:00 c8bde2d8332d313b04856377cb95ccd555051a0e clip invalid windows to fix screen size, failure to do so causes display errors that result in corrupted display and invalid video modes. prints a warning only once, if this warning is present in the logs then there is a misbehaving application. Bug 821094 (cherry picked from commit e08f18eba00bd5d86cb7770f709417a1bd0ca14f) Change-Id: Ie5cec5c805bfe2bd4c5f1e5b7e22d5f255ca2680 Reviewed-on: http://git-master/r/30587 Reviewed-by: Varun Colbert <vcolbert@nvidia.com> Tested-by: Varun Colbert <vcolbert@nvidia.com> 
clip invalid windows to fix screen size, failure to do so causes display
errors that result in corrupted display and invalid video modes.
prints a warning only once, if this warning is present in the logs then
there is a misbehaving application.

Bug 821094

(cherry picked from commit e08f18eba00bd5d86cb7770f709417a1bd0ca14f)

Change-Id: Ie5cec5c805bfe2bd4c5f1e5b7e22d5f255ca2680
Reviewed-on: http://git-master/r/30587
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
usb: tegra: set sclk rate 2011-05-10T23:05:30+00:00 Prashant Gaikwad pgaikwad@nvidia.com 2011-04-26T05:34:48+00:00 a14aa5572e32649156c4b755219a07e68b7af5e2 sclk minimum rate is set to 40MHz which is less than required by usb. set sclk rate to 80MHz when usb is connected and disable sclk when usb is not connected so that sclk will get clocked at minimum rate. Bug 819796 Reviewed-on: http://git-master/r/28766 (cherry picked from commit e705e6b448791ef938a0897755205cdde72fa361) Change-Id: I180d044f788e153d0057355e22ed422f32552d5c Reviewed-on: http://git-master/r/30818 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com> 
sclk minimum rate is set to 40MHz which is less than required by usb.
set sclk rate to 80MHz when usb is connected and disable sclk when usb is
not connected so that sclk will get clocked at minimum rate.

Bug 819796

Reviewed-on: http://git-master/r/28766
(cherry picked from commit e705e6b448791ef938a0897755205cdde72fa361)

Change-Id: I180d044f788e153d0057355e22ed422f32552d5c
Reviewed-on: http://git-master/r/30818
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
serial: core: Restore termios settings on resume console ports 2011-05-10T01:00:22+00:00 Vandana Salve vsalve@nvidia.com 2011-05-06T06:51:01+00:00 952e0e908ab4dcd61eaab0ad8fef3e42fe5f8fce The commit 4547be7 rewrites suspend and resume functions. According to this rewrite, when a serial port is a printk console device and can suspend(without set no_console_suspend flag), it will definitely call set_termios function during its resume, but parameter termios isn't initialized, this will pass an unpredictable config to the serial port. If this serial port is not a userspace opened tty device , a suspend and resume action will make this serial port unusable. I.E. ttyS0 is a printk console device, ttyS1 or keyboard+display is userspace tty device, a suspend/resume action will make ttyS0 unusable. If a serial port is both a printk console device and an opened tty device, this issue can be overcome because it will call set_termios again with the correct parameter in the uart_change_speed function. Refer to the deleted content of commit 4547be7, revert parts relate to restore settings into parameter termios. It is safe because if a serial port is a printk console only device, the only meaningful field in termios is c_cflag and its old config is saved in uport->cons->cflag, if this port is also an opened tty device, it will clear uport->cons->cflag in the uart_open and the old config is saved in tty->termios. refer http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.37.y.git; a=commit;h=891b9dd10764352926e1e107756aa229dfa2c210 cherry-pick the changes from the kernel 2.6.37 commit id :891b9dd10764352926e1e107756aa229dfa2c210 Cherry-picked http://git-master/r/#change,20302 Bug 819016 Change-Id: Ic7ce0a6d595c0e1f65285d7978db93be12158f0f Reviewed-on: http://git-master/r/30680 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com> 
The commit 4547be7 rewrites suspend and resume functions. According
to this rewrite, when a serial port is a printk console device and
can suspend(without set no_console_suspend flag), it will definitely
call set_termios function during its resume, but parameter termios
isn't initialized, this will pass an unpredictable config to the
serial port. If this serial port is not a userspace opened tty device
, a suspend and resume action will make this serial port unusable.
I.E. ttyS0 is a printk console device, ttyS1 or keyboard+display is
userspace tty device, a suspend/resume action will make ttyS0
unusable.

If a serial port is both a printk console device and an opened tty
device, this issue can be overcome because it will call set_termios
again with the correct parameter in the uart_change_speed function.

Refer to the deleted content of commit 4547be7, revert parts relate
to restore settings into parameter termios. It is safe because if
a serial port is a printk console only device, the only meaningful
field in termios is c_cflag and its old config is saved in
uport->cons->cflag, if this port is also an opened tty device,
it will clear uport->cons->cflag in the uart_open and the old config
is saved in tty->termios.

refer http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.37.y.git;
a=commit;h=891b9dd10764352926e1e107756aa229dfa2c210

cherry-pick the changes from the kernel 2.6.37 commit id
:891b9dd10764352926e1e107756aa229dfa2c210

Cherry-picked http://git-master/r/#change,20302

Bug 819016

Change-Id: Ic7ce0a6d595c0e1f65285d7978db93be12158f0f
Reviewed-on: http://git-master/r/30680
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
video: tegra: dc: handle error condition 2011-05-10T01:00:08+00:00 Amit Kamath akamath@nvidia.com 2011-04-27T12:23:43+00:00 6d750e0fafe6833b7d59abf576e5a9c536919e02 Do not handle requests further for displays that are not enabled Bug 813310 Bug 813728 Reviewed-on: http://git-master/r/29515 (cherry picked from commit 22578f1d7065ea84855fdbcaf09a792e9f9d3856) Change-Id: I1fa907e33f2d250fff64752c8f0e26de51f3655b Reviewed-on: http://git-master/r/30672 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Bharat Nihalani <bnihalani@nvidia.com> 
Do not handle requests further for displays that are not enabled

Bug 813310
Bug 813728

Reviewed-on: http://git-master/r/29515
(cherry picked from commit 22578f1d7065ea84855fdbcaf09a792e9f9d3856)

Change-Id: I1fa907e33f2d250fff64752c8f0e26de51f3655b
Reviewed-on: http://git-master/r/30672
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
usb: fsl_udc: Resume of device mode optimized. 2011-05-10T00:59:12+00:00 Suresh Mangipudi smangipudi@nvidia.com 2011-05-05T12:48:52+00:00 cae416e076b8c31c422b71b6df82a7921132ee11 Having the device resume and suspend when the cable is not present is an overhead for the system. Hence removed resume and device function calls when the cable is not present. Bug 803280 Change-Id: I238474fb1f3629f78833d58a89ffcabff7754fbb Reviewed-on: http://git-master/r/30500 Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com> Tested-by: Suresh Mangipudi <smangipudi@nvidia.com> Reviewed-by: Rakesh Bodla <rbodla@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
Having the device resume and suspend when the cable is not present is
an overhead for the system. Hence removed resume and device function
calls when the cable is not present.

Bug 803280

Change-Id: I238474fb1f3629f78833d58a89ffcabff7754fbb
Reviewed-on: http://git-master/r/30500
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Rakesh Bodla <rbodla@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
crypto: tegra-aes: performance optimisations 2011-05-10T00:59:01+00:00 Varun Wadekar vwadekar@nvidia.com 2011-05-03T11:55:56+00:00 aefcb5131be5fc4d252e0f6489cf9d6d90b9cea8 * set bsea sclk to ulong_max * use unbounded work queues with 1 max_active work item on each of them * clear INTR_STATUS per operation * free nvmap handle after using it Bug 803932 Change-Id: I9e46d86891f0026504ca4ab2f0c6da5776bb9a73 Signed-off-by: Varun Wadekar <vwadekar@nvidia.com> Reviewed-on: http://git-master/r/30196 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
* set bsea sclk to ulong_max
* use unbounded work queues with 1 max_active
  work item on each of them
* clear INTR_STATUS per operation
* free nvmap handle after using it

Bug 803932

Change-Id: I9e46d86891f0026504ca4ab2f0c6da5776bb9a73
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/30196
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
media: video: tegra: avp: set sclk rate 2011-05-07T03:24:27+00:00 Prashant Gaikwad pgaikwad@nvidia.com 2011-04-26T05:31:32+00:00 e6afc94c9bb6ee865a9dc2d546e792cc87ec407f sclk is shared between usb and avp. usb sets it to 80MHz, hence set sclk rate to max when avp is running. Bug 819796 Reviewed-on: http://git-master/r/28765 (cherry picked from commit 44234ba7be2de25ef79b803747064ce54f6dc081) Change-Id: Iea5c785da0aff69f61c82f7e67356d93ead1d994 Reviewed-on: http://git-master/r/30314 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com> 
sclk is shared between usb and avp. usb sets it to 80MHz, hence set sclk rate
to max when avp is running.

Bug 819796

Reviewed-on: http://git-master/r/28765
(cherry picked from commit 44234ba7be2de25ef79b803747064ce54f6dc081)

Change-Id: Iea5c785da0aff69f61c82f7e67356d93ead1d994
Reviewed-on: http://git-master/r/30314
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
tegra:otg: Fix clock disable to match ref count 2011-05-04T17:56:13+00:00 Bitan Biswas bbiswas@nvidia.com 2011-03-04T16:03:13+00:00 ac3f62effd31f2b9654f81cd1538f9a16dbd5f9f usbd clock is enabled during the probe and not disabled after the functionality. Due to this clock reference count is non-zero and hence usbd clock is not disabled during suspend. Fixed this by disabling clock appropriately. - Since clocks are now turned off during suspend clock needs to be enabled during fsl_udc_resume. Bug 793834 Reviewed-on: http://git-master/r/21652 (cherry picked from commit 8fa46a6da22e6def221435098de054e55c7d1196) Reviewed-on: http://git-master/r/22999 (cherry picked from commit 7ca37264ae9f7358afea2622fa35b928391f8561) Change-Id: I9f39696e04674e76fb088e9eee498153f981bac6 Reviewed-on: http://git-master/r/30075 Reviewed-by: Bitan Biswas <bbiswas@nvidia.com> Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com> Tested-by: Suresh Mangipudi <smangipudi@nvidia.com> Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
usbd clock is enabled during the probe and not disabled after the
functionality. Due to this clock reference count is non-zero and hence
usbd clock is not disabled during suspend. Fixed this by disabling
clock appropriately.
 - Since clocks are now turned off during suspend clock
   needs to be enabled during fsl_udc_resume.

Bug 793834

Reviewed-on: http://git-master/r/21652
(cherry picked from commit 8fa46a6da22e6def221435098de054e55c7d1196)

Reviewed-on: http://git-master/r/22999
(cherry picked from commit 7ca37264ae9f7358afea2622fa35b928391f8561)

Change-Id: I9f39696e04674e76fb088e9eee498153f981bac6
Reviewed-on: http://git-master/r/30075
Reviewed-by: Bitan Biswas <bbiswas@nvidia.com>
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
usb: host: tegra: PORTSC.SUSP needs a delay 2011-05-03T01:04:23+00:00 Suresh Mangipudi smangipudi@nvidia.com 2011-04-12T14:10:35+00:00 e6354059de6a1231bf340753657bbb4ef16c17a0 Delay of 4ms is needed after the SUSPEND bit in the PORTSC register is programmed. The hardware would be set only after 4ms of delay. Bug 812427 Change-Id: I5253928264112b429f78e6682e261a44820811db Reviewed-on: http://git-master/r/27510 Reviewed-on: http://git-master/r/29974 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com> Tested-by: Suresh Mangipudi <smangipudi@nvidia.com> 
Delay of 4ms is needed after the SUSPEND bit in the PORTSC register is
programmed. The hardware would be set only after 4ms of delay.

Bug 812427

Change-Id: I5253928264112b429f78e6682e261a44820811db
Reviewed-on: http://git-master/r/27510
Reviewed-on: http://git-master/r/29974
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Suresh Mangipudi <smangipudi@nvidia.com>
Tested-by: Suresh Mangipudi <smangipudi@nvidia.com>