ADIv5 transport support moves to separate files
commit6f8b8593d63bc9781435270a54b6f7d245eecd8e
authorDavid Brownell <dbrownell@users.sourceforge.net>
Tue, 16 Mar 2010 21:12:00 +0000 (16 14:12 -0700)
committerDavid Brownell <dbrownell@users.sourceforge.net>
Tue, 16 Mar 2010 21:12:00 +0000 (16 14:12 -0700)
tree5b5928e9b4b2cfbafe287dd5d69c85254c099e2d
parent030ee192dd9647b10ff0841a671facec9d6b833f
ADIv5 transport support moves to separate files

Unclutter arm_adi_v5.c by moving most transport-specific code
to a transport-specific files adi_v5_{jtag,swd}.c ... it's not
a full cleanup, because of some issues which need to be addressed
as part of SWD support (along with implementing the DAP operations
on top of SWD transport):

 - The mess where mem_ap_read_buf_u32() is currently coded to
   know about JTAG scan chains, and thus needs rewriting before
   it will work with SWD;

 - Initialization is still JTAG-specific

Also  move JTAG_{DP,ACK}_* constants from adi_v5.h to the JTAG
file; no other code should care about those values.

Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
src/target/Makefile.am
src/target/adi_v5_jtag.c [new file with mode: 0644]
src/target/adi_v5_swd.c [new file with mode: 0644]
src/target/arm_adi_v5.c
src/target/arm_adi_v5.h