| Age | Commit message (Collapse) | Author |
|---|
|
Issues reported in commit aed6c4fe5 have now been fixed.
Signed-off-by: Anthony Felice <tony.felice@timesys.com>
|
|
Signed-off-by: Anthony Felice <tony.felice@timesys.com>
|
|
The gic_enable_ppi() function is used with the global timer when resuming
from STOP mode on the Vybrid Tower. With the __cpuinit attribute set, the
gic_enable_ppi() function would have already been freed once the kernel
finishes loading, causing a kernel oops when attempting to resume from STOP mode.
Signed-off-by: Anthony Felice <tony.felice@timesys.com>
|
|
|
|
EDMA enabled in the UART configuration prevents ADC from working in MQX 4.0.2.
We also disable EDMA with UART in other Vybrid variants due to an
incompatibility with sysvinit.
|
|
|
|
- change PHY TX/RX parameters accoording to Richard's email
- Disable OTG descripor
- Add Freescale VID/PID
Signed-off-by: Peter Chen <peter.chen@freescale.com>
|
|
|
|
Fixes issue reported in ticket #52637
|
|
|
|
|
|
|
|
This is the same defconfig that Timesys Factory uses.
|
|
This patch was submitted by Roshni Shah <roshni.shah@timesys.com>
for ticket #52067
|
|
This patch was submitted by Yoshihisa Ozawa <ozawa@lineo.co.jp> in
ticket #52306.
|
|
to occur when using USB1.
|
|
L2 cache is not present.
Author: Roshni Shah <roshni.shah@timesys.com>
|
|
semaphore without requesting it
|
|
|
|
|
|
cleanup debug comment / code in i2c-imx
|
|
|
|
Commit 455bd4c430b0 ("ARM: 7668/1: fix memset-related crashes caused by
recent GCC (4.7.2) optimizations") attempted to fix a compliance issue
with the memset return value. However the memset itself became broken
by that patch for misaligned pointers.
This fixes the above by branching over the entry code from the
misaligned fixup code to avoid reloading the original pointer.
Also, because the function entry alignment is wrong in the Thumb mode
compilation, that fixup code is moved to the end.
While at it, the entry instructions are slightly reworked to help dual
issue pipelines.
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Tested-by: Alexander Holler <holler@ahsoftware.de>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
(cherry picked from commit 418df63adac56841ef6b0f1fcf435bc64d4ed177)
|
|
optimizations
Recent GCC versions (e.g. GCC-4.7.2) perform optimizations based on
assumptions about the implementation of memset and similar functions.
The current ARM optimized memset code does not return the value of
its first argument, as is usually expected from standard implementations.
For instance in the following function:
void debug_mutex_lock_common(struct mutex *lock, struct mutex_waiter *waiter)
{
memset(waiter, MUTEX_DEBUG_INIT, sizeof(*waiter));
waiter->magic = waiter;
INIT_LIST_HEAD(&waiter->list);
}
compiled as:
800554d0 <debug_mutex_lock_common>:
800554d0: e92d4008 push {r3, lr}
800554d4: e1a00001 mov r0, r1
800554d8: e3a02010 mov r2, #16 ; 0x10
800554dc: e3a01011 mov r1, #17 ; 0x11
800554e0: eb04426e bl 80165ea0 <memset>
800554e4: e1a03000 mov r3, r0
800554e8: e583000c str r0, [r3, #12]
800554ec: e5830000 str r0, [r3]
800554f0: e5830004 str r0, [r3, #4]
800554f4: e8bd8008 pop {r3, pc}
GCC assumes memset returns the value of pointer 'waiter' in register r0; causing
register/memory corruptions.
This patch fixes the return value of the assembly version of memset.
It adds a 'mov' instruction and merges an additional load+store into
existing load/store instructions.
For ease of review, here is a breakdown of the patch into 4 simple steps:
Step 1
======
Perform the following substitutions:
ip -> r8, then
r0 -> ip,
and insert 'mov ip, r0' as the first statement of the function.
At this point, we have a memset() implementation returning the proper result,
but corrupting r8 on some paths (the ones that were using ip).
Step 2
======
Make sure r8 is saved and restored when (! CALGN(1)+0) == 1:
save r8:
- str lr, [sp, #-4]!
+ stmfd sp!, {r8, lr}
and restore r8 on both exit paths:
- ldmeqfd sp!, {pc} @ Now <64 bytes to go.
+ ldmeqfd sp!, {r8, pc} @ Now <64 bytes to go.
(...)
tst r2, #16
stmneia ip!, {r1, r3, r8, lr}
- ldr lr, [sp], #4
+ ldmfd sp!, {r8, lr}
Step 3
======
Make sure r8 is saved and restored when (! CALGN(1)+0) == 0:
save r8:
- stmfd sp!, {r4-r7, lr}
+ stmfd sp!, {r4-r8, lr}
and restore r8 on both exit paths:
bgt 3b
- ldmeqfd sp!, {r4-r7, pc}
+ ldmeqfd sp!, {r4-r8, pc}
(...)
tst r2, #16
stmneia ip!, {r4-r7}
- ldmfd sp!, {r4-r7, lr}
+ ldmfd sp!, {r4-r8, lr}
Step 4
======
Rewrite register list "r4-r7, r8" as "r4-r8".
Signed-off-by: Ivan Djelic <ivan.djelic@parrot.com>
Reviewed-by: Nicolas Pitre <nico@linaro.org>
Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
(cherry picked from commit 455bd4c430b0c0a361f38e8658a0d6cb469942b5)
|
|
This change fixes a linking problem, which happens if oprofile is selected to
be compiled as built-in:
`oprofile_arch_exit' referenced in section `.init.text' of
arch/arm/oprofile/built-in.o: defined in discarded section
`.exit.text' of arch/arm/oprofile/built-in.o
The problem is appeared after commit 87121ca504, which introduced
oprofile_arch_exit() calls from __init function. Note that the aforementioned
commit has been backported to stable branches, and the problem is known to be
reproduced at least with 3.0.13 and 3.1.5 kernels.
Cc: stable@kernel.org # 3.0+
Cc: Will Deacon <will.deacon@arm.com>
Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@nokia.com>
Signed-off-by: Robert Richter <robert.richter@amd.com>
|
|
|
|
The issue was caused due to sched_clock() inplementation in pit.c which reported values which were incosistent with what it should
|
|
default console (i.e. printf) for MQX as of the beta-3 release.
|
|
|
|
|
|
routing interrupt routing bits unchanged
|
|
Signed-off-by: Ed Nash <ed@kidlearn.com>
|
|
|
|
manually integrate from the CAAM part by Jason
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
|
|
From Singh Pradip-B09147. Integrate by Jason Jin
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
|
|
Signed-off-by: Alison Wang <b18965@freescale.com>
|
|
Add platform support for ADC driver.
Signed-off-by: Wang Xiaojun <b41435@freescale.com>
|
|
Handle usb suspend/resume, currently the BSP doesn't
support usb plug/unplug wakeup.
Signed-off-by: Jingchang Lu <b35083@freescale.com>
|
|
Signed-off-by: Jingchang Lu <b35083@freescale.com>
|
|
Fix layers blending and reinitialization issue for DCU driver.
Update power management part for DCU driver.
Signed-off-by: Alison Wang <b18965@freescale.com>
|
|
System could run into STOP and LPRun modes. When system was working in STOP mode,
pressing SW1 button or inserting or removing SD card could wake up it.
Signed-off-by: Alison Wang <b18965@freescale.com>
|
|
Add platform support for Vybrid L2 switch driver.
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
|
|
Add second FEC support for Vybrid.
Signed-off-by: Alison Wang <b18965@freescale.com>
|
|
Add platform support for watchdog driver.
Signed-off-by: Wang Xiaojun <b41435@freescale.com>
|
|
Add hardware flow control support,
Add transmit DMA support,
Add FIFO operation support,
Add MSB/LSB on data support,
Add 9-bits MARK/SPACE support.
Signed-off-by: Jingchang Lu <b35083@freescale.com>
|
|
Add platform support for Quad SPI driver.
Signed-off-by: Alison Wang <b18965@freescale.com>
Xiaochun Li <b41219@freescale.com>
|
|
Add platform support for touch screen driver.
Signed-off-by: Alison Wang <b18965@freescale.com>
|
|
Update platform support for dspi driver after debugging on board.
Signed-off-by: Jason Jin <jason.jin@freescale.com>
Alison Wang <b18965@freescale.com>
|
|
Four LEDS are connected to FTM0 ch0~3 on TWR-MVF600 board,
the PWM signal can use control these LEDS on/off or demo.
Signed-off-by: Jingchang Lu <b35083@freescale.com>
|
|
The FlexTimer work on PWM mode with EPWM and CPWM supported.
The API configures each FTM channels the same due to pwm subsystem
interface restriction.
Signed-off-by: Jingchang Lu <b35083@freescale.com>
|
