Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp255422imm; Wed, 30 May 2018 23:04:16 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKQYGZv0ljNrM/wOrS7YNWWpf5NjJI9VTVzYYQiBu3YjTxnSpU4m815kRdnVmeP9nuQXoEX X-Received: by 2002:a17:902:28ab:: with SMTP id f40-v6mr5734650plb.208.1527746655973; Wed, 30 May 2018 23:04:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527746655; cv=none; d=google.com; s=arc-20160816; b=z/fqOAr2rVPBdLCqvAX9jvpnh2f0pjaFjn8X1zUHNeX/+Pb5v8yKB7tWJTD/CtK8WB aKIxvsOM1UiEN4y/5dhn6qmlMU0R+Xl4/8ZbxeUEiStnzwS6XcpcHD8mjgXPp2vGGc/P Gvr5s7hqB+yM7Qe/Swpj4kAWDEvhAfD52Ewaecx0lEM2imVykBPGzSqNOx+gG+qPsvLq ZTOybmrPNRw0pOMgxZEzFNhPeIe1leBunPGzb2WzpLGj1v1RKHg4SmJ1oEpjpN6DUtOt /yW+vAVujenbVFspAiIQ2j/QpTT06VmVxvA2eXAiF5/wNl4DYyZyAj4ofIEhQIWZ2HLY C0/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=T3g5ge4tUcmEqh+3blefbcMaGFCx16wgusDvzMXOcYY=; b=IrxQ8XDm9Yw6FIgyiLBiUhapbZuMv2rFBxTzimGAmzl5mkCT9ODSdaxxFuBgVluJfm 4xjWLxF1FeYxvMWTatsLWw8jdOswZs9d2+JRIMBc+H6Ff5OkXu1Pn3+bMQvsVt3Btw3g 6MmyXymO5F5myyPnwfbVH7niRuTXUW/vfC3eq+xy5wGvz8bNKpIHzp/SBdp51zXrnhjj 6SkNJ+X/HQuQTHY1c2OpiotOYR70FokmpDqwzgZ2QKcVvfpVFRLG85fBZJgOARE2C9Zi 5lg5SvWYu6AaA1EgJGSacF3axNmfLQpEZHNSUKrqhroaJHRN8+uASaDy2dXGHGBLw29b K+4Q== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 82-v6si36234784pfs.40.2018.05.30.23.04.01; Wed, 30 May 2018 23:04:15 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753981AbeEaGCG (ORCPT + 99 others); Thu, 31 May 2018 02:02:06 -0400 Received: from mga18.intel.com ([134.134.136.126]:31759 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751037AbeEaGCF (ORCPT ); Thu, 31 May 2018 02:02:05 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 May 2018 23:02:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,462,1520924400"; d="scan'208";a="60036401" Received: from helong-vb.png.intel.com ([10.226.242.245]) by fmsmga001.fm.intel.com with ESMTP; 30 May 2018 23:02:01 -0700 From: "Hean-Loong, Ong" To: Rob Herring , Dinh Nguyen , Daniel Vetter , Laurent Pinchart Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, dri-devel@lists.freedesktop.org, hean.loong.ong@intel.com, yves.vandervennet@intel.com, chin.liang.see@intel.com, Ong@vger.kernel.org Subject: [PATCHv8 0/3] Intel FPGA Video and Image Processing Suite Date: Thu, 31 May 2018 14:01:51 +0800 Message-Id: <1527746514-3861-1-git-send-email-hean.loong.ong@intel.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Ong, Hean Loong The FPGA FrameBuffer Soft IP could be seen as the GPU and the DRM driver patch here is allocating memory for information to be streamed from the ARM/Linux to the display port. Basically the driver just wraps the information such as the pixels to be drawn by the FPGA FrameBuffer 2. The piece of hardware in discussion is the SoC FPGA where Linux runs on the ARM chip and the FGPA is driven by its NIOS soft core with its own proprietary firmware. For example the application from the ARM Linux would have to write information on the /dev/fb0 with the information stored in the SDRAM to be fetched by the FPGA framebuffer IP and displayed on the Display Port Monitor. Ong Hean Loong (3): ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite ARM:socfpga-defconfig Intel FPGA Video and Image Processing Suite ARM:drm ivip Intel FPGA Video and Image Processing Suite .../devicetree/bindings/display/altr,vip-fb2.txt | 112 +++++++++++ arch/arm/configs/socfpga_defconfig | 5 + drivers/gpu/drm/Kconfig | 2 + drivers/gpu/drm/Makefile | 1 + drivers/gpu/drm/ivip/Kconfig | 14 ++ drivers/gpu/drm/ivip/Makefile | 9 + drivers/gpu/drm/ivip/intel_vip_conn.c | 96 ++++++++++ drivers/gpu/drm/ivip/intel_vip_core.c | 162 ++++++++++++++++ drivers/gpu/drm/ivip/intel_vip_drv.h | 52 ++++++ drivers/gpu/drm/ivip/intel_vip_of.c | 193 ++++++++++++++++++++ 10 files changed, 646 insertions(+), 0 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/altr,vip-fb2.txt create mode 100644 drivers/gpu/drm/ivip/Kconfig create mode 100644 drivers/gpu/drm/ivip/Makefile create mode 100644 drivers/gpu/drm/ivip/intel_vip_conn.c create mode 100644 drivers/gpu/drm/ivip/intel_vip_core.c create mode 100644 drivers/gpu/drm/ivip/intel_vip_drv.h create mode 100644 drivers/gpu/drm/ivip/intel_vip_of.c