Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp988299ybz; Wed, 22 Apr 2020 11:29:45 -0700 (PDT) X-Google-Smtp-Source: APiQypIkPYY3cpsXyCUZ3eqI0LzmwpnFT2cBVBoOYjE+R+LhEAyiC08X71b9BdEGgiqyNRCtMu2G X-Received: by 2002:a17:906:4810:: with SMTP id w16mr26415520ejq.226.1587580185314; Wed, 22 Apr 2020 11:29:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587580185; cv=none; d=google.com; s=arc-20160816; b=wMSKqIrD0VC8k6mMpIzFag9rU/RTeIbZl+7bGCVH2fBr+Hk4R8WPfmHJaVovzlfDGz dVKcwJMxTDWp+uPWgd9xvar1LPsbDy4BKQVXAKqfESfoRppjbSsFNlHu2CSus/O7y9ru UnNKSSO6a6/Xz6WTuHyB/tT77d55GSrOrp8BecQ2/nhoaN3+qKVL2NAMEyqfdEm2KQa6 z8nRAo7/9yXzk1wictyszjJGhRE9Yn7ULpzsLoyHxUBnpJsfpGegtUKh2ClFws6nrmoE rP/b29RFruUQ8hKaZJZpkB6SMzJjpIPdo8mX6BSbK+U5eM8HZDfszU7k+6AiGLq+I78t Guqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=fxIemATZr+Jj72Sq0gv/Y8Y0CxRoIaNtcDCWp0Bqo4s=; b=KTlzVrI/0vablTlLEt93nPkWabGVf6U/Lk2eCkhCfV6yKohBU5DuNzFN5nfmYU1f3v dLK0h2xMbYoP5yvRFl/7Mj5QRBuIIdcqlKlaICU/mNimDBfex/EE0bMKefcQHQYbxec+ idhumYX/68itKUXFbcNZmSey8TP72gI39TsUKpXgc4Xi/na834E8An3UOZkXfy/GGRJI n78raeXD7LP7XlOqRPcz6PSN3MkY+HVGlsbjKaP4pjr3meMC3IXNY/rMuULnn3tzX8UU 7B6ZnZUlWRdVw2MJq0Ym1pgkdoxzRM8oSBfj5DnEphM6akEq7fQFyQDDola7vIZ871Jk gERA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=E1A4uzto; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b5si4287390edq.191.2020.04.22.11.29.12; Wed, 22 Apr 2020 11:29:45 -0700 (PDT) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=E1A4uzto; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726416AbgDVSY6 (ORCPT + 99 others); Wed, 22 Apr 2020 14:24:58 -0400 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:30010 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725839AbgDVSY5 (ORCPT ); Wed, 22 Apr 2020 14:24:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587579895; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fxIemATZr+Jj72Sq0gv/Y8Y0CxRoIaNtcDCWp0Bqo4s=; b=E1A4uzto6IDptQIgb2dILXCDEK6LFQP8DQis91yb2A/2zgbNiX+zXFhiaBf6Z+0p56K6Mx moqHUDE0W3j8lqNgwZYOrOE87oYNy2tBgd5oRWoOpJLovANW7CIFobcG8+MT+s+7+PBgp7 eGcwDn+nNH/aVrmxqSQcUUREm4npxYw= Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-290-QyZ91bRwNKa0CgADZWcj6Q-1; Wed, 22 Apr 2020 14:24:52 -0400 X-MC-Unique: QyZ91bRwNKa0CgADZWcj6Q-1 Received: by mail-qk1-f197.google.com with SMTP id k138so3808499qke.15 for ; Wed, 22 Apr 2020 11:24:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=fxIemATZr+Jj72Sq0gv/Y8Y0CxRoIaNtcDCWp0Bqo4s=; b=ml572qIMUmAjYreJOaKjvJCoT4ZaE+WUh4oQDd2gGnNePz7xrpZEvfRPc1x6U9B2SV VV7i+BpsHa6J6MI8J2iCKPR1DG3OsHHAK5D8QJbuHaEtZ2s+B0HFy+vBZ97DgtmYNFsO JO8rkZVrO82pZGti8mTeplRV8htMaAe3TgVPmCfU8KzZOifpJEkOTEM9FuyoMoleNsAx BIN7sf3G/OjyhCJ+a660WRRAXjoqpXJGx7dRJi3k+cfZEWyDoLYKA20HnvA7dIOny/Dc wY98IS2AX+QI4rzCNH6njc8Unp6tQluQDaTlTNHD4D/sbamm739JzS+Viw3S9vJJgdXM WdKw== X-Gm-Message-State: AGi0PuZ0oQEhebrZWl5YWwj1TLpPang1Lb7NCPidLndaRWEI5A9qsdfL Swtn+nK/o0BXaWJ0wMaBvr5LnlfJBVQBipSQ+qk4NgRjvF6E1toEs9suWC+YsZuywXU/v9cL3Yd UxTlIwuFjVu0iD8l+GvhW48W1 X-Received: by 2002:aed:2d27:: with SMTP id h36mr27910773qtd.228.1587579891960; Wed, 22 Apr 2020 11:24:51 -0700 (PDT) X-Received: by 2002:aed:2d27:: with SMTP id h36mr27910724qtd.228.1587579891410; Wed, 22 Apr 2020 11:24:51 -0700 (PDT) Received: from trix.remote.csb ([75.142.250.213]) by smtp.gmail.com with ESMTPSA id o22sm4509050qtm.90.2020.04.22.11.24.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Apr 2020 11:24:50 -0700 (PDT) Subject: Re: How to upload fpga firmware To: Sascha Hauer , linux-fpga@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Moritz Fischer References: <20200422114432.GM1694@pengutronix.de> From: Tom Rix Message-ID: Date: Wed, 22 Apr 2020 11:24:49 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20200422114432.GM1694@pengutronix.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I believe you need to use OPAE, user level interface to the kernel. Here is a good starting point. https://opae.github.io/latest/docs/fpga_tools/fpgaconf/fpgaconf.html Tom On 4/22/20 4:44 AM, Sascha Hauer wrote: > Hi, > > I wonder what can be done with the mainline state of drivers/fpga/. The > entry to the framework seems to be fpga_mgr_load(). The only user of > this function is fpga_region_program_fpga(). This in turn is only called > in response of applying a device tree overlay. A device tree overlay is > applied with of_overlay_fdt_apply() which has no users in the Kernel. > > My current task is to load a firmware to a FPGA. The code all seems to > be there in the Kernel, it only lacks a way to trigger it. I am not very > interested in device tree overlays since the FPGA appears as a PCI > device (although applying a dtbo could enable the PCIe controller device > tree node). Is there some mainline way to upload FPGA firmware? At the > moment we are using the attached patch to trigger loading the firmware > from userspace. Would something like this be acceptable for mainline? > > Sascha > > ---------------------------8<---------------------------------- > > From 71a5ea845dd673d4011391f9e57fdaf427767ed5 Mon Sep 17 00:00:00 2001 > From: Ahmad Fatoum > Date: Tue, 2 Oct 2018 17:13:40 +0200 > Subject: [PATCH] fpga: region: Add sysfs attribute for loading firmware > > Signed-off-by: Ahmad Fatoum > --- > drivers/fpga/fpga-region.c | 50 +++++++++++++++++++++++++++++++++++++- > 1 file changed, 49 insertions(+), 1 deletion(-) > > diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c > index bde5a9d460c5..ca6dc830fadf 100644 > --- a/drivers/fpga/fpga-region.c > +++ b/drivers/fpga/fpga-region.c > @@ -5,6 +5,7 @@ > * Copyright (C) 2013-2016 Altera Corporation > * Copyright (C) 2017 Intel Corporation > */ > +#include > #include > #include > #include > @@ -170,11 +171,58 @@ static ssize_t compat_id_show(struct device *dev, > (unsigned long long)region->compat_id->id_h, > (unsigned long long)region->compat_id->id_l); > } > - > static DEVICE_ATTR_RO(compat_id); > > +static ssize_t firmware_name_show(struct device *dev, > + struct device_attribute *attr, > + char *buf) > +{ > + struct fpga_region *region = to_fpga_region(dev); > + > + if (!region->info || !region->info->firmware_name) > + return 0; > + > + return sprintf(buf, "%s\n", region->info->firmware_name); > +} > + > +static ssize_t firmware_name_store(struct device *dev, > + struct device_attribute *attr, > + const char *firmware_name, size_t count) > +{ > + struct fpga_region *region = to_fpga_region(dev); > + struct fpga_image_info *info = region->info; > + int error; > + > + if (!info) { > + info = fpga_image_info_alloc(dev); > + if (!info) > + return -ENOMEM; > + } else if (info->firmware_name) { > + devm_kfree(dev, info->firmware_name); > + } > + > + info->firmware_name = devm_kstrdup(dev, firmware_name, GFP_KERNEL); > + if (!info->firmware_name) > + return -ENOMEM; > + > + if (count > 0 && info->firmware_name[count - 1] == '\n') > + info->firmware_name[count - 1] = '\0'; > + > + region->info = info; > + error = fpga_region_program_fpga(region); > + if (error) { > + devm_kfree(dev, info->firmware_name); > + info->firmware_name = NULL; > + } > + > + return error ? error : count; > +} > + > +static DEVICE_ATTR_RW(firmware_name); > + > static struct attribute *fpga_region_attrs[] = { > &dev_attr_compat_id.attr, > + &dev_attr_firmware_name.attr, > NULL, > }; > ATTRIBUTE_GROUPS(fpga_region);