From: Andrew Lunn <andrew@lunn.ch>
To: Oleksandr Shamray <oleksandrs@mellanox.com>
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
devicetree@vger.kernel.org, jiri@resnulli.us,
system-sw-low-level@mellanox.com, openbmc@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
openocd-devel-owner@lists.sourceforge.net, mec@shout.net,
robh+dt@kernel.org, joel@jms.id.au, linux-serial@vger.kernel.org,
vadimp@maellanox.com, tklauser@distanz.ch,
linux-arm-kernel@lists.infradead.org
Subject: Re: [patch v2 0/2]
Date: Wed, 9 Aug 2017 16:31:28 +0200 [thread overview]
Message-ID: <20170809143128.GI30723@lunn.ch> (raw)
In-Reply-To: <1502115467-1735-1-git-send-email-oleksandrs@mellanox.com>
On Mon, Aug 07, 2017 at 05:17:45PM +0300, Oleksandr Shamray wrote:
> When a need raise up to use JTAG interface for system's devices
> programming or CPU debugging, it could be done from the external
> JTAG master controller.
>
> For such purpose, usually the user layer
> application implements jtag protocol or using a proprietary
> connection to vendor hardware.
> This method is slow and not generic.
>
> We propose to implement general JTAG interface and infrastructure
> to communicate with user layer application.
Hi Oleksandr
You might find this discussion interesting:
https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2017-August/004721.html
You are defining a new ABI here, so linux-abi should be involved in
the discussion of these patches.
Andrew
next prev parent reply other threads:[~2017-08-09 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 14:17 [patch v2 0/2] Oleksandr Shamray
2017-08-07 14:17 ` [patch v2 1/2] drivers: jtag: Add JTAG core driver Oleksandr Shamray
2017-08-09 5:22 ` kbuild test robot
2017-08-07 14:17 ` [patch v2 2/2] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver Oleksandr Shamray
2017-08-10 20:58 ` Rob Herring
2017-08-09 14:31 ` Andrew Lunn [this message]
2017-08-10 15:18 ` [patch v2 0/2] Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-04-26 18:24 [PATCH " Jacopo Mondi
2017-08-19 18:03 sean.wang
2014-09-23 21:58 [PATCH 0/2] Fix a division by zero Greg Kroah-Hartman
2014-09-23 19:54 ` Frans Klaver
2014-09-24 7:55 ` [PATCH v2 0/2] Frans Klaver
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=20170809143128.GI30723@lunn.ch \
--to=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mec@shout.net \
--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@maellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).