Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3253777imm; Sun, 3 Jun 2018 23:42:52 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIFlQ6VPukqfjkEORfujIyvJBgnuApnn8LR6t04kWRP6EmcAxlPygD46Dq3BzQIaDtUA2oR X-Received: by 2002:a17:902:8c81:: with SMTP id t1-v6mr20362999plo.310.1528094572789; Sun, 03 Jun 2018 23:42:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528094572; cv=none; d=google.com; s=arc-20160816; b=T//EBUZtu4It+OOxpyV9dRYtD406UZT74Sz9Thz/JH5VouIO9ULQe1FMdSfy/6rhlq iYV1M2+m2d+t/E+WooqPRPeFAM1uCYaaymHv5u2iNas91j310OS6tmhIuX6f5iIjuTMJ SYrqFXkyYtQFcbP8hOnX2/aUdeASHKN1HESZTdUWNRcENu5jJjnhGA0LD+JBy0TvudFd uHE/FhF6Xdsc6pr7CCoSWgGKpMgEX6wokZprSraWOTV3rQgCflHgGpGwtMuxJ3cq9ezE ex8b2hokMBcCNW/BJbUq6M522mbi5t1KuAYnSk8tbpB7uJ/ysONjrAOl/kA3ZexhXQ9E qkXA== 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=wi+zNw5RQmtxnfuLiBAPy42LsRUHEguHY1cXDfqr7bc=; b=mHNw3PuCpf48poe6GCe22SWbb7f6FZUG6C+kmw6pLXR7JTGvqmssHJQNMk+C6nBJeg w1oJV3wGMnwN+8u/hgGKZsaByEiVmxB3FFYZ64T23qdVzAtNu92AUC947r5asyEzUGnY pTHWOwxlIommhx/yNGTRnj7tdEOCRoSrvZiHbyJIe1Q6hIhcqbqQxTL0r5PDCm+ijaRQ O1Z3Os20nzBPtEjuJ0tZcHEDwmONuZLmpmb/L9f97s6bvOmY9vJBp0Mz3094sQz7nnao H24Z4dP6cIwqqeDAZlU0+GLzGOSgQ8pZoUIEu6pgxwWTtPvRJsI28MUkcpyiFLzQ68eD rUpw== 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 n7-v6si858017pfn.270.2018.06.03.23.42.38; Sun, 03 Jun 2018 23:42:52 -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 S1751445AbeFDGkn (ORCPT + 99 others); Mon, 4 Jun 2018 02:40:43 -0400 Received: from mga06.intel.com ([134.134.136.31]:24439 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750731AbeFDGkl (ORCPT ); Mon, 4 Jun 2018 02:40:41 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jun 2018 23:40:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,475,1520924400"; d="scan'208";a="64069201" Received: from helong-vb.png.intel.com ([10.226.242.245]) by orsmga002.jf.intel.com with ESMTP; 03 Jun 2018 23:40:38 -0700 From: "Hean-Loong, Ong" To: Rob Herring , Dinh Nguyen , Daniel Vetter , Laurent Pinchart , Randy Dunlap 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, Ong@vger.kernel.org Subject: [PATCHv9 0/3] Intel FPGA Video and Image Processing Suite Date: Mon, 4 Jun 2018 14:40:01 +0800 Message-Id: <1528094404-3542-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 (2): ARM:socfpga-defconfig Intel FPGA Video and Image Processing Suite ARM:drm ivip Intel FPGA Video and Image Processing Suite Ong, Hean Loong (1): ARM:dt-bindings:display Intel FPGA Video and Image Processing Suite .../devicetree/bindings/display/altr,vip-fb2.txt | 99 ++++++++++ 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 | 95 ++++++++++ drivers/gpu/drm/ivip/intel_vip_core.c | 161 ++++++++++++++++ drivers/gpu/drm/ivip/intel_vip_drv.h | 52 ++++++ drivers/gpu/drm/ivip/intel_vip_of.c | 193 ++++++++++++++++++++ 10 files changed, 631 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