Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2424171pxb; Sat, 30 Jan 2021 02:07:08 -0800 (PST) X-Google-Smtp-Source: ABdhPJwhqF/pTevqb/c5ahYoXkTsV2T2w7uCMw+d6yL559YAFwpmT4t0p5zCCos1RNtJ2cmwBmJv X-Received: by 2002:a17:906:3401:: with SMTP id c1mr8675018ejb.156.1612001227903; Sat, 30 Jan 2021 02:07:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612001227; cv=none; d=google.com; s=arc-20160816; b=b/LRSDSDLPr5eWb5QGh/bxN/IitpGD3lhlImBBUXvwpcDTNoXBWserTS5/dTTnWEkN CT6lyDqU9xS1edlr86KUW23MkAM9mJFLqE/LsuUQhwTxMOaO5iw5h+nlNv01xyV7okvP oDJLEkQSkJY1NZ/b2l9/r+VtKJTMQM8+C9+7y5P3k1FQuGhOTtuAwwZu2QI8lyIcxnHR mPdOzugTkdzVnWNTJn2MB52i/3CYXyJ55lobYMySYHh8MyTzDy+/VXNKXHiwzpz4SdUz BqUaGJazSAeZWSdpxhNlUs3v+DaV0uz8l74poQ12JiqRbZFRwuNh9u0yfP60GWl2XEqe qzEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:references:in-reply-to:message-id:date:subject :cc:to:from:ironport-sdr:ironport-sdr; bh=QbkjJKm37trdKj65WtxK0PctGgOWy0BOFbg2tkdUlsI=; b=N07FeGXGROrlsXIRj2OE+naIjcHh5jKZqASBFeIhdPh3rap2X6QwfRZn0d+1wHT2U3 /hmWv+EJyX56PDsPkTgwfGZptHKf+2w+zeLf+kC8J+OI+N3fN4HmSgPtDofT8AxRU7G/ RESrqy2cpEbp4NeYW6EmxFzofZxhIa1c5fI4aG7EscAAIgIxwu20w8ET+6YvEtHiGpb+ LhCwy6FFrhMmZaI5AyfXZ5N6Gy0p6DbE/Om99C7coz500YWzHj9KI2R5AdqoONsyHj9Z maxBnPVH7k+LRa93WebA4HuzqB+/ktVi5Ebemewun7lp54B1JN/tRJaNbkLISyiexQ7E OGWg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v3si6533066edw.127.2021.01.30.02.06.43; Sat, 30 Jan 2021 02:07:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231701AbhA3KFl (ORCPT + 99 others); Sat, 30 Jan 2021 05:05:41 -0500 Received: from mga11.intel.com ([192.55.52.93]:25408 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233194AbhA3Crl (ORCPT ); Fri, 29 Jan 2021 21:47:41 -0500 IronPort-SDR: rAosmi/eCJcjvg2irvDbSPrFhibh/lSmw1e7sm8UeLsWsrd4UeuBNGKaI8eo6OVDjGqUMryAYo 2vcbj+IYG+qw== X-IronPort-AV: E=McAfee;i="6000,8403,9879"; a="177000085" X-IronPort-AV: E=Sophos;i="5.79,387,1602572400"; d="scan'208";a="177000085" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2021 18:21:30 -0800 IronPort-SDR: fYWIPAP77KQb9KhFT6x6lbuztG9kkio5XdOGEU5F2uffjI93VPQ5/03bzF9s0/QaIabOJmzoU6 ldJNlVo/26pQ== X-IronPort-AV: E=Sophos;i="5.79,387,1602572400"; d="scan'208";a="579672318" Received: from smtp.ostc.intel.com ([10.54.29.231]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2021 18:21:29 -0800 Received: from mtg-dev.jf.intel.com (mtg-dev.jf.intel.com [10.54.74.10]) by smtp.ostc.intel.com (Postfix) with ESMTP id B3187636D; Fri, 29 Jan 2021 18:21:29 -0800 (PST) Received: by mtg-dev.jf.intel.com (Postfix, from userid 1000) id A7D3A36367C; Fri, 29 Jan 2021 18:21:29 -0800 (PST) From: mgross@linux.intel.com To: markgross@kernel.org, mgross@linux.intel.com, arnd@arndb.de, bp@suse.de, damien.lemoal@wdc.com, dragan.cvetic@xilinx.com, gregkh@linuxfoundation.org, corbet@lwn.net, palmerdabbelt@google.com, paul.walmsley@sifive.com, peng.fan@nxp.com, robh+dt@kernel.org, shawnguo@kernel.org, jassisinghbrar@gmail.com Cc: linux-kernel@vger.kernel.org, Srikanth Thokala , linux-doc@vger.kernel.org Subject: [PATCH v4 08/34] misc: xlink-pcie: Add documentation for XLink PCIe driver Date: Fri, 29 Jan 2021 18:20:58 -0800 Message-Id: <20210130022124.65083-44-mgross@linux.intel.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20210130022124.65083-1-mgross@linux.intel.com> References: <20210130022124.65083-1-mgross@linux.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Srikanth Thokala Provide overview of XLink PCIe driver implementation Cc: Jonathan Corbet Cc: linux-doc@vger.kernel.org Reviewed-by: Mark Gross Signed-off-by: Mark Gross Signed-off-by: Srikanth Thokala --- Documentation/vpu/index.rst | 1 + Documentation/vpu/xlink-pcie.rst | 90 ++++++++++++++++++++++++++++++++ 2 files changed, 91 insertions(+) create mode 100644 Documentation/vpu/xlink-pcie.rst diff --git a/Documentation/vpu/index.rst b/Documentation/vpu/index.rst index 7e290e048910..661cc700ee45 100644 --- a/Documentation/vpu/index.rst +++ b/Documentation/vpu/index.rst @@ -14,3 +14,4 @@ This documentation contains information for the Intel VPU stack. :maxdepth: 2 vpu-stack-overview + xlink-pcie diff --git a/Documentation/vpu/xlink-pcie.rst b/Documentation/vpu/xlink-pcie.rst new file mode 100644 index 000000000000..85a70990e9c9 --- /dev/null +++ b/Documentation/vpu/xlink-pcie.rst @@ -0,0 +1,90 @@ +.. SPDX-License-Identifier: GPL-2.0 + +================================ +Kernel driver: Xlink-pcie driver +================================ +Supported chips: + * Intel Edge.AI Computer Vision platforms: Keem Bay + Suffix: Bay + Slave address: 6240 + Datasheet: Publicly available at Intel + +Author: Srikanth Thokala Srikanth.Thokala@intel.com + +Introduction +============ +The Xlink-pcie driver provides transport layer implementation for +the data transfers to support Xlink protocol subsystem communication with the +peer device, i.e., between remote host system and Keem Bay device. + +The Keem Bay device is an ARM-based SOC that includes a vision processing +unit (VPU) and deep learning, neural network core in the hardware. +The Xlink-pcie driver exports a functional device endpoint to the Keem Bay +device and supports two-way communication with the peer device. + +High-level architecture +======================= +Remote Host: IA CPU +Local Host: ARM CPU (Keem Bay):: + + +------------------------------------------------------------------------+ + | Remote Host IA CPU | | Local Host ARM CPU (Keem Bay) | | + +==================================+=+===============================+===+ + | User App | | User App | | + +----------------------------------+-+-------------------------------+---+ + | XLink UAPI | | XLink UAPI | | + +----------------------------------+-+-------------------------------+---+ + | XLink Core | | XLink Core | | + +----------------------------------+-+-------------------------------+---+ + | XLink PCIe | | XLink PCIe | | + +----------------------------------+-+-------------------------------+---+ + | XLink-PCIe Remote Host driver | | XLink-PCIe Local Host driver | | + +----------------------------------+-+-------------------------------+---+ + |-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:|:|:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:| + +----------------------------------+-+-------------------------------+---+ + | PCIe Host Controller | | PCIe Device Controller | HW| + +----------------------------------+-+-------------------------------+---+ + ^ ^ + | | + |------------- PCIe x2 Link -----------------| + +This XLink PCIe driver comprises of two variants: +* Local Host driver + + * Intended for ARM CPU + * It is based on PCI Endpoint Framework + * Driver path: {tree}/drivers/misc/Xlink-pcie/local_host + +* Remote Host driver + + * Intended for IA CPU + * It is a PCIe endpoint driver + * Driver path: {tree}/drivers/misc/Xlink-pcie/remote_host + +XLink PCIe communication between local host and remote host is achieved through +ring buffer management and MSI/Doorbell interrupts. + +The Xlink-pcie driver subsystem registers the Keem Bay device as an endpoint +driver and provides standard Linux PCIe sysfs interface: +'/sys/bus/pci/devices/xxxx:xx:xx.0/' + + +XLink protocol subsystem +======================== +Xlink is an abstracted control and communication subsystem based on channel +identification. It is intended to support VPU technology both at SoC level as +well as at IP level, over multiple interfaces. + +- The Xlink subsystem abstracts several types of communication channels + underneath, allowing the usage of different interfaces with the + same function call interface. +- The Communication channels are full-duplex protocol channels allowing + concurrent bidirectional communication. +- The Xlink subsystem also supports control operations to VPU either + from standalone local system or from remote system based on communication + interface underneath. +- The Xlink subsystem supports the following communication interfaces: + * USB CDC + * Gigabit Ethernet + * PCIe + * IPC -- 2.17.1