| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
SVN-Revision: 35916
|
| |
|
|
| |
SVN-Revision: 34169
|
| |
|
|
|
|
|
| |
SMP already selects HAVE_ARM_TWD and HAVE_ARM_SCU,
ARCH_CNS3XXX already selects MIGHT_HAVE_PCI
SVN-Revision: 34114
|
| |
|
|
| |
SVN-Revision: 34101
|
| |
|
|
| |
SVN-Revision: 33825
|
| |
|
|
|
|
|
|
| |
Properly terminate the correct platform resource for laguna UARTs
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33721
|
| |
|
|
|
|
|
|
| |
Resolves crashes when probing multiple serial devices
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33719
|
| |
|
|
|
|
|
|
|
| |
The Laguna boards do not use all the same pins for SDHCI as the Cavium
reference board.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33684
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ARM11MPCore Timer/Watchdog registers start at offset 0x600 which is where
all mpcore-wdt boards point the driver base too. I believe this is wrong
because 0x600 is aliased to the timer/watchdog of the 'current CPU' where
0x700 is CPU0's timer/watchdog, and 0x800 is CPU1's timer/watchdog. Thus
if your timer/watchdog application is switching between CPU's it can end up
writing to the wrong CPU's registers which results in random board resets
from watchdog timeouts etc.
This patch forces the timer/watchdog driver to use CPU0's registers always.
Its my opinion that other mpcore-wdt boards should be doing the same thing.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33683
|
| |
|
|
|
|
|
|
|
|
|
| |
Add GPIO/LED support for Gateworks GW2383
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
target/linux/cns3xxx/patches-3.3/300-laguna_support.patch | 18 +++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
SVN-Revision: 33649
|
| |
|
|
|
|
| |
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
SVN-Revision: 33580
|
| |
|
|
| |
SVN-Revision: 33502
|
|
|
SVN-Revision: 33486
|
