KuldeepX Vyas [Wed, 6 Jun 2012 13:07:52 +0000 (18:37 +0530)]
[WORKAROUND]audio: SW support to swap mic bias1 & bias2
BZ: 39873
Lex PR1.1 and PR2.1 have their AMIC bias lines are swapped.
Codec and Machine driver needs to handle the difference
between these two boards using SPID.
During driver initialization drivers reads SPID and based on
board, appropriate audio map is initialized. In machine driver,
use appropriate AMIC Bias to handle headset button presses.
This patch should be reverted once Lex PR1.1 is EOLed.
Change-Id: I11c35644419e2d6b683cbb0e130c3bac51f4dfe9
Signed-off-by: KuldeepX Vyas <kuldeepx.vyas@intel.com>
Signed-off-by: Ramesh Babu K V <ramesh.babu@intel.com>
Reviewed-on: http://android.intel.com:8080/53652
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Tested-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Illyas Mansoor [Mon, 18 Jun 2012 17:58:51 +0000 (23:28 +0530)]
intel_mdf_battery: move .suspend/.resume to .prepare/.complete
BZ: 42523
Medfield battery driver stops and starts the charger health monitoring
workqueue, this issues a lot of IPC commands and interferes with D0ix
transitions that are happening during system suspend/resume, causing
SCU contention and in rare cases d0ix transition timeouts.
Fixing this by moving the .suspend/.resume callbacks to .prepare/.complete
Added a delay during scheduling the workqueue in complete().
Change-Id: Iab4ce37e12bc1f3c3b4b530692bfe129fa64bb8f
Signed-off-by: Illyas Mansoor <illyas.mansoor@intel.com>
Reviewed-on: http://android.intel.com:8080/53244
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Hogander, Jouni <jouni.hogander@intel.com>
Reviewed-by: Jena, TapanX <tapanx.jena@intel.com>
Reviewed-by: Pallala, Ramakrishna <ramakrishna.pallala@intel.com>
Tested-by: Kallappa Manjanna, MadhukumarX <madhukumarx.kallappa.manjanna@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ramakrishna Pallala [Fri, 22 Jun 2012 11:14:50 +0000 (16:44 +0530)]
MFD/Battery: Fix battery status setting logic for interrupt case
BZ: 38168
Right we are setting the battery status to Not Chargring upon certain
interrutps without properly(really) checking the charger fault condition.
This patch will fix this issue by making sure that we check charger
fault case AND interrupt bits.
Change-Id: Ia41c5820dd616ca295a0421f8c3894828a173892
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/53736
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Reviewed-by: Mukherjee, DevapriyaX <devapriyax.mukherjee@intel.com>
Reviewed-by: Jena, TapanX <tapanx.jena@intel.com>
Tested-by: Kallappa Manjanna, MadhukumarX <madhukumarx.kallappa.manjanna@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Wu, Hao [Wed, 20 Jun 2012 11:09:37 +0000 (19:09 +0800)]
usb/penwell_otg: set charging current limitation to 100mA by default for SDP case
BZ: 38168
This is in order to workaround one issue in low battery level case,
set charging current to 100mA once SDP is detected. Late setting
may cause system shutdown due to low power state.
Change-Id: I829e3283b32a858b446e7287e72179e65825516b
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/53444
Reviewed-by: Mukherjee, DevapriyaX <devapriyax.mukherjee@intel.com>
Reviewed-by: Pallala, Ramakrishna <ramakrishna.pallala@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Jena, TapanX <tapanx.jena@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Kallappa Manjanna, MadhukumarX <madhukumarx.kallappa.manjanna@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Shankar D K [Thu, 21 Jun 2012 15:32:41 +0000 (21:02 +0530)]
audio:add missing mutex protection to _dapm_sync call
BZ: 42423
There can be race condition if _dapm_sync() is not called without
holding codec mutex. It can lead to kernel crash.
This patch adds mutex locks before invoking _dapm_sync().
The _dapm_sync() needs to be called explicitely
only when driver uses _force_enable_pin() or _disable_pin().
Removed a reduntant _dapm_sync() call in codec driver, where
neither a enable or disable pin is used.
Change-Id: I6a81572993805d3a8c1ea3dde00274638d2a0a97
Signed-off-by: Shankar D K <shankar.d.kodandaram@intel.com>
Signed-off-by: Ramesh Babu K V <ramesh.babu@intel.com>
Reviewed-on: http://android.intel.com:8080/53642
Reviewed-by: R, Dharageswari <dharageswari.r@intel.com>
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Tested-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Daisuke Nishimura [Thu, 15 Dec 2011 05:37:41 +0000 (14:37 +0900)]
[PORT FROM R4]sched: Fix cgroup movement of waking process
BZ: 42195
(backport of upstream commit
62af3783e4f, merged in v3.3-rc1)
There is a small race between try_to_wake_up() and sched_move_task(),
which is trying to move the process being woken up.
try_to_wake_up() on CPU0 sched_move_task() on CPU1
--------------------------------+---------------------------------
raw_spin_lock_irqsave(p->pi_lock)
task_waking_fair()
->p.se.vruntime -= cfs_rq->min_vruntime
ttwu_queue()
->send reschedule IPI to CPU1
raw_spin_unlock_irqsave(p->pi_lock)
task_rq_lock()
-> tring to aquire both p->pi_lock and
rq->lock with IRQ disabled
task_move_group_fair()
-> p.se.vruntime
-= (old)cfs_rq->min_vruntime
+= (new)cfs_rq->min_vruntime
task_rq_unlock()
(via IPI)
sched_ttwu_pending()
raw_spin_lock(rq->lock)
ttwu_do_activate()
...
enqueue_entity()
child.se->vruntime += cfs_rq->min_vruntime
raw_spin_unlock(rq->lock)
As a result, vruntime of the process becomes far bigger than min_vruntime,
if (new)cfs_rq->min_vruntime >> (old)cfs_rq->min_vruntime.
This patch fixes this problem by just ignoring such process in
task_move_group_fair(), because the vruntime has already been normalized in
task_waking_fair().
Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Tejun Heo <tj@kernel.org>
Link: http://lkml.kernel.org/r/20111215143741.df82dd50.nishimura@mxp.nes.nec.co.jp
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Orig-Change-Id: I5eabfb717750908a7045a35d8c10a1fcf7706052
Signed-off-by: German Monroy <german.monroy@intel.com>
Conflicts:
kernel/sched_fair.c
Change-Id: I2b32a77e3958f4b83ad99b3e74b898439b1e9da7
Reviewed-on: http://android.intel.com:8080/54413
Reviewed-by: Monroy, German <german.monroy@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Paul Turner [Wed, 6 Jul 2011 02:07:21 +0000 (19:07 -0700)]
[PORT FROM R4]sched: update correct entity's runtime in check_preempt_wakeup()
BZ: 42195
(backport of upstream commit
9bbd7374361d, merged in v3.1-rc1)
While looking at check_preempt_wakeup() I realized that we are
potentially updating the wrong entity in the fair-group scheduling
case. In this case the current task's cfs_rq may not be the same as
the one used for the comparison between the waking task and the
existing task's vruntime.
This potentially results in us using a stale vruntime in the
pre-emption decision, providing a small false preference for the
previous task. The effects of this are bounded since we always
perform a hierarchal update on the tick.
Signed-off-by: Paul Turner <pjt@google.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/CAPM31R+2Ke2urUZKao5W92_LupdR4AYEv-EZWiJ3tG=tEes2cw@mail.gmail.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Change-Id: I32e6c3be9339bbd1f0435365f3b048dcba8c35d1
Orig-Change-Id: I6d728362a5cc654ba0f92ab0043a4011925a4444
Signed-off-by: German Monroy <german.monroy@intel.com>
Reviewed-on: http://android.intel.com:8080/54412
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Mike Galbraith [Tue, 22 Nov 2011 14:21:26 +0000 (15:21 +0100)]
[PORT FROM R4]sched: Set skip_clock_update in yield_task_fair()
BZ: 42195
(backport of upstream commit
916671c08, merged in v3.3-rc1)
This is another case where we are on our way to schedule(),
so can save a useless clock update and resulting microscopic
vruntime update.
Signed-off-by: Mike Galbraith <efault@gmx.de>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/1321971686.6855.18.camel@marge.simson.net
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Change-Id: I55962c20a65857f52566c1970cb02e27f82845a8
Orig-Change-Id: I9e0b31ea4008cb0ed84b1dd3739c401856fdac4d
Signed-off-by: German Monroy <german.monroy@intel.com>
Reviewed-on: http://android.intel.com:8080/54410
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Daisuke Nishimura [Thu, 15 Dec 2011 05:36:07 +0000 (14:36 +0900)]
[PORT FROM R4]sched: Fix cgroup movement of newly created process
BZ: 42195
(backport of upstream commit
7ceff013, merged in 3.3-rc1)
There is a small race between do_fork() and sched_move_task(), which is
trying to move the child.
do_fork() sched_move_task()
--------------------------------+---------------------------------
copy_process()
sched_fork()
task_fork_fair()
-> vruntime of the child is initialized
based on that of the parent.
-> we can see the child in "tasks" file now.
task_rq_lock()
task_move_group_fair()
-> child.se.vruntime
-= (old)cfs_rq->min_vruntime
+= (new)cfs_rq->min_vruntime
task_rq_unlock()
wake_up_new_task()
...
enqueue_entity()
child.se.vruntime += cfs_rq->min_vruntime
As a result, vruntime of the child becomes far bigger than min_vruntime,
if (new)cfs_rq->min_vruntime >> (old)cfs_rq->min_vruntime.
This patch fixes this problem by just ignoring such process in
task_move_group_fair(), because the vruntime has already been normalized in
task_fork_fair().
Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Tejun Heo <tj@kernel.org>
Link: http://lkml.kernel.org/r/20111215143607.2ee12c5d.nishimura@mxp.nes.nec.co.jp
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Change-Id: I43b700487d934ede48fa95fe9942176d740c24f1
Orig-Change-Id: I2c9db9352e9ce33a62880192f798687280bd02ad
Signed-off-by: German Monroy <german.monroy@intel.com>
Reviewed-on: http://android.intel.com:8080/54408
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Daisuke Nishimura [Thu, 15 Dec 2011 05:36:55 +0000 (14:36 +0900)]
[PORT FROM R4]sched: Fix cgroup movement of forking process
BZ: 42195
(backport of upstream commit
4fc420c91, merged in v3.3-rc1)
There is a small race between task_fork_fair() and sched_move_task(),
which is trying to move the parent.
task_fork_fair() sched_move_task()
--------------------------------+---------------------------------
cfs_rq = task_cfs_rq(current)
-> cfs_rq is the "old" one.
curr = cfs_rq->curr
-> curr is set to the parent.
task_rq_lock()
dequeue_task()
->parent.se.vruntime -= (old)cfs_rq->min_vruntime
enqueue_task()
->parent.se.vruntime += (new)cfs_rq->min_vruntime
task_rq_unlock()
raw_spin_lock_irqsave(rq->lock)
se->vruntime = curr->vruntime
-> vruntime of the child is set to that of the parent
which has already been updated by sched_move_task().
se->vruntime -= (old)cfs_rq->min_vruntime.
raw_spin_unlock_irqrestore(rq->lock)
As a result, vruntime of the child becomes far bigger than expected,
if (new)cfs_rq->min_vruntime >> (old)cfs_rq->min_vruntime.
This patch fixes this problem by setting "cfs_rq" and "curr" after
holding the rq->lock.
Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Acked-by: Paul Turner <pjt@google.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Tejun Heo <tj@kernel.org>
Link: http://lkml.kernel.org/r/20111215143655.662676b0.nishimura@mxp.nes.nec.co.jp
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Change-Id: I5fdea6d67116199553e0b608603e237e4e995946
Orig-Change-Id: I1ee474f2b786b962bbdf6409c7690abcea88bd2c
Signed-off-by: German Monroy <german.monroy@intel.com>
Reviewed-on: http://android.intel.com:8080/54404
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Sathyanarayanan Kuppuswamy [Fri, 22 Jun 2012 20:31:07 +0000 (13:31 -0700)]
Add SPID reference in MSIC_AUDIO & SN95031 platform data
BZ: 41996
Audio driver needs to differentiate between HW versions of
board during runtime. If there are any difference between
boards, Audio driver will take decision based on SPID.
This patch adds that support.
Change-Id: If02f33110c6d0a20cf631666e7fb92692c2019c7
Signed-off-by: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-on: http://android.intel.com:8080/54045
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Fri, 22 Jun 2012 18:20:01 +0000 (11:20 -0700)]
BT:BACKPORT: Issue fixed in upstream
BZ: 43211
Bluetooth: rfcomm: Fix sleep in invalid context in rfcomm_security_cfm
This was triggered by turning off encryption on ACL link when rfcomm
was using high security. rfcomm_security_cfm (which is called from rx
task) was closing DLC and this involves sending disconnect message
(and locking socket).
Move closing DLC to rfcomm_process_dlcs and only flag DLC for closure
in rfcomm_security_cfm.
BUG: sleeping function called from invalid context at net/core/sock.c:2032
in_atomic(): 1, irqs_disabled(): 0, pid: 1788, name: kworker/0:3
[<
c0068a08>] (unwind_backtrace+0x0/0x108) from [<
c05e25dc>] (dump_stack+0x20/0x24)
[<
c05e25dc>] (dump_stack+0x20/0x24) from [<
c0087ba8>] (__might_sleep+0x110/0x12c)
[<
c0087ba8>] (__might_sleep+0x110/0x12c) from [<
c04801d8>] (lock_sock_nested+0x2c/0x64)
[<
c04801d8>] (lock_sock_nested+0x2c/0x64) from [<
c05670c8>] (l2cap_sock_sendmsg+0x58/0xcc)
[<
c05670c8>] (l2cap_sock_sendmsg+0x58/0xcc) from [<
c047cf6c>] (sock_sendmsg+0xb0/0xd0)
[<
c047cf6c>] (sock_sendmsg+0xb0/0xd0) from [<
c047cfc8>] (kernel_sendmsg+0x3c/0x44)
[<
c047cfc8>] (kernel_sendmsg+0x3c/0x44) from [<
c056b0e8>] (rfcomm_send_frame+0x50/0x58)
[<
c056b0e8>] (rfcomm_send_frame+0x50/0x58) from [<
c056b168>] (rfcomm_send_disc+0x78/0x80)
[<
c056b168>] (rfcomm_send_disc+0x78/0x80) from [<
c056b9f4>] (__rfcomm_dlc_close+0x2d0/0x2fc)
[<
c056b9f4>] (__rfcomm_dlc_close+0x2d0/0x2fc) from [<
c056bbac>] (rfcomm_security_cfm+0x140/0x1e0)
[<
c056bbac>] (rfcomm_security_cfm+0x140/0x1e0) from [<
c0555ec0>] (hci_event_packet+0x1ce8/0x4d84)
[<
c0555ec0>] (hci_event_packet+0x1ce8/0x4d84) from [<
c0550380>] (hci_rx_task+0x1d0/0x2d0)
[<
c0550380>] (hci_rx_task+0x1d0/0x2d0) from [<
c009ee04>] (tasklet_action+0x138/0x1e4)
[<
c009ee04>] (tasklet_action+0x138/0x1e4) from [<
c009f21c>] (__do_softirq+0xcc/0x274)
[<
c009f21c>] (__do_softirq+0xcc/0x274) from [<
c009f6c0>] (do_softirq+0x60/0x6c)
[<
c009f6c0>] (do_softirq+0x60/0x6c) from [<
c009f794>] (local_bh_enable_ip+0xc8/0xd4)
[<
c009f794>] (local_bh_enable_ip+0xc8/0xd4) from [<
c05e5804>] (_raw_spin_unlock_bh+0x48/0x4c)
[<
c05e5804>] (_raw_spin_unlock_bh+0x48/0x4c) from [<
c040d470>] (data_from_chip+0xf4/0xaec)
[<
c040d470>] (data_from_chip+0xf4/0xaec) from [<
c04136c0>] (send_skb_to_core+0x40/0x178)
[<
c04136c0>] (send_skb_to_core+0x40/0x178) from [<
c04139f4>] (cg2900_hu_receive+0x15c/0x2d0)
[<
c04139f4>] (cg2900_hu_receive+0x15c/0x2d0) from [<
c0414cb8>] (hci_uart_tty_receive+0x74/0xa0)
[<
c0414cb8>] (hci_uart_tty_receive+0x74/0xa0) from [<
c02cbd9c>] (flush_to_ldisc+0x188/0x198)
[<
c02cbd9c>] (flush_to_ldisc+0x188/0x198) from [<
c00b2774>] (process_one_work+0x144/0x4b8)
[<
c00b2774>] (process_one_work+0x144/0x4b8) from [<
c00b2e8c>] (worker_thread+0x198/0x468)
[<
c00b2e8c>] (worker_thread+0x198/0x468) from [<
c00b9bc8>] (kthread+0x98/0xa0)
[<
c00b9bc8>] (kthread+0x98/0xa0) from [<
c0061744>] (kernel_thread_exit+0x0/0x8)
Change-Id: I1736d4d81ee5c5f89f17b42d66cafd0e57f7c471
Signed-off-by: Szymon Janc <szymon.janc@tieto.com>
Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
Reviewed-on: http://android.intel.com:8080/53836
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Reviewed-by: Kuppuswamy, Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jianxu Zheng [Tue, 19 Jun 2012 05:19:39 +0000 (13:19 +0800)]
atomisp: add spinlock to solve race condition
BZ: 34525
issue: kernel panicking and system hang when doing MTBF
root cause:
In failed case, atomisp_isr() is running on CPU0,
atomisp_acc_load() is on another CPU1 (hyper-thread / dual-core).
Atomisp_acc_load() sets my_css.invalidate between
sh_css_preview_next_stage_needs_alloc(), and atomisp_start_binary().
It causes kernel panicing when CSS API sh_css_preview_start()
tries to free memory. Because the memory (de)allocation
might trigger a sleep operation and it's in the ISR of ISP.
solution:
added a spinlock to protect the CSS flag my_css.invalidate in
sh_css_load_acceleration(), meanwhile the memory allocation for
header->sp_arg in sh_css_load_acc() should be moved out of the
path spinlock protection. Moved it into the function
sh_css_acc_set_argument() which is the first place to use
the variable header->sp_arg.
For digital zoom/xnr, also add spinlock/mutex to protect
the CSS flag my_css.invalidate.
Change-Id: Icec8b3d2e1b513290fcbabcd19210710a962ecb8
Signed-off-by: Jianxu Zheng <jian.xu.zheng@intel.com>
Reviewed-on: http://android.intel.com:8080/53298
Reviewed-by: Augusteijn, Lex <lex.augusteijn@intel.com>
Reviewed-by: Govindapillai, Vinod <vinod.govindapillai@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Tuominen, TeemuX <teemux.tuominen@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Tue, 19 Jun 2012 08:33:11 +0000 (16:33 +0800)]
mmc: host: use spinlock to lock across the acquire ownership
BZ: 42752
use spin lock to across the acquiring ownership to protect IA threads
compete
Change-Id: I1492b5fad0d309efb812adab37fa45744adccb52
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/53370
Reviewed-by: Zhang, Yanmin <yanmin.zhang@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Yoshio Wada [Wed, 13 Jun 2012 05:56:09 +0000 (07:56 +0200)]
atomisp: [mt9e013]set frame_valid flag in work queue call back.
BZ: 41629
root cause:
gain control was designed below;
First: control the filter at SOF via work queue.
Next: respond the gain setup request via ioctl from user space.
However work queue service delayed when cpu is heavily-loaded.
This situation happens at 1080 recording.
The work queue call back delayed 12 msec from enqueued at worst.
In this case, control order is broken like below;
First: respond the gain setup request.
Second: control the filter.
In the result, gain is setupped twice during one frame.
solution:
set frame_valid flag in the work queue call back instead receipt SOF signal.
then the gain setup request is suspended when work queue service delayed.
Change-Id: I4827b589591e010cb4fbefb3cbf8700f1224e5ec
Signed-off-by: Yoshio Wada <yoshio.wada@intel.com>
Reviewed-on: http://android.intel.com:8080/52711
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Kantola, Lasse <lasse.kantola@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Lei Zhang [Mon, 4 Jun 2012 01:41:27 +0000 (09:41 +0800)]
GFX-Display: Added Post2 support for frame buffer flipping.
BZ: 33412
This is 1/3 patches to solve Bug 33412.
Since post() path only supports update display plane surface in
kernel driver, we cannot configure other display plane settings
dynamically from user space.
This patch eanbled frame buffer flipping in Post2() path, and it
enhanced kernel driver to be able to re-config all display plane
registers, so that HWC can adjust display plane configs such as
plane format, z order dynamically.
This patch also increased the number of buffer of display class
so that we can multiple buffers to kernel driver in one flip cmd.
Change-Id: Id9b6bfcd0c59a2fbcb6338dc20dbbfd219ce5e9a
Signed-off-by: Jackie Li <yaodong.li@intel.com>
Signed-off-by: Lei Zhang <lei.zhang@intel.com>
Reviewed-on: http://android.intel.com:8080/51149
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Robert Jarzmik [Fri, 11 May 2012 15:31:49 +0000 (17:31 +0200)]
drivers/misc: ipanic should have a module parameter to specify dump partition
BZ: 42097
Previously, dump partition was always number 6 (ie. mmcblk0p6). This
prevents repartitioning and reordering on futur boards.
This patch keeps 6 as the default, but makes the number configurable
as a module param :
- with kernel commandline emmc_ipanic.ipanic_part_number=3 for mmcblk0p3
Change-Id: I600b08fd22d781f6175039479df000a4cb7eae72
Signed-off-by: Robert Jarzmik <robert.jarzmik@intel.com>
Reviewed-on: http://android.intel.com:8080/52962
Reviewed-by: Puech, Yann <yann.puech@intel.com>
Tested-by: Romieu, Benoit <benoit.romieu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Zhi Jin [Thu, 21 Jun 2012 05:41:40 +0000 (13:41 +0800)]
atomisp: set the digital zoom in atomisp_set_fmt()
BZ: 43056
Zoom must be recalculated by calling atomisp_digital_zoom()
when switching resolution.
Originally from: Zhi Jin <zhi.jin@intel.com>
Change-Id: Idbf5568965cb1ff20e0b255f269b627b4afbc2b3
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/53557
Reviewed-by: Kontola, Kalervo <kalervo.kontola@intel.com>
Reviewed-by: Tuominen, TeemuX <teemux.tuominen@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jouni Hogander [Sun, 10 Jun 2012 08:49:56 +0000 (11:49 +0300)]
GFX: Use sleep instead of delay when restoring registers
BZ: 41131
mdfld_restore_display_registers is unnecessarily using mdelay and
udelay instead of usleep_range. mdfld_restore_display_registers is
never called from context were sleep is not allowed. Fix this by
changing mdelays and udelays to usleep_range.
Change-Id: I50e93eebadfcacbe0736719b36659a73cf7cf9b4
Signed-off-by: Jouni Hogander <jouni.hogander@intel.com>
Reviewed-on: http://android.intel.com:8080/52409
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Geng Xiujun [Wed, 23 May 2012 01:14:50 +0000 (09:14 +0800)]
Gfx-Display: optimizate hdmi detection and mode setting
BZ: 38339
This patch has following changes:
1. revert commit
a315838f5d0be90e0f0abaf6b0f3683d9dc3b96f, as it's unused
currently.
2. using pointer rather than memcpy and memset.
3. trun off some log print.
4. optime mode setting path.
Change-Id: Ice1e9f916828b2446e0b6f2cf5a74402e08a909f
Signed-off-by: Geng Xiujun <xiujun.geng@intel.com>
Reviewed-on: http://android.intel.com:8080/53134
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ke Ai [Fri, 15 Jun 2012 11:19:14 +0000 (19:19 +0800)]
GFX-Display: fix mistake in /proc/display_status.
BZ: 42140
system will hange ,when using /proc/display_status.
it is related to buf overflow ,which been not protected well.
one example:
echo "a b000 b100">/proc/display_status
cat /proc/display_status
Change-Id: I4695e6b8a9a31faaee6e437bbd0ae3e5d5b7900f
Signed-off-by: Ke Ai <ke.ai@intel.com>
Reviewed-on: http://android.intel.com:8080/53129
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jason Hu [Wed, 13 Jun 2012 07:54:55 +0000 (15:54 +0800)]
GFX-Display: detach overlay rw ioctrl, gtt map/umap ioctrl from drm global lock.
BZ: 38361
1. Gtt map/unmap ioctrl don't need hold drm global lock. There is already a mm lock
for protecting gtt mm resource.
2. overlay wait vblank function should not block on mode_config lock, that will cause
actual wait time exceed a vblank period.
3. Add a mutex to protect overlay rw ioctrl instead of drm global lock. Because this
ioctrl is only used by overlay, it is not necessary to lock other display registers.
Change-Id: Ic9f98fb5bcb28925740133a4fb0c0aa3679b25ac
Signed-off-by: Jason Hu <jason.hu@intel.com>
Reviewed-on: http://android.intel.com:8080/52606
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Li Zeng [Fri, 8 Jun 2012 12:31:16 +0000 (20:31 +0800)]
drm/ttm: reset user pages to WB if modified by ttm
BZ: 37816
Set user pages to UC/WC to improve vec performance, need to reset user pages to WB when release TTM buffer object
Change-Id: I110c3dfd1a77d2a60f3d1b0be43563f8c033c7c4
Signed-off-by: Li Zeng <li.zeng@intel.com>
Reviewed-on: http://android.intel.com:8080/52473
Reviewed-by: Ding, Haitao <haitao.ding@intel.com>
Tested-by: Ding, Haitao <haitao.ding@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Tue, 19 Jun 2012 22:38:44 +0000 (15:38 -0700)]
SPID: update kernel to match SPID spec v1.02
BZ: 42727
Also remove the OEMB table revision check as IA firmware supports
SPID for all hardware now.
Change-Id: I88c428db23765b662cd6ea933e9ab760daecb0ce
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/53655
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Raffaele Aquilone [Fri, 15 Jun 2012 10:08:25 +0000 (12:08 +0200)]
Bluetooth: hidp device creation error handled
BZ: 27942
The problems consists in sysfs_create_dir() missing a safety check on the
parent_sd value that sometimes is null. This, in turn, should never happen and
it depends on some structural problems in the HIDP core: this patch is not going
to fix all of them. What it does is just moving the device creation before
the session creation and handling the hid_add_device() failure accordingly.
Change-Id: I2ba7b11b8ded3e323d15180926ccb099deb26212
Signed-off-by: Raffaele Aquilone <raffaelex.aquilone@intel.com>
Reviewed-on: http://android.intel.com:8080/52900
Reviewed-by: Bransiec, ChristopheX <christophex.bransiec@intel.com>
Reviewed-by: Gros, JulienX <julienx.gros@intel.com>
Reviewed-by: Beldie, OvidiuX <ovidiux.beldie@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Champciaux, Nicolas <nicolas.champciaux@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Christophe Lebouc [Wed, 13 Jun 2012 10:34:46 +0000 (12:34 +0200)]
Revert "[REVERTME] Improve check of validity of Fabric Log Buffer"
BZ: 40861
Revert commit
0ad40d01c3abf8fc05d71d8fed4d87a745f4b761
Change-Id: I183fc72791f913404831aea44a456c04e58ce1cb
Signed-off-by: Christophe Lebouc <christophe.lebouc@intel.com>
Reviewed-on: http://android.intel.com:8080/52625
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
yifei.xue [Tue, 19 Jun 2012 09:24:40 +0000 (17:24 +0800)]
Graphics: fix the widi regression
BZ: 42474
WiDi's MIPI turn off operation cause the LEX's screen can't turn back on.
Command mode's dpms path doesn't works well cause the issue. This patch is
wa. Will improve the dpms path to fix the issue later.
Change-Id: I4f28a83999958f7b7d848d687a033bb4426f5134
Signed-off-by: yifei.xue <yifeix.xue@intel.com>
Reviewed-on: http://android.intel.com:8080/53283
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jouni Hogander [Tue, 19 Jun 2012 11:03:21 +0000 (14:03 +0300)]
init/calibrate: Fix bug in calibrate_delay
BZ: 41942
There is a bug in calibrate_delay which causes delay calibration to be
performed on nonboot cpus when waking up from S3. This has huge impact on
screen resume latency. Fix this by correcting errorneous else if statement.
Change-Id: I57d0bd83f44d58ed8abe5e8aab7b34b00de04e2f
Signed-off-by: Jouni Hogander <jouni.hogander@intel.com>
Reviewed-on: http://android.intel.com:8080/53297
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Dong Yang [Tue, 19 Jun 2012 05:20:29 +0000 (13:20 +0800)]
IPC: add delay if read mip failed
BZ: 42495
The read_mip() function uses a dead loop to access mip, if read
mip access failed, this is not reasonable, since SCU will access
the emmc, and get the emmc mutex, if get mutex failed, SCU will
return and this function will read error return status and
trigger the IPC again. This will bring up the SCU interrupt storm,
about 800 times/second, and impact the other IPC. So we add a
delay in this loop, or IPC will continue until IA release the
emmc mutex.
Change-Id: I022fd46e04530b31d5118f91f3b1404b3ab85d0d
Signed-off-by: Dong Yang <dong.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/53241
Reviewed-by: Zhang, Shijie <shijie.zhang@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: He, Bo <bo.he@intel.com>
Tested-by: Tang, HaifengX <haifengx.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Mark Allyn [Tue, 19 Jun 2012 21:14:59 +0000 (14:14 -0700)]
drivers: staging: sep: Acquire IMR base from register for secure dma
BZ: 42711
Bug: 42711
Change-Id: Ie92b58c9f508453582a53c3ee838b57fb5dc476f
Signed-off-by: Mark Allyn <mark.a.allyn@intel.com>
Reviewed-on: http://android.intel.com:8080/53365
Reviewed-by: Mangalampalli, Jayant <jayant.mangalampalli@intel.com>
Tested-by: Mangalampalli, Jayant <jayant.mangalampalli@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Chuanxiao Dong [Mon, 18 Jun 2012 02:07:37 +0000 (10:07 +0800)]
mmc: panic_ops: release Dekker mutex during ipanic saving
BZ: 42244
panic_ops: release Dekker mutex during ipanic saving
Change-Id: I675e033887244714cc8d6e720e1ce195cc76dd86
Signed-off-by: Chuanxiao Dong <chuanxiao.dong@intel.com>
Reviewed-on: http://android.intel.com:8080/53044
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Berthier, Emmanuel <emmanuel.berthier@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Lebouc, Christophe <christophe.lebouc@intel.com>
Tested-by: Lebouc, Christophe <christophe.lebouc@intel.com>
Tested-by: Sun, Jianhua <jianhua.sun@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Leo Yan [Fri, 15 Jun 2012 09:58:48 +0000 (17:58 +0800)]
ltr301als: Change the adc-lux conversion method
BZ: 39399 41574
The adc-lux conversion is not accurate on the DV20, change the
algorithm and coefficent according to the vendor's advice.
Change-Id: I5a6e11c86c8553cd40732c9cf300421a69ac440b
Signed-off-by: Leo Yan <leo.yan@intel.com>
Reviewed-on: http://android.intel.com:8080/52892
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Chen, Jie D <jie.d.chen@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Tang, HaifengX <haifengx.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Geng Xiujun [Mon, 11 Jun 2012 08:24:31 +0000 (16:24 +0800)]
Gfx-Display: [REVERTME] improve the SW workaround 47423
BZ: 41053
The patch move WA 47423 from pci_fixup callback to i2c driver context. Once
there's a device using I2C bus 2, then try to turn on vadd, after finishing
transfer, try to turn off vadd. The turn off vadd operation is put in a delay
work queue, it will be delayed 100ms. once there's no device accessing this i2c
bus, then vadd will be turned off, otherwise the work will be canceled. This can
reduce time consumption if there're constant bus accessing.
another change is after turn on vadd, change wait time from 260ms to 60ms per
CMI panel spec, and before enabling GPIO_BL, wait another 200ms. this can save
200ms if there's i2c accessing before panel on.
Change-Id: I5d9e9e919506da606283e9e26b4cd9ce327bb736
Signed-off-by: Geng Xiujun <xiujun.geng@intel.com>
Reviewed-on: http://android.intel.com:8080/52721
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Christophe Guerard [Mon, 18 Jun 2012 13:16:29 +0000 (15:16 +0200)]
[CRASHLOG] Reformat fabric err logs
BZ: 42166
The display format of the hex value of each Dword is changed
to show all bytes of the Dword for cosmetic
Change-Id: I8c02ddde240d68b0514222415f97eb3c585b4cba
Signed-off-by: Christophe Guerard <christophe.guerard@intel.com>
Reviewed-on: http://android.intel.com:8080/53124
Reviewed-by: Hogander, Jouni <jouni.hogander@intel.com>
Reviewed-by: Kanigeri, Hari K <hari.k.kanigeri@intel.com>
Reviewed-by: Lebouc, Christophe <christophe.lebouc@intel.com>
Tested-by: Lebouc, Christophe <christophe.lebouc@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Robert Jong-A-Lock [Wed, 13 Jun 2012 07:08:32 +0000 (09:08 +0200)]
[PORT FROM R4] mt9e013: add 480p+ 20% dvs envelope resolution
BZ: 41002
For ICS a 480p sensor setting that also includes a 20% FoV needs to be added.
The sensor will then select this resolution instead of the two different ones
it was selecting before.
Change-Id: I28ec2ad8fee0266684173d72bb4b4983f76508b0
Orig-Change-Id: Ic19b0a6118edf4aec284f04c3f11ee4ee3eca5b8
Signed-off-by: Robert Jong-A-Lock <robert.jong-a-lock@intel.com>
Reviewed-on: http://android.intel.com:8080/52856
Reviewed-by: Niemimuukko, Ukri <ukri.niemimuukko@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Mon, 18 Jun 2012 08:59:36 +0000 (11:59 +0300)]
mt9m114: implement VIDIOC_S/G_PARM for setting/getting stream parameters
BZ: 41720
Implement VIDIOC_G_PARM and VIDIOC_S_PARM to set and get struct
v4l2_streamparm.
Change-Id: I18eef26ced26b6bb871d737c0e47e28b7fe61fdb
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/53085
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Mon, 18 Jun 2012 08:08:14 +0000 (11:08 +0300)]
atomisp: return framerate for VIDIOC_G_PARM ioctl call
BZ: 41720
VIDIOC_G_PARM should return the video frame rate, so call the
sensor driver to get the frame rate and return it.
Change-Id: Icbe636971934facfa11bf4732e0d4230c23e2789
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/53070
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Fri, 15 Jun 2012 07:48:17 +0000 (10:48 +0300)]
mt9e013: add a full FOV mode for 1080p
BZ: 41720
Add sensor mode with full field-of-view (FOV) and resolution
1640x956 @ 30 fps for Blackbay. This mode can be used for creating
1080p mode by using ISP upscaling.
Also add an option to specifically enable sensor modes which have
less than full FOV. Enable low FOV modes for Blackbay but leave
disabled for Enzo and Lexington.
Change-Id: Ib8d0743bcad62b1d275266add4c3a1a398941ef5
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/52874
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Thu, 14 Jun 2012 14:28:47 +0000 (17:28 +0300)]
atomisp: disable digital video stabilization when upscaling
BZ: 41720
Disable digital image stabilization (DVS) when ISP is doing
upscaling.
Change-Id: I6fc84d79476a534c6eabff04b9cccd92e0155d39
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/52800
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Wang, Wen W <wen.w.wang@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Thu, 14 Jun 2012 14:24:54 +0000 (17:24 +0300)]
atomisp: calculate zoom factor properly when upscaling
BZ: 41720
ISP zoom must be properly configured when upscaling is enabled.
Calculate the zoom limits and scale the user provided zoom
factor into proper range.
Change-Id: I755e0a87da6da56523208bde7d5051cbac6778eb
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/52799
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Wed, 13 Jun 2012 11:39:52 +0000 (14:39 +0300)]
ov8830: implement VIDIOC_G_PARM for getting stream parameters
BZ: 41720
Implement function to return struct v4l2_streamparm and call this
function from VIDIOC_S_PARM handler to fill the returned
structure. Also clear sensor mode parameters when streaming mode
is set. The sensor mode should be selected after the streaming mode
has been set.
Change-Id: I8fcac0925db91a9a691f5cb126e9fc992827bf2b
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/52730
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Cohen, David A <david.a.cohen@intel.com>
Reviewed-by: Kontola, Kalervo <kalervo.kontola@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Wed, 13 Jun 2012 08:17:01 +0000 (11:17 +0300)]
atomisp: enable upscaling on ISP
BZ: 41720
If the requested resolution is bigger than what the sensor supports,
use ISP upscaler to construct image of desired size instead of
returning a smaller resolution to user space.
Change-Id: Ie7b9e55fbe28b38b976851008f03537456501d26
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/52729
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Wed, 13 Jun 2012 07:36:24 +0000 (10:36 +0300)]
mt9e013: implement VIDIOC_G_PARM for getting stream parameters
BZ: 41720
Implement function to return struct v4l2_streamparm and call this
function from VIDIOC_S_PARM handler to fill the returned
structure. Also clear sensor mode parameters when streaming mode
is set. The sensor mode should be selected after the streaming mode
has been set.
Change-Id: I040510ce6b767695a1425e76388da4f57c8801d3
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/52728
Reviewed-by: Niemimuukko, Ukri <ukri.niemimuukko@intel.com>
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Kontola, Kalervo <kalervo.kontola@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tuukka Toivonen [Wed, 6 Jun 2012 07:48:27 +0000 (10:48 +0300)]
atomisp: clear struct v4l2_streamparm which is passed to sensor driver
BZ: 41720
AtomISP driver calls s_parm function of sensor drivers and gives
as an argument struct v4l2_streamparm without clearing it. This
causes random parameters to be passed on to drivers causing
possibly random effects.
Change-Id: Id04321ccbebf2ccaa30cdc5debfa1d3396330369
Signed-off-by: Tuukka Toivonen <tuukka.toivonen@intel.com>
Reviewed-on: http://android.intel.com:8080/52727
Reviewed-by: Niemimuukko, Ukri <ukri.niemimuukko@intel.com>
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Emmanuel Berthier [Tue, 12 Jun 2012 11:07:22 +0000 (13:07 +0200)]
atomisp: Wrong cache page alignment
BZ: 41025
After enabling SLUB allocator debugging (cf BZ 39652), we get strange warning
logs:
KERNEL : [ 51.307896] WARNING: at hardware/intel/linux-2.6/arch/x86/mm/pageattr.c:877 change_page_attr_set_clr+0x273/0x420()
It appears that ISP pages are not aligned to kernel pages (0x400 instead of
0x1000).
Signed-off-by: Emmanuel Berthier <emmanuel.berthier@intel.com>
Change-Id: I57e0f747f45640bcaf3b83bd798bcb31e68a6d31
Reviewed-on: http://android.intel.com:8080/52491
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Bin Yang [Wed, 13 Jun 2012 03:18:24 +0000 (11:18 +0800)]
ignore xmitr checking while port is inactive
BZ: 41591
when hsu is inactive, all hsu accesses will be put into a queue.
It is not necessary to check the xmitr.
Change-Id: Ief9268da85c7f5d7fcb6e309658acc93e6e454cf
Signed-off-by: Bin Yang <bin.yang@intel.com>
Signed-off-by: Wang Yiyang <yiyang.wang@intel.com>
Reviewed-on: http://android.intel.com:8080/52844
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Tang, HaifengX <haifengx.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Yun Tu(Mark Tu) [Sat, 16 Jun 2012 06:55:29 +0000 (14:55 +0800)]
[GFX-3D]Release last flip buffer after a while even if there is no new frame coming
BZ:42074
Release last flip buffer after a while even if there is no new frame coming,
as looks like user space try to lock last frame without submitting a new frame first
and cause dead lock then
Signed-off-by: Yun Tu(Mark Tu) <yun.tu@intel.com>
Change-Id: Ifa76783985418cd2011546c01169c996baf25901
Reviewed-on: http://android.intel.com:8080/52876
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jzhuan5 [Thu, 14 Jun 2012 22:24:49 +0000 (18:24 -0400)]
usb:otg: wait for system resume before stopping host
BZ: 38545
add a PM notifier to know whether system is resumed.
EHCI driver should not be removed until system is resumed.
Change-Id: I012d1130215f08bd4230af8adf4068d8cb588c0b
Signed-off-by: jzhuan5 <jin.can.zhuang@intel.com>
Reviewed-on: http://android.intel.com:8080/52758
Reviewed-by: Wu, Hao <hao.wu@intel.com>
Reviewed-by: Tang, Jianqiang <jianqiang.tang@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: Gao, Yunpeng <yunpeng.gao@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Hong Liu [Mon, 18 Jun 2012 08:36:56 +0000 (16:36 +0800)]
max11871: add 06-17 driver drop from maxim
BZ: 42240
Maxim new release (intel-2012-06-17), including new firmware + driver to
support LEX PR2.0.
Change-Id: I35e0a8b4445ec8b0bf6bbada0395d7a496def1f3
Signed-off-by: Hong Liu <hong.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/53080
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Wang, Zhifeng <zhifeng.wang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
ShuoX Liu [Mon, 21 May 2012 01:36:30 +0000 (09:36 +0800)]
[PORT FROM R2][REVERTME] cpu: trigger a BUG() when boot cpu1 failed when being woke up from S3.
BZ: 36367
From yanmin:
It's hard to reproduce this issue and we don't know where CPU 1 is
running when it happens. A potential patch is to call BUG() to trigger
a panic when CPU 0 couldn't boot CPU 1, so system would reboot by
software WDT and wouldn't consume power unconsciously.
Change-Id: I32624a6875b435655dc0fe7e3f647dbbeb6d793a
Orig-Change-Id: I700068ab629cf60061ac24315733aeedb5710b86
Signed-off-by: Yanmin Zhang <yanmin.zhang@intel.com>
Signed-off-by: ShuoX Liu <shuox.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/52325
Reviewed-by: Popescu, CatalinX <catalinx.popescu@intel.com>
Reviewed-by: Hogander, Jouni <jouni.hogander@intel.com>
Reviewed-by: Mansoor, Illyas <illyas.mansoor@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
liu chuansheng [Thu, 14 Jun 2012 11:31:05 +0000 (19:31 +0800)]
GFX: config the right active power latency to 50ms
BZ: 38510
Now the GFX SYS_SGX_ACTIVE_POWER_LATENCY_MS is 5, which should
effect the system load and reduce the performance.
After refer some other manufacturing config, 50 -- 100 is the
reasonable value.
Change-Id: Ie77a0a6b9344586feb28eb2a31057e12ec1428e6
Signed-off-by: liu chuansheng <chuansheng.liu@intel.com>
Reviewed-on: http://android.intel.com:8080/52709
Reviewed-by: Shi, Yang A <yang.a.shi@intel.com>
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
gwang23 [Mon, 28 May 2012 10:20:21 +0000 (18:20 +0800)]
Graphics: Update graphics kernel driver to DDK 905891
BZ: 38713
Update graphics kernel driver to DDK 905891
Change-Id: Icfb4db392c2699369a32fd1446bf31135a38dba9
Signed-off-by: Tong, Bo <box.tong@intel.com>
Reviewed-on: http://android.intel.com:8080/52593
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Randy Xu [Sat, 9 Jun 2012 03:25:01 +0000 (11:25 +0800)]
[PVR/GFX]: Enable one IMG option to avoid SGX lock up
BZ: 37183
Per IMG's suggestion, enable kernel driver option to avoid SGX lock up
SUPPORT_DC_CMDCOMPLETE_WHEN_NO_LONGER_DISPLAYED := 1
More, Mark solves the tearing issue introduced by this option
Change-Id: I280ece6cfaa09e97e24dae8b4a92058ad27ba17b
Signed-off-by: Randy Xu <randy.xu@intel.com>
Signed-off-by: Tong, Bo <box.tong@intel.com>
Reviewed-on: http://android.intel.com:8080/52258
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Li, Ning [Wed, 13 Jun 2012 08:02:55 +0000 (16:02 +0800)]
fw_update: fix buffer overflow issue
BZ: 41666
Klocwork scan found a "Buffer Overflow in Bound String Copy" issue
in intel_scu_fw_update.c. This patch fix this issue.
Change-Id: Id328f616f079b42553ffc6cf1d50be3422880f9d
Signed-off-by: Li, Ning <ning.li@intel.com>
Reviewed-on: http://android.intel.com:8080/52601
Reviewed-by: Yang, Bin <bin.yang@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Tang, HaifengX <haifengx.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ramesh Babu K V [Mon, 11 Jun 2012 16:44:12 +0000 (22:14 +0530)]
audio:use single block DMA transfer for firmware download
BZ: 35751
Fabric error has been noticed when we use LLI DMA along with single
block transfer. LLI and single block DMAs works good independently.
Fabric error have been experienced when switching from single block
DMA to LLI DMA.
Added single block DMA transfer support for downloading firmware.
Change-Id: I5df836fea163612a56e2edf2d5d8a9ff89b8111c
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Ramesh Babu K V <ramesh.babu@intel.com>
Reviewed-on: http://android.intel.com:8080/52368
Reviewed-by: R, Dharageswari <dharageswari.r@intel.com>
Reviewed-by: Vinnakota, Lakshmi N <lakshmi.n.vinnakota@intel.com>
Reviewed-by: Agarwal, Vaibhav <vaibhav.agarwal@intel.com>
Reviewed-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: Hibare, PramodX <pramodx.hibare@intel.com>
Tested-by: Hibare, PramodX <pramodx.hibare@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jli127 [Tue, 12 Jun 2012 11:45:35 +0000 (19:45 +0800)]
Revert "atmel_mxt_ts: Change the touch calibration condition"
BZ: 40848
This reverts commit
e1a5b9cfefe16f7de8024562f7c988b1db7e4272.
The patch reverted here sometime causing touch screen stop
responding when device comes from suspend.
The patch reverted skips touch screen calibration progress
if fingers are detected on touch sreen when device comes
from suspend, this may cause touch screen stop responding.
Change-Id: I9d509bbc41dacf3ec71f948f12cc4ebe057c94d0
Signed-off-by: jli127 <jian.d.li@intel.com>
Reviewed-on: http://android.intel.com:8080/52495
Reviewed-by: Liu, Hong <hong.liu@intel.com>
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Yan, Leo <leo.yan@intel.com>
Tested-by: Tang, HaifengX <haifengx.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Aymen Zayet [Fri, 16 Mar 2012 14:01:30 +0000 (15:01 +0100)]
ST: Adding Runtime PM and S3 support for the shared transport release
BZ: 24772
This patch provides the implementation of PM runtime corresponding to
the new release of the shared transport layer :
- All the newly added callbacks for the KIM driver have been defined.
- The previous implementation of PM runtime get/put have been moved
to the new callbacks .chip_asleep() and .chip_awake() for more
consistency.
- Add more check to avoid S3 while the device is in ST_LL_AWAKE state.
Change-Id: I0aa6aceb5b6c692584e224dee03f9fadbb8dcfdb
Signed-off-by: Aymen Zayet <aymenx.zayet@intel.com>
Reviewed-on: http://android.intel.com:8080/51770
Reviewed-by: Champciaux, Nicolas <nicolas.champciaux@intel.com>
Tested-by: Champciaux, Nicolas <nicolas.champciaux@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Emmanuel Berthier [Tue, 12 Jun 2012 11:19:11 +0000 (13:19 +0200)]
Kernel config: Enable SLUB allocator debugging
BZ: 39652
In order to be able to debug kernel memory corruptions (generating Paging
request BUGs), it could be useful to activate SLUB allocator debugging
features.
Signed-off-by: Emmanuel Berthier <emmanuel.berthier@intel.com>
Change-Id: I1687bae9cb750a1856c4b4d8646b495f8315a317
Reviewed-on: http://android.intel.com:8080/52492
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
yifei.xue [Fri, 8 Jun 2012 03:08:14 +0000 (11:08 +0800)]
[Graphics]: Enable the LEX command mode DSTB,CABC, fix the tearing issue
BZ: 40910
Enable the LEX command mode DSTB support, add dynamic interface to
control CABC(enable the CABC default).
Disable CABC: echo 0 > /sys/module/gfx/parameters/psb_enable_lex_cabc
The root cause of commad mode tearing is DC writing the panel internal mem with direction
bottom to top while the panel scan the internal mem with direction top to bottom.
Change-Id: Ieae5298cad716a04e4a028dbf1d1e09e3325c350
Signed-off-by: yifei.xue <yifeix.xue@intel.com>
Reviewed-on: http://android.intel.com:8080/52416
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
yifei.xue [Tue, 29 May 2012 08:31:47 +0000 (16:31 +0800)]
Graphics: Lex display command mode support
BZ: 32664
Enable the LEX display command mode
Change-Id: I17545d9af9e769383dbe26a4d74e412a4a278bba
Signed-off-by: yifei.xue <yifeix.xue@intel.com>
Signed-off-by: Ke Ai <ke.ai@intel.com>
Signed-off-by: Tong, Bo <box.tong@intel.com>
Reviewed-on: http://android.intel.com:8080/52423
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Lingyun Zhu [Wed, 6 Jun 2012 02:05:28 +0000 (10:05 +0800)]
GFX-Display: Fix Out Of Memory issue when playing video while rotating the device with suspend and resume
BZ: 39131
Add definitaion of SUPPORT_LARGE_GENERAL_HEAP in kernel/driver/staging/mrst/medfield/Makefile
to enlarge the GeneralHeap in gpu, and ensure there is enough video memory for video playing
while rotate the screen with suspend and resume.
Change-Id: If7653c1068a01f22dca77d2342555222dc0765cf
Signed-off-by: Lingyun Zhu <lingyun.zhu@intel.com>
Reviewed-on: http://android.intel.com:8080/52413
Reviewed-by: Tong, BoX <box.tong@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
zhong Dongsheng [Sun, 3 Jun 2012 22:38:38 +0000 (06:38 +0800)]
GFX-Display: refine the dsi_error_handler
BZ:35254
Update the error handling and refine the logging.
Change-Id: Ia4441a503a7357ab254bd8bb7d2feb31744e8812
Signed-off-by: zhong Dongsheng <dongsheng.zhang@intel.com>
Signed-off-by: Ke Ai <ke.ai@intel.com>
Reviewed-on: http://android.intel.com:8080/52411
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ke Ai [Fri, 1 Jun 2012 06:41:11 +0000 (14:41 +0800)]
GFX-display: Suboptimal sequence in mdfld_dsi_pr2_power_on
BZ: 38884
optimize the sequence of TURN_ON
because according spec, after TURN_ON need wait 100ms.
after exit sleep 120ms is needed.
here try to optimize the sequence to reduce the wait time
Change-Id: I0f81d52d294895e5c83672ecff436bf3de33d53a
Signed-off-by: Ke Ai <ke.ai@intel.com>
Reviewed-on: http://android.intel.com:8080/52315
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Li, Ning [Wed, 6 Jun 2012 09:47:07 +0000 (17:47 +0800)]
fw_update: fw upgrade memory handle
BZ: 40065
There are some potential issues in fw_update driver, such as haven't
set pointer to NULL after freed and not having cancel IFWI upgrade
mechanism.
Add an early_param "alloc_fota_mem_early". If it's set, the 4M fota
memory will be allocated during driver init. At the same time, the
memory allocation at binary file writing is still kept as before.
A new sysfs interface is created for user space to cancel fw update by:
echo 1 > /sys/devices/ipc/intel_fw_update.0/fw_info/cancel_update
Change-Id: I149c88c56ea77adfe004161f20167b8408d7e983
Signed-off-by: Li, Ning <ning.li@intel.com>
Reviewed-on: http://android.intel.com:8080/52573
Reviewed-by: Du, Alek <alek.du@intel.com>
Reviewed-by: Puech, Yann <yann.puech@intel.com>
Reviewed-by: Yang, Bin <bin.yang@intel.com>
Tested-by: Tang, HaifengX <haifengx.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ramakrishna Pallala [Thu, 7 Jun 2012 15:00:38 +0000 (20:30 +0530)]
max170xx_battery: add fake temperature support
BZ: 40875
This patch enables the user space to get fake battery temperature
from fuel gauge driver.This is needed for doing conformence tests
by HW teams.
Usage:
To get fake battery temperature reported:
echo 1 > enable_fake_temp
To get real battery temperature:
echo 0 > enable_fake_temp
Change-Id: Iee154da96ba9cb212cf4b52d09101429d8067520
Signed-off-by: Ramakrishna Pallala <ramakrishna.pallala@intel.com>
Reviewed-on: http://android.intel.com:8080/52023
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: Mitra, DebalinaX <debalinax.mitra@intel.com>
Reviewed-by: Jena, TapanX <tapanx.jena@intel.com>
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Tested-by: Kallappa Manjanna, MadhukumarX <madhukumarx.kallappa.manjanna@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Geng Xiujun [Fri, 8 Jun 2012 05:41:39 +0000 (13:41 +0800)]
Gfx-Display: change CABC PWM frequency to 200hz
BZ: 32836
set CABC PWM frequency to 200hz can reduce headset noise significantly.
and flicker issue is ignorable.
Change-Id: Ia4e4eeb61ef05e1c4f8163fd686326115de99143
Signed-off-by: Geng Xiujun <xiujun.geng@intel.com>
Reviewed-on: http://android.intel.com:8080/52311
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ramesh Babu K V [Mon, 4 Jun 2012 10:04:11 +0000 (15:34 +0530)]
Revert "Audio: Synchronous message posting for ALSA trigger commands"
BZ: 37713
This reverts commit
27ee72007abaf4a8fe9a3579923ad893d2f28842.
Change-Id: I957bc01caefdd48620d520a89c2b51da1f53cc7d
Signed-off-by: Ramesh Babu K V <ramesh.babu@intel.com>
Reviewed-on: http://android.intel.com:8080/52159
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: Continente, Christophe <christophe.continente@intel.com>
Reviewed-by: Hibare, PramodX <pramodx.hibare@intel.com>
Tested-by: Hibare, PramodX <pramodx.hibare@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ramesh Babu K V [Mon, 4 Jun 2012 10:03:35 +0000 (15:33 +0530)]
Revert "audio:sst: Change work queues to singlethread work queues"
BZ: 37713
This reverts commit
e669f0fd2aeb0ae5b7a524ad05e3a5c977eeb4ce.
Change-Id: I82f8f824dc639aa4a92b803f8a9947e51472e171
Signed-off-by: Ramesh Babu K V <ramesh.babu@intel.com>
Reviewed-on: http://android.intel.com:8080/52158
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: Continente, Christophe <christophe.continente@intel.com>
Reviewed-by: Hibare, PramodX <pramodx.hibare@intel.com>
Tested-by: Hibare, PramodX <pramodx.hibare@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Shreyas Neerebailoor [Fri, 8 Jun 2012 04:39:38 +0000 (10:09 +0530)]
HDMI-Audio: Fix Spinlock-Recursion and Null-Pointer issues
BZ: 21688 37320
Change to prevent Recursive spinlock in trigger.
In middle of start trigger, if HDMI is Pluged-out, the driver
state is disconnected and unplug function calls snd_pcm_stop to
inform the upper layer about disconnection. This internally calls
snd_pcm_stop and stop trigger. Here the lock is recursively
acquired. Solution is to not call snd_pcm_stop if the
substream is active.
Change to prevent Substream NULL during programming buffer.
During successive quick plug and unplug of HDMI cable,
unplug is processed before Start trigger gets to process.
But the trigger state is saved. On unplug the Stop trigger is
called and because it is disconnected it does nothing. Once
cable is plugged in silence is played and the old saved
start trigger causes to retrieve the substream which is NULL
at this point of time. Solution is to clear Trigger state during
unplug. During Plugin inform the upper layer about the event,
if the substream is still active.
HDMI Audio code ported from R2 branch contains Dummy_playback
code. This workaround is no longer needed in R3. (ICS platform)
This patch removes dummy_playback implemtation. Some variables
are renamed for better readability.
Change-Id: I36f4b655316846f8dbf7e0f8935f6a6cff707624
Signed-off-by: Shreyas Neerebailoor <shreyasx.neerebailoor@intel.com>
Reviewed-on: http://android.intel.com:8080/52079
Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com>
Reviewed-by: Agarwal, Vaibhav <vaibhav.agarwal@intel.com>
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: Hibare, PramodX <pramodx.hibare@intel.com>
Tested-by: Hibare, PramodX <pramodx.hibare@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Leo Yan [Tue, 12 Jun 2012 00:24:22 +0000 (08:24 +0800)]
[PORT FROM R4]lis3dh: Send init events to userspace when status changes
BZ: 39086
In some use case, when sensor device's status changes, such as
enable/disable, interrupt/polling mode switching. Android framework
doesn't have enough accelerometer data to set window orientation
correctly, so we need to send them manually.
Change-Id: I53ba0b15b8dcabd01dab8209de9515570e5547a5
Signed-off-by: Leo Yan <leo.yan@intel.com>
Reviewed-on: http://android.intel.com:8080/52406
Reviewed-by: Du, Alek <alek.du@intel.com>
Tested-by: Tang, HaifengX <haifengx.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Pavan Kumar S [Thu, 7 Jun 2012 09:27:29 +0000 (14:57 +0530)]
smb347_charger: Add a small delay after OTG-disable.
BZ: 39775
When OTG disabled and charging enabled, send the uevent after a
short delay, as Status Register C is not updated immediately.
Change-Id: I24160a7a5f9350aa50ca5dbad6af5b0c23a4188b
Signed-off-by: Pavan Kumar S <pavan.kumar.s@intel.com>
Reviewed-on: http://android.intel.com:8080/51924
Reviewed-by: Tc, Jenny <jenny.tc@intel.com>
Reviewed-by: Jena, TapanX <tapanx.jena@intel.com>
Tested-by: Kallappa Manjanna, MadhukumarX <madhukumarx.kallappa.manjanna@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Frode Isaksen [Mon, 4 Jun 2012 13:58:13 +0000 (15:58 +0200)]
fmradio: new delivery from T.I with bug fixes in FM driver
BZ: 39471
OMAPS00269234:
Changes in FM Driver include:( fm_drv_chr.c )
1. Initialization of the FM lock before the usage.
2.Removed call init_waitqueue_head as this is already done at fm_chr_open()
3.Memory leak fixes. Proper memory freeing for the FM SKB buffers
Change-Id: I6999a87a57bd7327b5aa90326ab9843a4c098cfe
Signed-off-by: Frode Isaksen <frodex.isaksen@intel.com>
Reviewed-on: http://android.intel.com:8080/51277
Reviewed-by: Peix, Fabien <fabien.peix@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Zurmely, PierreX <pierrex.zurmely@intel.com>
Reviewed-by: Zayet, Aymen <aymen.zayet@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Fei Yang [Fri, 18 May 2012 18:41:41 +0000 (11:41 -0700)]
VPN: Enable L2TP/IPSec mode
BZ: 37071
This patch set the following to enable VPN in L2TP/IPSec mode,
CONFIG_L2TP=y
CONFIG_NET_KEY=y
CONFIG_NET_KEY_MIGRATE=y
Change-Id: Ib00717215b646f67ce4539d1b4f8c8533ff671d6
Signed-off-by: Fei Yang <fei.yang@intel.com>
Reviewed-on: http://android.intel.com:8080/52370
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
xiaobing tu [Wed, 6 Jun 2012 06:42:01 +0000 (14:42 +0800)]
Ptrace: enable the process to read other process's stack and comm
BZ: 36161
For debug usage,For debug ANR and UIWDT issues, we need get more details from the
/d/binder, /proc/xxx/stack, proc/xxx/comm, from it we can know which
process block the binder read, and we can also get more other useful
informations, but the current ptrace implement may block it. the patch
add a debugfs interface to enable read by default.
Signed-off-by: xiaobing tu <xiaobing.tu@intel.com>
Change-Id: Ied22eaa00316ff5e3602799af5825f2afb4fa21f
Reviewed-on: http://android.intel.com:8080/51907
Reviewed-by: Zhang, LongX <longx.zhang@intel.com>
Reviewed-by: Gross, Mark <mark.gross@intel.com>
Reviewed-by: Ren, Jack <jack.ren@intel.com>
Reviewed-by: Yang, Fei <fei.yang@intel.com>
Tested-by: Ng, Cheon-woei <cheon-woei.ng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Marie-Celine Dubut [Mon, 11 Jun 2012 08:57:14 +0000 (10:57 +0200)]
Revert "hwmon: Change late resume priority to enable gfx first"
BZ: 37619
This reverts commit
2aa1c6020d920a6e77c967f7428db328c89536b5.
This reverts patch http://android.intel.com:8080/#/c/51961/
Change-Id: I361acce85160f5a761651c8710d4c8a37fc4f9fc
Signed-off-by: Marie-Celine Dubut <marie.celinex.dubut@intel.com>
Reviewed-on: http://android.intel.com:8080/52298
Vincent Pillet [Wed, 30 May 2012 12:54:03 +0000 (14:54 +0200)]
hsi_ffl_tty.c: Do not rely on TTY_THROTTLE when low_latency is set
BZ: 35524
As TTY_THROTTLE can be wrong when tty->low_latency is set (rare race condition
identified), we stop relying on this bit. No drawback, as tty_insert_flip_string_flag
will return 0.
Change-Id: Iede1babcaa076cbb450dfafca4ef5266f37210a1
Signed-off-by: Vincent Pillet <vincentx.pillet@intel.com>
Reviewed-on: http://android.intel.com:8080/51986
Reviewed-by: Predon, Frederic <frederic.predon@intel.com>
Reviewed-by: Lebsir, SamiX <samix.lebsir@intel.com>
Tested-by: Lebsir, SamiX <samix.lebsir@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Vincent Pillet [Wed, 9 May 2012 14:39:17 +0000 (16:39 +0200)]
n_gsm.c : Open gsmtty in blocking mode whitout taking count of Carrier Detect
BZ: 28988
Some modem (IMC, but other as well) do not set CD when DLCI for AT command are
opened. CLOCAL can't be used before the first open, as file descriptor is
needed (fd is given once CD is received)
We add here a new parameter to the MUX during initialization IOCTL.
Parameter name : clocal.
clocal = 1 : Force CLOCAL, ie. do not wait for Carrier Detect from modem
clocal = 0 : Wait for Carrier Detect from modem
Default value in MUX is 1.
As tty_port_block_til_ready will exit due to CLOCAL, we need also to wait UA
from modem. We have also to wait UA in gsmtty_close.
CLOCAL can be unset later as usual.
Change-Id: I01d78449dac3d21196aaa8f4f984baf8a3fb578f
Signed-off-by: Vincent Pillet <vincentx.pillet@intel.com>
Reviewed-on: http://android.intel.com:8080/51984
Reviewed-by: Predon, Frederic <frederic.predon@intel.com>
Reviewed-by: Lebsir, SamiX <samix.lebsir@intel.com>
Tested-by: Lebsir, SamiX <samix.lebsir@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Michie Yamauchi [Thu, 31 May 2012 04:31:06 +0000 (06:31 +0200)]
atomisp: CSS/FW release from Synergy baseline of 30May2012
BZ: 28761
This release of CSS/FW addresses the following issues:
- Making thresholds for rejected AWB blocks tunable
Change-Id: I8b382a28825f41f8af6665f189087e32c260ebb4
Signed-off-by: Michie Yamauchi <michie.yamauchi@intel.com>
Reviewed-on: http://android.intel.com:8080/51527
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Van Immerzeel, Ronald <ronald.van.immerzeel@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
yoshio wada [Wed, 25 Apr 2012 23:53:49 +0000 (01:53 +0200)]
atomisp: flash-light appears on the screen.
BZ: 36446
keep the timing to write the itg and gain value into mt9e013 register.
- use SOF irq
- implement the gain delay filter in the sensor driver
Solution :
- atomisp
- libcamera
- libmfldadvci
- bionic
Change-Id: Iaba0da1906af9895af2b6f9054d3601d3455c044
Signed-off-by: Yoshio Wada <yoshio.wada@intel.com>
Reviewed-on: http://android.intel.com:8080/51348
Reviewed-by: Kantola, Lasse <lasse.kantola@intel.com>
Reviewed-by: Kruger, Jozef <jozef.kruger@intel.com>
Reviewed-by: Koski, Anttu <anttu.koski@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: Koskinen, Ilkka <ilkka.koskinen@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Kai Vehmanen [Mon, 4 Jun 2012 15:46:06 +0000 (18:46 +0300)]
atomisp: fix regression in file injection support
BZ: 38404
File injection was broken in the following commit:
fd67fb1 atomisp: port css codebase to support mrfl vp
Most of the patch was affecting only CONFIG_X86_MRFLD builds, but it
contained one ifdef that significantly changed the code flow for other
platforms. This patches reverts those unintented changes.
Change-Id: I62580ab93f5f34b8a18dc3cee05382b7badcce07
Signed-off-by: Kai Vehmanen <kai.vehmanen@intel.com>
Reviewed-on: http://android.intel.com:8080/51300
Reviewed-by: Tao, Jing <jing.tao@intel.com>
Reviewed-by: Laakso, Antti <antti.laakso@intel.com>
Reviewed-by: Toivonen, Tuukka <tuukka.toivonen@intel.com>
Tested-by: Koski, Anttu <anttu.koski@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Geng Xiujun [Fri, 1 Jun 2012 05:23:23 +0000 (13:23 +0800)]
Gfx-Display: fix kernel panic when setting csc
BZ: 34537
operator precedence is misused.
Change-Id: Ifbfacc4ec108533b85f133b47b662e82a581a04e
Signed-off-by: Geng Xiujun <xiujun.geng@intel.com>
Reviewed-on: http://android.intel.com:8080/51963
Reviewed-by: Tong, BoX <box.tong@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: Ai, Ke <ke.ai@intel.com>
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Jackie Li [Tue, 8 May 2012 02:40:51 +0000 (10:40 +0800)]
GFX-Display: resolved the flashing issue when booting up SC1.
BZ: 32042
Fixed by:
1. Not doing mode setting, DPMS operation and suspending/resuming before driver
loadling completes, as IFWI turns on the MIPI panel when launching system;
2. Replacing mdfld_dsi_dbi_update_power() with mdfld_auo_dsi_dbi_set_power(),
to avoid potential incorrect DCS command sequence.
3. Making DBI panel update_fb() work when the frame buffer device is used to
update screen in droidboot mode.
4. Also fixed the droidboot displaying nothing issue caused by patch #47785,
by sending "write_mem_start" DSI command in TE interrupt handler in droidboot
mode where there isn't page flip request.
This issue is from Enzo BZ #570.
Change-Id: I9c52ef7e4e28ec6504be67843121293fbc2a6cd8
Signed-off-by: Jackie Li <yaodong.li@intel.com>
Signed-off-by: Austin Hu <austin.hu@intel.com>
Signed-off-by: Ke Ai <ke.ai@intel.com>
Reviewed-on: http://android.intel.com:8080/51962
Reviewed-by: Tong, BoX <box.tong@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
John Mathew [Mon, 21 May 2012 14:43:51 +0000 (17:43 +0300)]
hwmon: Change late resume priority to enable gfx first
BZ: 37619
This patch is intended for BZ: 33446. Currently during a
system wide late resume call the hwmon late resume calls
are called before gfx_display late resume call. This patch
changes the order to enable gfx_diplay late resume calls
to be called before the hwmon late resume calls.
Change-Id: I8991998dc447b5940c85d3427fcb5aa43934adb5
Signed-off-by: John Mathew <john.mathew@intel.com>
Reviewed-on: http://android.intel.com:8080/51961
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Ke Ai [Fri, 1 Jun 2012 06:27:13 +0000 (14:27 +0800)]
GFX_display: optimize panel reset time
BZ: 37475
contracted with panel vender,
After panel reset and before sending IC setting,
wait for 7ms is ok.
Change-Id: Idc3a4261f8288e2436a26c43d24562619ce515cd
Signed-off-by: Ke Ai <ke.ai@intel.com>
Reviewed-on: http://android.intel.com:8080/51960
Reviewed-by: Tong, BoX <box.tong@intel.com>
Tested-by: Tong, BoX <box.tong@intel.com>
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jianqian [Tue, 5 Jun 2012 06:23:50 +0000 (14:23 +0800)]
usb/host:Enter runtime_suspend without 500ms delay when otg state == A_HOST
|| otg state == A_WAIT_B_CON
BZ: 36969
Enter runtime_suspend without delay in runtime_idle to prevent port change happens
during 500ms delay.
If during 500ms delay, devices like mouse connect to port, this event can not process
for driver also enter runtime suspend.
Change to submit to R3-Stable.
Change-Id: I5286c0b69ca667a4a40052a273e014bfc3ad2fcb
Signed-off-by: jianqian <jianqiang.tang@intel.com>
Reviewed-on: http://android.intel.com:8080/51382
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jianqian [Tue, 5 Jun 2012 05:38:58 +0000 (13:38 +0800)]
usb/host : Add time-out wakelock to let usb finish work before system suspend
or after system resume.
BZ: 34381
[PATCH 3/3]
Add time-out wakelock in ehci-hcd.c and hub.c to let usb finish work before system suspend.
After enable D0i3/D3 for host, usb host do not hold any wakelock when
doing usb work, this will cause usb cannot finish enumeration and
releated work such as report uevent to upper layer to turn on screen
before system enter suspend.
Note: When system entering S3, this patch may not work for system may not
trigger any wakelock of this patch.
Change-Id: Ied432d1da40215589f7aeb644f3a3272aa60d506
Signed-off-by: jianqian <jianqiang.tang@intel.com>
Reviewed-on: http://android.intel.com:8080/51380
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jianqian [Tue, 5 Jun 2012 05:30:06 +0000 (13:30 +0800)]
usb/host : Add time-out wakelock data structure to usb_hcd and intel_mid_otg_xceiv.
Also do init and distory for this wakelock.
BZ: 34381
[PATCH 2/3]
Add time-out wakelock data structure to usb_hcd and intel_mid_otg_xceiv.
Also do init and distory for this wakelock.
Change-Id: Ifc24d16d83a25aaff4c0e0ad8d20af34dfaaf69c
Signed-off-by: jianqian <jianqiang.tang@intel.com>
Reviewed-on: http://android.intel.com:8080/51379
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
jianqian [Tue, 5 Jun 2012 05:19:12 +0000 (13:19 +0800)]
usb/host : Disable persist_enable feature for there is risk for mistake.
BZ: 34381
[PATCH 1/3]
Disable persist_enable feature for there is risk for mistake
and can not turn on screen.
Change-Id: I6ac51eb4e67b6ebc7698682a46c2a29111ca0846
Signed-off-by: jianqian <jianqiang.tang@intel.com>
Reviewed-on: http://android.intel.com:8080/51378
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Christophe Lebouc [Thu, 7 Jun 2012 14:59:18 +0000 (16:59 +0200)]
[REVERTME] Improve check of validity of Fabric Log Buffer
BZ: 40861
Improve check of validity of Fabric Log Buffer
Change-Id: Ia1c605d4a14e58dd3f3c8769dff4a350589a59af
Signed-off-by: Christophe Lebouc <christophe.lebouc@intel.com>
Reviewed-on: http://android.intel.com:8080/52010
Reviewed-by: Guerard, Christophe <christophe.guerard@intel.com>
Reviewed-by: Leveque, Olivier <olivier.leveque@intel.com>
Reviewed-by: Onkalo, Samu <samu.onkalo@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Shreyas Neerebailoor [Fri, 18 May 2012 03:27:35 +0000 (08:57 +0530)]
HDMI-Audio: Prevent Suspend if the substream is alive
BZ: 36456 36536
In cases of short and repeated sound clips like alarm,
the Stop-Start Triggers may be called in between.
On HDMI, if in between Stop and Start trigger, suspend
is requested, the device would move to suspend.
To prevent this suspend when the clip is still playing,
additional check for a valid substream is added.
Change-Id: I93ce38d8e27bfbe53568f94114d00b053243bec8
Signed-off-by: Shreyas Neerebailoor <shreyasx.neerebailoor@intel.com>
Reviewed-on: http://android.intel.com:8080/51410
Reviewed-by: Babu, Ramesh <ramesh.babu@intel.com>
Reviewed-by: Koul, Vinod <vinod.koul@intel.com>
Reviewed-by: Gupta, ArvindX K <arvindx.k.gupta@intel.com>
Reviewed-by: Hibare, PramodX <pramodx.hibare@intel.com>
Tested-by: Hibare, PramodX <pramodx.hibare@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
yifei.xue [Tue, 29 May 2012 08:31:47 +0000 (16:31 +0800)]
Revert "Graphics: Lex display command mode support"
BZ: 32664
This reverts commit
6a844894383789ecfdd760c8e617e21f212dbab4.
Change-Id: I790ddcca5db5994a1c1cb44aa210fdd1dca4f314
Signed-off-by: Erwan Mahe <erwan.mahe@intel.com>
Reviewed-on: http://android.intel.com:8080/52034
Prachita Talathi [Mon, 28 May 2012 10:39:05 +0000 (16:09 +0530)]
sfi-cpufreq : Modifying residency_count_multiplier according to maximum operating frequency supported by the platform
BZ: 38418
P-state driver calculates the CPU load value based upon the C-state(C2 to C6)
residencies in the given time interval. Since MSRs record the residency with 1MHz clock,
to compute the actual residency at maximum speed, the value should be multiplied by
a factor = (maximum clock / 1M ).
This patch makes the calculation of this multiplier generic by taking the maximum
frequency from the frequency table as the multiplier value.
Change-Id: I5f6e37cd3ad9e488c04c9926ddb8e9314ccb8947
Signed-off-by: Illyas Mansoor <illyas.mansoor@intel.com>
Signed-off-by: Prachita Talathi <prachita.j.talathi@intel.com>
Reviewed-on: http://android.intel.com:8080/51412
Reviewed-by: Martin, LoicX <loicx.martin@intel.com>
Tested-by: Martin, LoicX <loicx.martin@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Mathieu Soulard [Tue, 5 Jun 2012 11:53:52 +0000 (13:53 +0200)]
[PORT FROM R2][Audio] Noise during phone call on Lenovo Medfield design
BZ: 38506
Audience recommends to assert the reset line 1ms minimum.
This patch increase the reset assert last from 100us to 1100us.
If the reset line is not asserted long enough, es305b internal
PLL initialization may fail. In such case noise is observed
during phone call.
Change-Id: I1c079ce8716bfae4260a30ec0c3be21322237e26
Signed-off-by: Mathieu Soulard <mathieu.soulard@intel.com>
Reviewed-on: http://android.intel.com:8080/51508
Reviewed-by: Centelles, Sylvain <sylvain.centelles@intel.com>
Tested-by: Mendi, EduardoX <eduardox.mendi@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
David Castelain [Fri, 11 May 2012 17:25:22 +0000 (19:25 +0200)]
API for setting and reading UMIP OEM Factory flag
BZ: 35509
API creation for setting and reading UMIP OEM Factory flag in intel_mid_umip.
Change-Id: Ie316a74e99517947c59449bd55c4af29db8f63d5
Signed-off-by: David Castelain <davidx.castelain@intel.com>
Reviewed-on: http://android.intel.com:8080/51533
Reviewed-by: Sahukar, Surya P <surya.p.sahukar@intel.com>
Tested-by: Afantenos, Marie CecileX <marie.cecilex.afantenos@intel.com>
Reviewed-by: Romieu, Benoit <benoit.romieu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Tong, Bo [Wed, 6 Jun 2012 13:13:29 +0000 (21:13 +0800)]
Gfx-Display: check hdmi state in display runtime suspend
BZ: 37468
This is the patch to correct the logic of patch 49533 in which it will
block display goes into D0i3. By adding hdmi_state check to determine
if it need to check hdmi audio suspend status.
Change-Id: I6ae9a768f4c1d795b2fd7e17c4c2624646d9ce66
Signed-off-by: Tong, Bo <box.tong@intel.com>
Reviewed-on: http://android.intel.com:8080/51779
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: Zhang, Lei <lei.zhang@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Zhouzhou(Scott) Fang [Tue, 5 Jun 2012 14:09:25 +0000 (22:09 +0800)]
[GFX-DISPLAY] Disable psb frame buffer driver ops to avoid intel logo disappear.
BZ: 38396
There is a black screen interval between firmware logo and Android
system logo, the logo drawn by firmware will be cleared intentionly
by kernel console layer, it is not what we want. Since frame buffer
operation won't be needed in Andriod system, disable driver layer's ops.
Change-Id: I0e80d3600b9f0ffad5ba4fe43501e7d1c9863aac
Signed-off-by: Zhouzhou(Scott) Fang <zhouzhou.fang@intel.com>
Reviewed-on: http://android.intel.com:8080/51709
Reviewed-by: Xu, Randy <randy.xu@intel.com>
Tested-by: Xu, Randy <randy.xu@intel.com>
Reviewed-by: Tu, Yun <yun.tu@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Wu, Hao [Mon, 4 Jun 2012 13:45:00 +0000 (21:45 +0800)]
usb/penwell_otg: add related notification for vbus invalid case
BZ: 39874
Add vbus invalid notification from usb driver, for overcurrent
condition for USB host mode.
Change-Id: I413aa37bf87384b30a918d3facf9ae8b402acdff
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/51550
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Tang, Jianqiang <jianqiang.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Wu, Hao [Mon, 4 Jun 2012 11:20:22 +0000 (19:20 +0800)]
usb/penwell_otg_test: use usb warning code instead of error code
BZ: 39874
Use usb warning code will be more readable than just error code.
Change-Id: I6345a8a676beb45280926b595dce386ff68ddd57
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/51549
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Tang, Jianqiang <jianqiang.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Wu, Hao [Mon, 4 Jun 2012 11:19:40 +0000 (19:19 +0800)]
usb/core: switch to usb warning code
BZ: 39874
Use warning code will be more readable.
Change-Id: I8edbe195223bef323f6f1f4799e0c1dd8f656583
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/51548
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Tang, Jianqiang <jianqiang.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
Wu, Hao [Mon, 4 Jun 2012 11:17:39 +0000 (19:17 +0800)]
usb/core: add warning code for notifcation
BZ: 39874
Use warning code will be more readable than just error code.
Also add one more warning code for VBUS INVALID case.
Change-Id: I4f5343f6c25c134233c240ecf81652c1ab0d7294
Signed-off-by: Wu, Hao <hao.wu@intel.com>
Reviewed-on: http://android.intel.com:8080/51547
Reviewed-by: Tang, Richard <richard.tang@intel.com>
Reviewed-by: Tang, Jianqiang <jianqiang.tang@intel.com>
Reviewed-by: Meng, Zhe <zhe.meng@intel.com>
Tested-by: Meng, Zhe <zhe.meng@intel.com>
Reviewed-by: buildbot <buildbot@intel.com>
Tested-by: buildbot <buildbot@intel.com>
projects / kernel / kernel-mfld-blackbay.git / log