Received: by 10.223.176.5 with SMTP id f5csp753111wra; Tue, 30 Jan 2018 19:04:18 -0800 (PST) X-Google-Smtp-Source: AH8x224NqxmOlvtk2QMrTsTpcosE+uXH4J7NBJaCVJRvqzUhNAfie8lerUUg2XUgXjZ/zf+PPfXL X-Received: by 10.98.82.68 with SMTP id g65mr32473607pfb.212.1517367858595; Tue, 30 Jan 2018 19:04:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517367858; cv=none; d=google.com; s=arc-20160816; b=NbWJ7a7kRtVLAPudkcKYGyRv4b0CfkLqAAj0u8pq4WmwgmTabz4FyziFCgrK6R2oZG CtooEmatYOROnKh2xbPypZbfvC64mdbnJ7YTALVuiv6PDUf3v1N7WOo6+N/EQdRy6Fzx /cKBaoUHX0LOWt1V4qZoEij/qjQDbNfVQ2n2ucmTyIGLBVPXqL3opacpYH4Gdi/UZZ/u rXFTDAZSnmITL39cIzski+gramysDYqW7Jx7P7B6vFUpmHia3zv99KGg8v2NZgRffp5U ERJ6TprQXQh0hQ5LpmdBQNaVokfJFkFVjp6WD1Jx5B6tN/Tlmhbl4qz2Had28ztMNE1z Uhlw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:subject:from:dkim-signature :arc-authentication-results; bh=0nbenLWKAKZe4OXNNgpOxyoDYsxfdDCIKGIERFtBFQI=; b=HyXPdo3sEWlxS80XvnKpxT8PEuk6VhpG2FwvkrabSMmZhkoH7rQE9HRzcZjfv2QPcJ Bp7r+A519N8ni5XEmmSxkP7YjjyyP+gS2ra+9O9JEbm4Z2NUUzWkf22+RCn1NKVxirm8 vy4qTGgXcQPMQ1gydgrrqNfxwrqXQVdlo0VtuP6uXkEXKcl+hdFaInIJhDqjAUmmqei7 E8ZEpOg9exAVPRAagj/uOgK3F9ZuReGv0YR2mtukcSkQ2N7IdWDjjle7Jgb9fcZVpgAJ 9C9VjsHFhfXPmnxmmGMzmCUqhXrQB05ewcZX2CaqO2hdkSvVL5/h7u2+UD3ws9z12x7k iVww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=HYGDrOA0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r11-v6si876434plo.624.2018.01.30.19.04.03; Tue, 30 Jan 2018 19:04:18 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=HYGDrOA0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752015AbeAaDDg (ORCPT + 99 others); Tue, 30 Jan 2018 22:03:36 -0500 Received: from mail-qt0-f195.google.com ([209.85.216.195]:38850 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751404AbeAaDDe (ORCPT ); Tue, 30 Jan 2018 22:03:34 -0500 Received: by mail-qt0-f195.google.com with SMTP id z10so20097605qti.5; Tue, 30 Jan 2018 19:03:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=0nbenLWKAKZe4OXNNgpOxyoDYsxfdDCIKGIERFtBFQI=; b=HYGDrOA0N3qiSpm0OXK19wAib0M9r/YUpXgwdsGFw1cwBEKjuBCj1PB0cn9hSuar/3 pIa3vMXchftvHBnk+gIjBcNOmeUHV8JKkbcrNY4N31rrC9DYDFW3Lj/7m1vLhOucGvpH owtJtVz5q5IlcnEwDSRcOWcqqyv2LMY6o1DKi2zNicg8hIoh+B69aaJpO9fdM3CVORlh Nlbfeb7swtX++5KAyY0V6lZFDJ2fbXlXc1Yt0PMml5K6cA9JjFcPOVOc+hD1QNUbuWOm i2JznUGPbykxWYN10E7XqeHATcrkAqyY/vbMaEQbf3ZUFWvmgwqzJGbNjVoJmGdNd8iB G7kg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=0nbenLWKAKZe4OXNNgpOxyoDYsxfdDCIKGIERFtBFQI=; b=WN9ReoiWrTQgH/Iv8W926M8o8FMjI9Nvoi7pjNZcXQQHtdWTnNGv0ENf80wqzYsoBR REBJ+U4UCsKqGaJZCaSL+fF18FBOOzA1XQ3HITxVrb5n9YA73CCb4G6Kg6Lx7bU6s+w2 XCfWysdNvMV3D3Jv0PluJEUGYgz8Mn8Crev8AZM0jwrbxDmykVjCaQa+xwALbldzKM1h H6QSdAmpPyhATeHhGfM0FZ+yx0uw1btMDUQbTdm76c2CDIhl52n1iyX7Uk9sJrDvqj3x 6mQ45Ze+S4m6Hi8Kx7D8YapJ+bCVO1lvU36smnYMGhjypm/lAQh4k4RmNfR1sCQI/Wn0 Gevw== X-Gm-Message-State: AKwxytdiBjW4oPIsuFCnjaMNllk9TmsSxAhjtW1DZfd5P+wMxd+HcjVa Nh0QkYzOC0qt//COLsGxFIk= X-Received: by 10.237.32.225 with SMTP id 88mr1231620qtb.99.1517367813567; Tue, 30 Jan 2018 19:03:33 -0800 (PST) Received: from ?IPv6:2001:470:d:73f:60d3:5d7f:dbfa:245f? ([2001:470:d:73f:60d3:5d7f:dbfa:245f]) by smtp.gmail.com with ESMTPSA id y29sm12774910qtk.47.2018.01.30.19.03.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jan 2018 19:03:32 -0800 (PST) From: Florian Fainelli Subject: Re: [patch v18 0/4] JTAG driver introduction To: Oleksandr Shamray , gregkh@linuxfoundation.org, arnd@arndb.de Cc: 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 References: <1517236305-4880-1-git-send-email-oleksandrs@mellanox.com> Message-ID: Date: Tue, 30 Jan 2018 19:03:29 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <1517236305-4880-1-git-send-email-oleksandrs@mellanox.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/29/2018 06:31 AM, Oleksandr Shamray wrote: > When a need raise up to use JTAG interface for system's devices > programming or CPU debugging, usually the user layer > application implements jtag protocol by bit-bang or using a > proprietary connection to vendor hardware. > This method can be slow and not generic. > > We propose to implement general JTAG interface and infrastructure > to communicate with user layer application. In such way, we can > have the standard JTAG interface core part and separation from > specific HW implementation. > This allow new capability to debug the CPU or program system's > device via BMC without additional devices nor cost. Oleksandr, you have completed dodged my questions here: https://lkml.org/lkml/2017/12/25/163 can you try to respond to some of these questions please? -- Florian