linux.git/arch/arc/kernel, branch v3.9-rc2

ARC: Fixup the current ABI version

2013-02-27T14:30:25+00:00

The upstream kernel ABI (v3) is different from current out-of-tree (v2):
* no-legacy-syscalls
* user_regs_struct layout has changed

So we rev up the ABI version

Signed-off-by: Vineet Gupta

ARC: make a copy of flat DT

2013-02-26T08:55:18+00:00

The flat DT (currently embedded in vmlinux) is in .init section.
The unflattened/binary tree doesn't copy strings through and references
them from orig flat DT - which could cause catestrohpy if of_* APIs are
called post init, say from a driver which is a loadable module.

Reported-by: James Hogan 
Signed-off-by: Vineet Gupta

ARC: Fix pt_orig_r8 access

2013-02-15T17:46:21+00:00

Syscall restarting fixes made pt_regs->orig_r8 a short word, which was
not reflected in the assembler code - thus could potentially break gdb
debugging.

Signed-off-by: Vineet Gupta

ARC: [3.9] Fallout of hlist iterator update

2013-02-15T17:46:20+00:00

Commit 0bbacca "hlist: drop the node parameter from iterators" changed
the iterator across the board - but ARC port being out-of-tree missed
it.

Signed-off-by: Vineet Gupta

ARC: 64bit RTSC timestamp hardware issue

2013-02-15T17:46:20+00:00

The 64bit RTSC is not reliable, causing spurious "jumps" in higher word,
making Linux timekeeping go bonkers. So as of now just use the lower
32bit timestamp.

A cleaner approach would have been removing RTSC support altogether as the
32bit RTSC is equivalent to old TIMER1 based solution, but some customers
can use the 32bit RTSC in SMP syn fashion (vs. TIMER1 which being incore
can't be done easily).

A fallout of this is sched_clock()'s hardware assisted version needs to
go away since it can't use 32bit wrapping counter - instead we use the
generic "weak" jiffies based version.

Signed-off-by: Vineet Gupta

ARC: [Review] Multi-platform image #7: SMP common code to use callbacks

2013-02-15T17:46:16+00:00

This again is for switch from singleton platform SMP API to
multi-platform paradigm

Platform code is not yet setup to populate the callbacks, that happens
in next commit

Signed-off-by: Vineet Gupta 
Cc: Arnd Bergmann 
Acked-by: Arnd Bergmann

ARC: [Review] Multi-platform image #4: Isolate platform headers

2013-02-15T17:46:14+00:00

-Top level ARC makefile removes -I for platform headers
-asm/irq.h no longer includes plat/irq.h

-platform makefile adds -I for it's specfic platform headers
-platform code to directly include it's plat/irq.h

-Linker script needed plat/memmap.h for CCM info, already in .config

Signed-off-by: Vineet Gupta 
Cc: Arnd Bergmann 
Acked-by: Arnd Bergmann

ARC: [Review] Multi-platform image #3: switch to board callback

2013-02-15T17:46:14+00:00

-platform API is retired and instead callbacks are used

Signed-off-by: Vineet Gupta 
Cc: Arnd Bergmann 
Acked-by: Arnd Bergmann

ARC: [Review] Multi-platform image #2: Board callback Infrastructure

2013-02-15T17:46:13+00:00

The orig platform code orgnaization was singleton design pattern - only
one platform (and board thereof) would build at a time.

Thus any platform/board specific code (e.g. irq init, early init ...)
expected by ARC common code was exported as well defined set of APIs,
with only ONE instance building ever.

Now with multiple-platform build requirement, that design of code no
longer holds - multiple board specific calls need to build at the same
time - so ARC common code can't use the API approach, it needs a
callback based design where each board registers it's specific set of
functions, and at runtime, depending on board detection, the callbacks
are used from the registry.

This commit adds all the infrastructure, where board specific callbacks
are specified as a "maThine description".

All the hooks are placed in right spots, no board callbacks registered
yet (with MACHINE_STARt/END constructs) so the hooks will not run.

Next commit will actually convert the platform to this infrastructure.

Signed-off-by: Vineet Gupta 
Cc: Arnd Bergmann 
Acked-by: Arnd Bergmann

ARC: Hostlink Pseudo-Driver for Metaware Debugger

2013-02-15T17:46:10+00:00

This allows ARC Target to do I/O to host in absence of any peripherals
whatsoever, assisted by Metaware Hostlink facility.

Further we have a FUSE based filesystem which makes us mount/access host
filesystem on target and do fops.

Signed-off-by: Vineet Gupta