From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 25F3AC4706F for ; Thu, 4 Jan 2024 08:03:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Qp4k4sA4yTKsmpZzT+HnmqgAt1/DxGPmZmOIbnzhKpQ=; b=lmQ/D6ezGOOose O5Gm905hvXVvchTVThJcop3LehktUW2CZvYSnEFK1eT8U2xEO/edfjIuJ5BDmJZvdZrVlVdul9v34 XJAAA3r2H3Yg+wRjGWCYwqzhrLyKgLIQuarQdCYEi7XYM2BttkDUs5aJ3i4LGYLYBvO6fr3DnRX4M xi9tP+bispw7TSpd73qD3WmiSKycwZ2CMoCIIqG8IpR7drfQoBGswk62moJu9gFX8e1yRgU7QOL6U EGtrb6LS8yHRAklbiNu9AFDO2WJKPgiP9PleFVvGkfBXO3bbqyKfGi3pa2zSKnCz9BE2BAcjgKuXe uITdiSTkT6zk6X949+Zw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1rLIgh-00D9ZC-1S; Thu, 04 Jan 2024 08:02:47 +0000 Received: from ams.source.kernel.org ([2604:1380:4601:e00::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1rLIge-00D9YP-1f for linux-arm-kernel@lists.infradead.org; Thu, 04 Jan 2024 08:02:46 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by ams.source.kernel.org (Postfix) with ESMTP id 31F07B80E7E; Thu, 4 Jan 2024 08:02:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0D555C433C7; Thu, 4 Jan 2024 08:02:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1704355362; bh=pp0So8gs5MkuWez0uSmAaEFSV4iDlUOwU5mnTRXt3yU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ZT148dVL8fyl//AMobk+iTX7hdxXTXCLo7CI1q4rQ/2nxySks0j8rIhnNRbrD7ix8 aqt1yPlxzziKE9MaIi7S/Y5UZXc3lW2V4j7QhjzoINuNOOZRoWv4ZB2oeYupmi1bKs xEqpHLIequJul/pMBeBEHX195HAeP+OqS7/hRc68= Date: Thu, 4 Jan 2024 09:02:39 +0100 From: "gregkh@linuxfoundation.org" To: "Manne, Nava kishore" Cc: "mdf@kernel.org" , "hao.wu@intel.com" , "yilun.xu@intel.com" , "trix@redhat.com" , "peter.colberg@intel.com" , "conor.dooley@microchip.com" , "v.georgiev@metrotek.ru" , "Simek, Michal" , Marco Pagani , "ruanjinjie@huawei.com" , "linux-fpga@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "git (AMD-Xilinx)" Subject: Re: [RFC] FPGA Subsystem User Space Interface Proposal Message-ID: <2024010451-syrup-obituary-3388@gregkh> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240104_000244_819034_6F85DB28 X-CRM114-Status: GOOD ( 15.59 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Jan 04, 2024 at 04:52:15AM +0000, Manne, Nava kishore wrote: > ======================================================================= > | Introduction | > ======================================================================= > This document provides a detailed overview of the proposed Kernel feature for FPGA Manager subsystem user interface. > It describes the problem statement behind the proposal, the problem to be solved, a top-level solution design. > > Table of Contents: > ------------------ > A. Problem Statement and Background > B. Scope and Out of scope of the proposal > B.1 Scope > B.2 Out of scope > C. Proposed Solution > D. Proposed User Interface Details > ======================================================================= > | A. Problem Statement and Background | > ======================================================================= > The existing FPGA manager subsystem didn't have any user space interface (other than the status/state in sysfs) in Kernel. > Basically, FPGAs are semiconductor devices that can be reprogrammed for desired hardware functionality. > FPGAs can be reprogrammed at runtime with different types of logic and IPs as per user need and hence there is a need to use device tree overlays for removing/updating/adding the devices at runtime for the IPs/controllers that are present in FPGA. > But we don't have any user interface in kernel for updating the device tree at runtime. Can you line-wrap your emails to make them easier to read? Also, something went wrong here: > . --------------------------------------. .-----------------------------------------. > | | | | > | .------------------| |---------------------. | > | | sysfs_load() |<=======> |Overaly_apply()| | > .---------------------------------. | '------------------| |---------------------' | > | | | | | | > | New Sysfs interface | ====> | of-fpga-region .c | | DT Overlay.c | > | load/unload | | | | | > '--------------------------------' | .---------------------| |-------------------------. | > | | sysfs_unload() |<=======> | Overlay_remove() | | > | '-------------------- | |-------------------------' | > | | | | > '----------------------------------- --' '------------------------------------------' And here: > .-----------------------. .--------------------------------------------. > | Host CPU | | FPGA | > | | | | > | -- -| | ----------- --------- | > | | H | | |==>| Bridge0 |<==>| PRR0 | | > | | W| | | ----------- -------- | > | | | | | | > | | B |<=====> |<== | ----------- -------- | > | | R | | |==>| Bridge1 |<==>| PRR1| | > | | I | | | ----------- -------- | > | | D | | | | > | | G | | | ----------- ------- | > | | E | | |==>| Bridge2 |<==>| PRR2 || > | ----| | ----------- -------- | > | | | | > '-----------------------' '---------------------------------------------' Your spaces all seem too big, making this really hard to read. But really, we need to see some code before we can go further. "proposals" are great, but that's not how kernel development works, we need actual patches to be able to evaluate anything, as that shows you at least have a working implementation to start with, and that you have resolved any of the obvious issues ahead of time. thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel