linux-toradex.git, branch imx-android-r13.3

ENGR00210728 testMultiCameraRelease failed in CameraTest

2012-05-24T09:48:14+00:00

Two camera instance will be opened at the same time, and
only one will be kept stream on. The previous camera's close
will stream off the second camera's dequeue function.

Signed-off-by: guoyin.chen

ENGR00179851: i.mx6dl: map the MEM mode to STANDBY mode

2012-05-24T01:38:11+00:00

Due to i.mx6dl TO1.0(TKT094231), Suspend/resume cannot work
stable under deep sleep mode(Dormant, MEM MODE) thus we need
map the MEM mode to STANBY mode(ARM will not power off), this
issue will be fixed on TO1.1

Signed-off-by: Jason Liu

nohz: Remove "Switched to NOHz mode" debugging messages

2012-05-24T01:19:04+00:00

When performing cpu hotplug tests the kernel printk log buffer gets flooded
with pointless "Switched to NOHz mode..." messages. Especially when afterwards
analyzing a dump this might have removed more interesting stuff out of the
buffer.
Assuming that switching to NOHz mode simply works just remove the printk.

Signed-off-by: Heiko Carstens 
Link: http://lkml.kernel.org/r/20110823112046.GB2540@osiris.boeblingen.de.ibm.com
Signed-off-by: Thomas Gleixner

ENGR00180495 [mx6]Fix suspend/resume issue caused by hotplug

2012-05-24T01:19:03+00:00

When we kill a secondary cpu, we need to wait for it
die, then kill it from hardware setting. And to avoid
the cache unalign issue, we use hardware register to
send flag to inform main cpu to kill secondary cpu.

Signed-off-by: Anson Huang

ARM: 7359/2: smp_twd: Only wait for reprogramming on active cpus

2012-05-24T01:19:02+00:00

During booting of cpu1, there is a short window where cpu1
is online, but not active where cpu1 is occupied by waiting
to become active. If cpu0 then decides to schedule something
on cpu1 and wait for it to complete, before cpu0 has set
cpu1 active, we have a deadlock.

Typically it's this CPU frequency transition that happens at
this time, so let's just not wait for it to happen, it will
happen whenever the CPU eventually comes online instead.

Cc: Peter Zijlstra 
Cc: stable@kernel.org
Signed-off-by: Jonas Aaberg 
Reviewed-by: Rickard Andersson 
Signed-off-by: Linus Walleij 
Signed-off-by: Russell King

ARM: 7406/1: hotplug: copy the affinity mask when forcefully migrating IRQs

2012-05-24T01:19:02+00:00

When a CPU is hotplugged off, we migrate any IRQs currently affine to it
away and onto another online CPU by calling the irq_set_affinity
function of the relevant interrupt controller chip. This function
returns either IRQ_SET_MASK_OK or IRQ_SET_MASK_OK_NOCOPY, to indicate
whether irq_data.affinity was updated.

If we are forcefully migrating an interrupt (because the affinity mask
no longer identifies any online CPUs) then we should update the IRQ
affinity mask to reflect the new CPU set. Failure to do so can
potentially leave /proc/irq/n/smp_affinity identifying only offline
CPUs, which may confuse userspace IRQ balancing daemons.

This patch updates migrate_one_irq to copy the affinity mask when
the interrupt chip returns IRQ_SET_MASK_OK after forcefully changing the
affinity of an interrupt.

Cc: stable@vger.kernel.org
Reported-by: Leif Lindholm 
Signed-off-by: Will Deacon 
Signed-off-by: Russell King

ARM: 7317/1: irq: avoid NULL check in for_each_irq_desc loop

2012-05-24T01:19:01+00:00

ARM unconditionally selects CONFIG_GENERIC_HARDIRQS, so the definition
of for_each_irq_desc will check that the desc is non-NULL anyway.

This patch removes a redundant check from the IRQ migration code.

Signed-off-by: Will Deacon 
Signed-off-by: Russell King

ARM: CPU hotplug: ensure we migrate all IRQs off a downed CPU

2012-05-24T01:19:00+00:00

Our selection of interrupts to consider for IRQ migration is sub-
standard.  We were potentially including per-CPU interrupts in our
migration strategy, but omitting chained interrupts.  This caused
some interrupts to remain on a downed CPU.

We were also trying to migrate interrupts which were not migratable,
resulting in an OOPS.

Instead, iterate over all interrupts, skipping per-CPU interrupts
or interrupts whose affinity does not include the downed CPU, and
attempt to set the affinity for every one else if their chip
implements irq_set_affinity().

Signed-off-by: Russell King

ARM: CPU hotplug: pass in proper affinity mask on IRQ migration

2012-05-24T01:18:59+00:00

Now that the GIC takes care of selecting a target interrupt from the
affinity mask, we don't need all this complexity in the core code
anymore.  Just detect when we need to break affinity.

Signed-off-by: Russell King

ARM: CPU hotplug: fix abuse of irqdesc->node

2012-05-24T01:18:59+00:00

irqdesc's node member is supposed to mark the numa node number for the
interrupt.  Our use of it is non-standard.  Remove this, replacing the
functionality with a test of the affinity mask.

Signed-off-by: Russell King