Age | Commit message (Collapse) | Author |
|
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>
|
|
Merge updates from tegra_defconfig
Change-Id: I45a488f27c516a0f892eb394771302c68cd2aa6c
Reviewed-on: http://git-master/r/31257
Tested-by: Daniel Willemsen <dwillemsen@nvidia.com>
Reviewed-by: Andrei Denissov <adenissov@nvidia.com>
Reviewed-by: Jonathan B White (Engrg-Mobile) <jwhite@nvidia.com>
Reviewed-by: Daniel Willemsen <dwillemsen@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>
|
|
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>
|
|
Set the platform data for the USB1 host mode to NULL during the unregister.
After freeing up the platform data pointer.
Bug 820333
Change-Id: I6fb3edf58d854c0d8f648572f40cebe6811e2069
Reviewed-on: http://git-master/r/30696
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>
|
|
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>
|
|
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>
|
|
Change-Id: Ic3eb5d136be746b55bea4efe302e0f417dfc1eb6
Reviewed-on: http://git-master/r/30512
Tested-by: Manjula Gupta <magupta@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Scott Peterson <speterson@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>
|
|
* 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>
|
|
Bug 803932
Change-Id: Ia9cf3f20c6921fc18b02527c9c0108fd4f08e79b
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/30195
Reviewed-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
shared clock rate is dependent on its parent max rate. Parent's max rate
get updated in sku limit init depending on the sku value. Hence initialize
shared clocks after sku limits are applied.
Bug 821534
Change-Id: Ic11631cd54af638c8afa75aceeb4bcd999c8135f
Reviewed-on: http://git-master/r/30504
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
|
|
dynamic changing of pclk divider to follow APB clock minimum
frequency requirements with respect to sclk frequency.
Bug 819796
Reviewed-on: http://git-master/r/29643
(cherry picked from commit c5ed952608ff2e3ffdcba99295f8892dac1506c0)
Change-Id: Iec403b137fa001ff401fd14990040889ec679eca
Reviewed-on: http://git-master/r/30315
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Tested-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@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>
|
|
sclk continues to be clocked at 120MHz even when there is no activity.
Add dfs so that different modules can set sclk rate as required and it will
be clocked to minimum when there is no activity.
Minimum limit changed to 40MHz for sclk.
Bug 819796
Reviewed-on: http://git-master/r/28764
(cherry picked from commit ee17dca953c7eadc01a221a245a7e95d0fff33ea)
Change-Id: I78d4a6b699bb827de4d5cfa5ac621961d09d47de
Reviewed-on: http://git-master/r/30313
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
the fix add testcase for testing aes ofb mode.
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Bug 787628
cherry picked the following commit
http://git.kernel.org/?p=linux/kernel/git/herbert/
cryptodev-2.6.git;a=commit;h=ba0e14acc417eceb895efda1ff46366f4d1728f8
Change-Id: Ibcb554ac4971edd61c8141137fbe6178e2fb8209
Reviewed-on: http://git-master/r/30339
Tested-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Revise some default settings for utimp phy
Bug 815848
Change-Id: I7eac6981e52bdf6b33e80d34aebb0dc403b326bf
Reviewed-on: http://git-master/r/30257
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-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>
|
|
some testing revealed certain loopholes in the
code. also the way the shell sends data down to
the sysfs handlers changed which warranted the
change in the handlers.
Change-Id: I131ab43691321a864ad5afd4f9852a7ba8842130
Signed-off-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-on: http://git-master/r/30134
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
This is to make sure this function will not cause any lock-up
during actual reboot
Should help bug 770426
Change-Id: Id5cfaee07d9438741b721b67c7cd342858e7b5cb
Reviewed-on: http://git-master/r/28345
Reviewed-on: http://git-master/r/30176
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Disabling IRQ and FIQ before we stop other processor cores and start reboot
process will make sure the restart procedure is not preempted. This is to
prevent the potential lockup caused by the loss of synchronisation among
different processor cores due to IPI_STOP.
Should help bug 770426
Reviewed-on: http://git-master/r/27780
(cherry picked from commit 3d63b7709f3614783ebbf97568132458e5198c29)
Change-Id: I513a1f7394478b16f6c0204af7b31b18244ac819
Reviewed-on: http://git-master/r/30172
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
LDO_SHDN_L signals control AVDD_2P8V and VDD_AF_2P8V supplies to
camera sensor modules. Power on these supplies only when camera
is in use.
BUG 782390
Change-Id: Ifefbb0b4da0b9213c4a2f76b51bcd3f2bbeb745d
Reviewed-on: http://git-master/r/30015
Tested-by: Nitin Kumbhar <nkumbhar@nvidia.com>
Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com>
Reviewed-by: Erik M Lilliebjerg <elilliebjerg@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
On ventana, pca9546 is used as a mux for 0v2710/ov5650 camera
sensors. With UJA0H14 version of ov5650 sensor, it is observed
that pca9546 driver incorrectly caches last channel when VDDIO_CAM
is toggled while enabling/disabling tegra camera. Deselect i2c
mux channel on exit so that i2c mux is correctly configured with
new mux channel.
BUG 812134
(cherry picked from commit 2d62e589c0bd933db846d4b8f9fe4f2116bef8ad)
Change-Id: Id249bbeb33c370b8fc5360af33bdefecfd62a48a
Reviewed-on: http://git-master/r/29811
Tested-by: Nitin Kumbhar <nkumbhar@nvidia.com>
Reviewed-by: Pritesh Raithatha <praithatha@nvidia.com>
Reviewed-by: Erik M Lilliebjerg <elilliebjerg@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@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>
|
|
Change-Id: I6f0bc3b5859c8545853051f10bda60ab6ac3dd8b
Bug 819975
Change-Id: I19e1448b07702bebaf2889efc3a304fcd2d07df8
Reviewed-on: http://git-master/r/29467
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Change-Id: I26f58048e4bb2988a7121bf4a7738607ced88a12
Signed-off-by: Sanjay Singh Rawat <srawat@nvidia.com>
Reviewed-on: http://git-master/r/29674
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Tested-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
* add bsea engine support for encryption and decryption
* add arbitration semaphore id for bsea
Bug 803932
Change-Id: I978b06a12265acecae99dbf13607e00ae74e87f7
Signed-off-by: Sanjay Singh Rawat <srawat@nvidia.com>
Reviewed-on: http://git-master/r/29672
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Tested-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
program pwren signal of max8907c regulator to power down/up core rail on
deep sleep enter/exit deep sleep mode.
core_timer and core_off_timer changed as per K32.
separate_req set to false as whistler pmu has combined power requests.
Bug 817378
Change-Id: Ia95a61360079f919a039572cf8fd4597db9efd50
Reviewed-on: http://git-master/r/28435
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
apis added to program max8907c regulator to power down and up core supply rail
via the pwren signal on enter and exit deep sleep mode.
Bug 817378
Change-Id: I5af04db22b6c84fc4359c1a0cf209710ca144159
Reviewed-on: http://git-master/r/28434
Tested-by: Prashant Gaikwad <pgaikwad@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Conflicts:
arch/arm/mm/proc-v7.S
drivers/video/tegra/dc/dc.c
Change-Id: I40be0d615f14f1c01305388a706d257f624ba968
|
|
|
|
|
|
Resolve potential race between resume and reset
Fix wmb after return
Change-Id: I98ad1e713b9781d780bf93561496011bf62b86d1
Signed-off-by: Andrei Warkentin <andreiw@motorola.com>
|
|
Fix SSL3250A camera flash I2C errors.
Bug 778859
Change-Id: Ifaf800405bcfc080a66c500cb74fe87ca3074be9
Reviewed-on: http://git-master/r/28205
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Bug 787628
Change-Id: I73c3b8f0b3e69f1c4bc13bdaea84b19b14eb73d1
Signed-off-by: Puneet Saxena <puneets@nvidia.com>
Reviewed-on: http://git-master/r/28003
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Rabin Vincent reports:
| On SMP, this BUG() in save_stack_trace_tsk() can be easily triggered
| from user space by reading /proc/$PID/stack, where $PID is any pid but
| the current process:
|
| if (tsk != current) {
| #ifdef CONFIG_SMP
| /*
| * What guarantees do we have here that 'tsk'
| * is not running on another CPU?
| */
| BUG();
| #else
Fix this by replacing the BUG() with an entry to terminate the stack
trace, returning an empty trace - I'd rather not expose the dwarf
unwinder to a volatile stack of a running thread.
Change-Id: Ide38bb5eeff09c1d1189bc1a30667a2cc6b96ba2
Reported-by: Rabin Vincent <rabin@rab.in>
Tested-by: Rabin Vincent <rabin@rab.in>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Reviewed-on: http://git-master/r/28325
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Change-Id: I5cdfdfef8dfc9ff4796e8a9b53d9af8f41e49e65
Reviewed-on: http://git-master/r/24360
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
- configured the pinmuxes needed by the baseband.
- added board specific baseband related code.
- added caif specific platform data needed by protocol layer.
bug 785523
Change-Id: I2d1936419ccd9190d6539836cb8bca563ea07c6e
Reviewed-on: http://git-master/r/23432
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
Signed-off-by: Dmitry Shmidt <dimitrysh@google.com>
|
|
Change-Id: I903db54b76781cdb9231bb25d79635cb8f264087
|
|
To ensure an accurate read of the RTC registers during the required
multi-byte read operation, the PMU RTC is designed with the following
protection scheme
- A circuit detects a write/read and locks the RTC_COUNT4 value
by keeping the RTC in a suspended mode
- During the suspended mode, a secondary counter is used to
keep track of all counts that would have normally incremented the RTC
- After the read is complete, the value of the secondary counter is
added back to the RTC registers and thereby keeping the RTC accurate
- The backup counter allows for a 1ms RTC suspend mode duration
when the RTC prescaler is enabled.
i2c needs to generate a 2 msgs when reading.
- the address setup(write RTC_COUNT4 operation),
hence start locking the RTC_COUNT4
- the data transfer (read RTC_COUNT4 operation),release locking it.
this may allow the CPU to execute other portions of code
in between the two operation.
The fix is to start a PMU RTC access by reading the register prior to
the RTC_COUNT4 so that access of the RTC PMU registers will be guaranteed
to always occur within the 1ms time period.
- the address setup(write RTC_COUNT4-1 operation),
so there is no locking the RTC_COUNT4
- the data transfer (read RTC_COUNT4 operation),
starting locking the RTC_COUNT4 and release locking the RTC_COUNT4
in one operation, so it will be guaranteed within 1ms
Bug 811075
Change-Id: Ie07472a329f6a0eed11e6a039cd93307bb5276a0
Reviewed-on: http://git-master/r/27537
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
bug 811316
Change-Id: I4513f81719a60c8f214ee07082e58defb1cca0aa
Reviewed-on: http://git-master/r/26985
Reviewed-by: Varun Colbert <vcolbert@nvidia.com>
Tested-by: Varun Colbert <vcolbert@nvidia.com>
|
|
bug 816348
Change-Id: I6551a867fdfcddc6689d6fcc1daaee11d8879e7f
Reviewed-on: http://git-master/r/28182
Tested-by: Sumit Bhattacharya <sumitb@nvidia.com>
Reviewed-by: Ravindra Lokhande <rlokhande@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Scott Peterson <speterson@nvidia.com>
|
|
there was a cropping code which saves from out of FB.However,
the cropping code was wrong and cropping should be done from
usermode driver instead of kernel. a warning is added here
for easy debugging
Bug 792524
Change-Id: Id57243e36f903b14a093dad23a6111032890c01a
Reviewed-on: http://git-master/r/28055
Reviewed-by: Donghan Ryu <dryu@nvidia.com>
Tested-by: Donghan Ryu <dryu@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Fix SSL3250A camera flash I2C errors.
Bug 778859
Change-Id: I086eb863cce343a107f5f382d2b96eecf70d6902
Reviewed-on: http://git-master/r/28202
Reviewed-by: Erik M Lilliebjerg <elilliebjerg@nvidia.com>
Tested-by: Erik M Lilliebjerg <elilliebjerg@nvidia.com>
Reviewed-by: Prayas Mohanty <pmohanty@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Bug 803932
Change-Id: Idfafba37e71e80bce1b70a7324daf5e8df2a9e0d
Signed-off-by: Sanjay Singh Rawat <srawat@nvidia.com>
Reviewed-on: http://git-master/r/28174
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Bug 803932
Change-Id: I52703d6281bf613d7ccf67c38daf6412ac790c74
Signed-off-by: Sanjay Singh Rawat <srawat@nvidia.com>
Reviewed-on: http://git-master/r/28173
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Tested-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Bug 803932
Change-Id: I61cf41423d08d2f2c19f314269be9e8ee6255b9b
Signed-off-by: Sanjay Singh Rawat <srawat@nvidia.com>
Reviewed-on: http://git-master/r/28172
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
Removes the Sidetone enable code, sidetone should
not be enabled for normal capture.
For Bug: 808731
Change-Id: I7159c023624c9d3f759cf52510e8a48551454db1
Reviewed-on: http://git-master/r/28013
Tested-by: Manjula Gupta <magupta@nvidia.com>
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
|
|
PPP handles packet loss but does not work with out of order packets.
This change performs reordering of incoming data packets within a
sliding window of one second. Since sequence number is optional,
receiving a packet without it will drop all queued packets.
Currently the logic is triggered by incoming packets, so queued
packets have to wait till another packet is arrived. It is done for
simplicity since no additional locks or threads are required. For
reliable protocols, a retransmission will kick it. For unreliable
protocols, queued packets just seem like packet loss. Time-critical
protocols might be broken, but they never work with queueing anyway.
Signed-off-by: Chia-chi Yeh <chiachi@android.com>
|