Message ID | 1513268971-13518-5-git-send-email-oleksandrs@mellanox.com |
---|---|
State | Not Applicable, archived |
Headers | show |
Series | JTAG driver introduction | expand |
Hi! > @@ -0,0 +1,27 @@ > +What: /dev/jtag[0-9]+ > +Date: October 2017 > +KernelVersion: 4.15 > +Contact: oleksandrs@mellanox.com > +Description: > + The misc device files /dev/jtag* are the interface > + between JTAG master interface and userspace. > + > + The ioctl(2)-based ABI is defined and documented in > + [include/uapi]<linux/jtag.h>. > + > + The following file operations are supported: > + > + open(2) > + The argument flag currently support only one access > + mode O_RDWR. > + > + ioctl(2) > + Initiate various actions. > + See the inline documentation in [include/uapi]<linux/jtag.h> > + for descriptions of all ioctls. I tried reading the jtag.h, and am still not sure how it works. Real docs would be nice... In particular, it seems to always specify read or write actiom. Sounds like a job for read/write syscalls? Pavel
diff --git a/Documentation/ABI/testing/jtag-dev b/Documentation/ABI/testing/jtag-dev new file mode 100644 index 0000000..cab867d --- /dev/null +++ b/Documentation/ABI/testing/jtag-dev @@ -0,0 +1,27 @@ +What: /dev/jtag[0-9]+ +Date: October 2017 +KernelVersion: 4.15 +Contact: oleksandrs@mellanox.com +Description: + The misc device files /dev/jtag* are the interface + between JTAG master interface and userspace. + + The ioctl(2)-based ABI is defined and documented in + [include/uapi]<linux/jtag.h>. + + The following file operations are supported: + + open(2) + The argument flag currently support only one access + mode O_RDWR. + + ioctl(2) + Initiate various actions. + See the inline documentation in [include/uapi]<linux/jtag.h> + for descriptions of all ioctls. + + close(2) + Stops and free up the I/O contexts that was associated + with the file descriptor. + +Users: TBD \ No newline at end of file