From: Pavel Machek <pavel@ucw.cz>
To: Oleksandr Shamray <oleksandrs@mellanox.com>
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
openbmc@lists.ozlabs.org, joel@jms.id.au, jiri@resnulli.us,
tklauser@distanz.ch, linux-serial@vger.kernel.org,
vadimp@mellanox.com, system-sw-low-level@mellanox.com,
robh+dt@kernel.org, openocd-devel-owner@lists.sourceforge.net,
linux-api@vger.kernel.org, davem@davemloft.net,
mchehab@kernel.org
Subject: Re: [patch v14 4/4] Documentation: jtag: Add ABI documentation
Date: Mon, 12 Feb 2018 00:43:44 +0100 [thread overview]
Message-ID: <20180211234344.GA3864@localhost> (raw)
In-Reply-To: <1513268971-13518-5-git-send-email-oleksandrs@mellanox.com>
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
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch v14 4/4] Documentation: jtag: Add ABI documentation
Date: Mon, 12 Feb 2018 00:43:44 +0100 [thread overview]
Message-ID: <20180211234344.GA3864@localhost> (raw)
In-Reply-To: <1513268971-13518-5-git-send-email-oleksandrs@mellanox.com>
Hi!
> @@ -0,0 +1,27 @@
> +What: /dev/jtag[0-9]+
> +Date: October 2017
> +KernelVersion: 4.15
> +Contact: oleksandrs at 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
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2018-02-11 23:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 16:29 [patch v14 0/4] JTAG driver introduction Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
[not found] ` <1513268971-13518-1-git-send-email-oleksandrs-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-12-14 16:29 ` [patch v14 1/4] drivers: jtag: Add JTAG core driver Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
2017-12-14 18:13 ` Philippe Ombredanne
2017-12-14 18:13 ` Philippe Ombredanne
2017-12-14 16:29 ` [patch v14 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
[not found] ` <1513268971-13518-3-git-send-email-oleksandrs-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-12-14 18:14 ` Philippe Ombredanne
2017-12-14 18:14 ` Philippe Ombredanne
2017-12-14 18:14 ` Philippe Ombredanne
2017-12-15 1:34 ` Joel Stanley
2017-12-15 1:34 ` Joel Stanley
2017-12-15 1:34 ` Joel Stanley
2017-12-14 16:29 ` [patch v14 3/4] Documentation: jtag: Add bindings for " Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
2017-12-14 16:29 ` [patch v14 4/4] Documentation: jtag: Add ABI documentation Oleksandr Shamray
2017-12-14 16:29 ` Oleksandr Shamray
2018-02-11 23:43 ` Pavel Machek [this message]
2018-02-11 23:43 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180211234344.GA3864@localhost \
--to=pavel@ucw.cz \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=joel@jms.id.au \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=oleksandrs@mellanox.com \
--cc=openbmc@lists.ozlabs.org \
--cc=openocd-devel-owner@lists.sourceforge.net \
--cc=robh+dt@kernel.org \
--cc=system-sw-low-level@mellanox.com \
--cc=tklauser@distanz.ch \
--cc=vadimp@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.