Date: Wed, 9 Aug 2017 16:31:28 +0200
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]
Message-ID: <20170809143128.GI30723@lunn.ch>
References: <1502115467-1735-1-git-send-email-oleksandrs@mellanox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1502115467-1735-1-git-send-email-oleksandrs@mellanox.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 784
Lines: 23

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