Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp3851334pxb; Tue, 19 Apr 2022 11:04:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJynYU4x7pHrbfv7hWo//vvwMzxF+mI4rWz7xC7xt2f35qJa/YNVVGwTZaKqkV06zCHMjPyb X-Received: by 2002:a05:6402:1cc1:b0:413:2b12:fc49 with SMTP id ds1-20020a0564021cc100b004132b12fc49mr18716344edb.118.1650391474467; Tue, 19 Apr 2022 11:04:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650391474; cv=none; d=google.com; s=arc-20160816; b=vdOA4Ntg5N8XksK8NcbarAY0c3hC2tfy2vHoQ9lizY1AXQRkQxSPvfv8z/7KueMvrc U7h+2nFKGFxKBKLkgeUodPCXs5qjEZ5uicfNuH3+y5WUcSSu4oUGj2sZ0Dp7mF3hbf1f KZsieFD3M+91+6gIqKg2tDmXMA55j4GpLgZRBP1kiUt5JwayPNcNOT17LDnRVyj7lmea 39yExSt8LC4A+KuCyCQA12kwDv2WpHntpLshIC685K/MuYza7oeG6AM/Ph/cidi3CS2+ 02yCZsYlsepe/qslPXO7vl5cpTXOK+O8SmoykWyrjqDsizndm2vSIFI58RY+ZaKYotoc XlaQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=ofGijNZFu4Zd/+sgz6duGn2Sru1g8U7plurzUXGM6dU=; b=KZxdfB9Syavd/pTWexZBRu3rzEcyvMWE29eVzqEZwi5b7iSrLCAr/Kj19ufqXlE5RU NpT5bdbDZ2KBtxPI7lGiosLh4lNi3yRBcqPfTxKRh1XwKCNh99SsEhHhqqRG6satKLHP z0bffnwfrU2G5yKjTDIhEp+qAA7Cu5pds8TG7cjAZP3QsK/YyjsRjXMyCQHXfJmyDkvy VSQ3CNvQSbo4BjAGOYEVAwU17uDMu3l90BZb02fEGNPXO9YBVPYjjOg6TkY05OAxhdmG a3JSFfoM3uu+RqzRrc6dp7nMmtZWsb3gCoGhpcXijDpcwneDNRAFyV2hOkcDH5kiFATW 0qKQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=P8tIoI7o; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bl17-20020a170906c25100b006e8af78c647si6855ejb.48.2022.04.19.11.04.08; Tue, 19 Apr 2022 11:04:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=P8tIoI7o; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231962AbiDRWks (ORCPT + 99 others); Mon, 18 Apr 2022 18:40:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52004 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229773AbiDRWkq (ORCPT ); Mon, 18 Apr 2022 18:40:46 -0400 Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2848722B21 for ; Mon, 18 Apr 2022 15:38:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650321485; x=1681857485; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=Rb4iwrLbDmyNKMaNz8Nmx1r9e7WMKNOBMr3G2Jjx3bc=; b=P8tIoI7o6JX+e32xq43VzT8ly79Gr2rHH1AK6Vf2VEFZO1KAoitLvznY /HTkRvCfOii0nFohIn6s0HsyvtPp6gWtkdnz53fv/HUwh/zyUSX0xuMfU 4w4sFKzBs3+RJre5NoGZEeS8bKklLNxxksrEh41VEzWV+1R+T9t2V6xm5 OXWMxXJ1NvxcUXwNVkUSfPH8PC9izrYcO3d+HnwmxAhWryoYnfEZKhzmc hjt3dGnUAhXahEsFnwGjVy7Unuz7xr/5H8Rd5E2mPi1odKMVLHNIDH0cK lYCBmixI/ZQM3dHNFsnBxm7tlC7un1R/+KpFVxkPRhJ6qhhQU6r19qZSC A==; X-IronPort-AV: E=McAfee;i="6400,9594,10321"; a="243557433" X-IronPort-AV: E=Sophos;i="5.90,271,1643702400"; d="scan'208";a="243557433" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Apr 2022 15:38:04 -0700 X-IronPort-AV: E=Sophos;i="5.90,271,1643702400"; d="scan'208";a="509907075" Received: from rhweight-mobl.amr.corp.intel.com (HELO rhweight-mobl.ra.intel.com) ([10.209.35.137]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Apr 2022 15:38:04 -0700 From: Russ Weight To: mcgrof@kernel.org, rafael@kernel.org, linux-kernel@vger.kernel.org Cc: trix@redhat.com, lgoncalv@redhat.com, yilun.xu@intel.com, hao.wu@intel.com, matthew.gerlach@linux.intel.com, basheer.ahmed.muddebihal@intel.com, tianfei.zhang@intel.com, Russ Weight Subject: [PATCH v3 0/8] Extend FW framework for user FW uploads Date: Mon, 18 Apr 2022 15:37:45 -0700 Message-Id: <20220418223753.639058-1-russell.h.weight@intel.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Extend the firmware loader subsystem to support a persistent sysfs interface that userspace may use to initiate a firmware update. For example, FPGA based PCIe cards automatically load firmware and FPGA images from local FLASH when the card boots. The images in FLASH may be updated with new images that are uploaded by the user. A device driver may call firmware_upload_register() to expose persistent "loading" and "data" sysfs files at /sys/class/firmare//*. These files are used in the same way as the fallback sysfs "loading" and "data" files. However, when 0 is written to "loading" to complete the write of firmware data, the data is also transferred to the lower-level driver using pre-registered call-back functions. The data transfer is done in the context of a kernel worker thread. Additional sysfs nodes are added in the same location as "loading" and "data" to monitor the transfer of the image data to the device using callback functions provided by the lower-level device driver and to allow the data transfer to be cancelled. Example usage: $ pwd /sys/class/firmware/secure-update.1 $ ls cancel device loading remaining_size subsystem data error power status uevent $ echo 1 > loading $ cat /tmp/firmware.bin > data $ echo 0 > loading $ while :; do cat status; cat remaining_size ; sleep 3; done preparing 44590080 <--snip--> transferring 44459008 transferring 44311552 <--snip--> transferring 173056 <--snip--> programming 0 <--snip--> idle 0 ^C $ cat error The first two patches in this set make minor changes to enable the fw_priv data structure and the sysfs interfaces to be used multiple times during the existence of the device driver instance. The third patch is mostly a reorganization of existing code in preparation for sharing common code with the firmware-upload support. The fourth and fifth patches provide the code for user-initiated firmware uploads. The final 3 patches extend selftest support to test firmware-upload functionality. Changelog v2 -> v3: - Added Reviewed-by tag - Added kdoc support for enum fw_upload_prog progress codes Changelog v1 -> v2: - Rebased to 5.18-rc2. - It was discovered that the new function in v1, fw_state_is_done(), is equivalent to the existing fw_sysfs_done() function. Renamed fw_sysfs_done() and fw_sysfs_loading() to fw_state_is_done() and fw_state_is_loading() respectively, and placed them along side companion functions in drivers/base/firmware_loader/firmware.h. - Removed the "if !fw_sysfs_done(fw_priv))" condition in switch case 1 of firmware_loading_store(). It is rendered unnecessary by other changes to the function. - Updated documentation Date and KernelVersion fields to July 2022 and 5.19. - Unconditionally set fw_priv->is_paged_buf to true in firmware_upload_register(); Changelog RFC -> v1: - Renamed files fw_sysfs.c and fw_sysfs.h to sysfs.c and sysfs.h - Moved "MODULE_IMPORT_NS(FIRMWARE_LOADER_PRIVATE);" from sysfs.c to sysfs.h to address an error identified by the kernel test robot - renamed fw_upload_register() and fw_upload_unregister() to firmware_upload_register() and fw_upload_unregister(). - Moved ifdef'd section of code out of firmware_loading_store() in sysfs.c into a new function, fw_upload_start(), in sysfs_upload.c. - Changed #defines to enums for error codes and progress states - Added additional kernel-doc supported symbols into the documentation. Some rewording in documentation as well. - Added module reference counting for the parent module in the firmware_upload_register() and firmware_upload_unregister() functions to fix problems found when testing with test_firmware module. - Removed unnecessary module reference counting for THIS_MODULE. - Added a new patch to modify the test_firmware module to support testing of the firmware upload mechanism. - Added a new patch to modify the test_firmware module to support error injection for firmware upload. - Added a new patch to extend the existing firmware selftests to cover firmware upload. Russ Weight (8): firmware_loader: Clear data and size in fw_free_paged_buf firmware_loader: Check fw_state_is_done in loading_store firmware_loader: Split sysfs support from fallback firmware_loader: Add firmware-upload support firmware_loader: Add sysfs nodes to monitor fw_upload test_firmware: Add test support for firmware upload test_firmware: Error injection for firmware upload selftests: firmware: Add firmware upload selftests .../ABI/testing/sysfs-class-firmware | 77 ++++ .../driver-api/firmware/fw_upload.rst | 126 +++++ Documentation/driver-api/firmware/index.rst | 1 + drivers/base/firmware_loader/Kconfig | 18 + drivers/base/firmware_loader/Makefile | 2 + drivers/base/firmware_loader/fallback.c | 430 ------------------ drivers/base/firmware_loader/fallback.h | 46 +- drivers/base/firmware_loader/firmware.h | 16 + drivers/base/firmware_loader/main.c | 18 +- drivers/base/firmware_loader/sysfs.c | 423 +++++++++++++++++ drivers/base/firmware_loader/sysfs.h | 100 ++++ drivers/base/firmware_loader/sysfs_upload.c | 397 ++++++++++++++++ drivers/base/firmware_loader/sysfs_upload.h | 54 +++ include/linux/firmware.h | 82 ++++ lib/test_firmware.c | 378 +++++++++++++++ tools/testing/selftests/firmware/Makefile | 2 +- tools/testing/selftests/firmware/config | 1 + tools/testing/selftests/firmware/fw_lib.sh | 7 + .../selftests/firmware/fw_run_tests.sh | 4 + tools/testing/selftests/firmware/fw_upload.sh | 214 +++++++++ 20 files changed, 1910 insertions(+), 486 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-class-firmware create mode 100644 Documentation/driver-api/firmware/fw_upload.rst create mode 100644 drivers/base/firmware_loader/sysfs.c create mode 100644 drivers/base/firmware_loader/sysfs.h create mode 100644 drivers/base/firmware_loader/sysfs_upload.c create mode 100644 drivers/base/firmware_loader/sysfs_upload.h create mode 100755 tools/testing/selftests/firmware/fw_upload.sh -- 2.25.1