Message ID | LV8PR11MB84634960758E20E781DB638F8B7D2@LV8PR11MB8463.namprd11.prod.outlook.com |
---|---|
State | Changes Requested, archived |
Headers | show |
Series | JTAG driver introduction | expand |
On Tue, Jan 30, 2024 at 11:32:14PM +0000, Corona, Ernesto wrote: > JTAG class driver provide infrastructure to support hardware/software JTAG platform drivers. It provide user layer API interface for flashing and debugging external devices which equipped with JTAG interface using standard transactions. Please properly wrap your changelog text, didn't checkpatch warn of this? > Driver exposes set of IOCTL to user space for: > - XFER: > SIR (Scan Instruction Register, IEEE 1149.1 Data Register scan); > SDR (Scan Data Register, IEEE 1149.1 Instruction Register scan); > - GIOCSTATUS read the current TAPC state of the JTAG controller > - SIOCSTATE Forces the JTAG TAPC to go into a particular state. > - SIOCFREQ/GIOCFREQ for setting and reading JTAG frequency. > - IOCBITBANG for low level control of JTAG signals. Where are these ioctls implemented? THat has nothing to do with this patch itself, right? And what's the "30" in the patch number above for? confused, greg k-h
diff --git a/Documentation/userspace-api/ioctl/ioctl-number.rst b/Documentation/userspace-api/ioctl/ioctl-number.rst index 457e16f06e04..cf602aa3a853 100644 --- a/Documentation/userspace-api/ioctl/ioctl-number.rst +++ b/Documentation/userspace-api/ioctl/ioctl-number.rst @@ -358,6 +358,8 @@ Code Seq# Include File Comments 0xB6 all linux/fpga-dfl.h 0xB7 all uapi/linux/remoteproc_cdev.h <mailto:linux-remoteproc@vger.kernel.org> 0xB7 all uapi/linux/nsfs.h <mailto:Andrei Vagin <avagin@openvz.org>> +0xB9 00-0F linux/jtag.h JTAG driver + <mailto:ernesto.corona@intel.com> 0xC0 00-0F linux/usb/iowarrior.h 0xCA 00-0F uapi/misc/cxl.h 0xCA 10-2F uapi/misc/ocxl.h