diff options
author | David Brownell <dbrownell@users.sourceforge.net> | 2010-02-27 00:12:38 -0800 |
---|---|---|
committer | David Brownell <dbrownell@users.sourceforge.net> | 2010-02-27 00:12:38 -0800 |
commit | a3245bd7cdd2d8c3740c5e8f31efcd78de67837a (patch) | |
tree | 37448ab9163c86ea221c821b956be11ebd06ebe8 /src/jtag/minidriver/minidriver_imp.h | |
parent | 4a64820f230a267b1f2e36d4be567074e5b8cb76 (diff) | |
download | openocd+libswd-a3245bd7cdd2d8c3740c5e8f31efcd78de67837a.tar.gz openocd+libswd-a3245bd7cdd2d8c3740c5e8f31efcd78de67837a.tar.bz2 openocd+libswd-a3245bd7cdd2d8c3740c5e8f31efcd78de67837a.tar.xz openocd+libswd-a3245bd7cdd2d8c3740c5e8f31efcd78de67837a.zip |
interface: define TMS sequence command
For support of SWD we need to be able to clock out special bit
sequences over TMS or SWDIO. Create this as a generic operation,
not yet called by anything, which is split as usual into:
- upper level abstraction ... here, jtag_add_tms_seq();
- midlayer implementation logic hooking that to the lowlevel code;
- lowlevel minidriver operation ... here, interface_add_tms_seq();
- message type for request queue, here JTAG_TMS.
This is done slightly differently than other operations: there's a flag
saying whether the interface driver supports this request. (In fact a
flag *word* so upper layers can learn about other capabilities too ...
for example, supporting SWD operations.)
That approach (flag) lets this method *eventually* be used to eliminate
pathmove() and statemove() support from most adapter drivers, by moving
all that logic into the mid-layer and increasing uniformity between the
various drivers. (Which will in turn reduce subtle bugginess.)
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'src/jtag/minidriver/minidriver_imp.h')
0 files changed, 0 insertions, 0 deletions