This makes sense, but can't we implement attribute_group->is_visible to The default > behavior is to allow the sysfs operations as before.
#FCEUGX 3.4.0 BOOT.ELF DRIVERS#
> Add support to deny the sysfs state/firmware/recovery change by > introducing a state flag 'deny_sysfs_ops' that the individual > remoteproc drivers can set based on their usage needs. Also, not all remoteproc drivers may want to > support the sysfs interfaces by default. > These interfaces can adversely affect a remoteproc and its clients > especially when a remoteproc is being controlled by a remoteproc > client driver(s). These interfaces are currently > allowed irrespective of how the remoteprocs were booted (like > remoteproc self auto-boot, remoteproc client-driven boot etc). The 'recovery' > sysfs file can also be used similarly to control the error recovery > state machine of a remoteproc. > The remoteproc framework provides sysfs interfaces for changing > the firmware name and for starting/stopping a remote processor > through the sysfs files 'state' and 'firmware'. V2: revised to account for the 'recovery' sysfs file as well, patchījorn Andersson Nov. The defaultīehavior is to allow the sysfs operations as before. Remoteproc drivers can set based on their usage needs. Introducing a state flag 'deny_sysfs_ops' that the individual Also, not all remoteproc drivers may want toĪdd support to deny the sysfs state/firmware/recovery change by These interfaces can adversely affect a remoteproc and its clientsĮspecially when a remoteproc is being controlled by a remoteprocĬlient driver(s). Remoteproc self auto-boot, remoteproc client-driven boot etc). These interfaces are currentlyĪllowed irrespective of how the remoteprocs were booted (like Sysfs file can also be used similarly to control the error recovery Through the sysfs files 'state' and 'firmware'. The firmware name and for starting/stopping a remote processor
The remoteproc framework provides sysfs interfaces for changing Subject: remoteproc: Introduce deny_sysfs_ops flag Received: from localhost ()īy .com (8.14.7/8.14.7) with ESMTP id (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL) MEoKytFEBXH64ai8JApLvpaTOXndTo9ORGocMOs4=
+tviOeX/3dnyBSKwLsqhK6rmttpuzlfodLBoQdPnCM6UKKYlhCGssWYgYqfldg4圓S H=From:To:CC:Subject:Date:In-Reply-To:References ī=Lqj+7k291l4uOnCc3kVwF8kQYBHb0BW5o8eF8kGAj9iRLYLA9cz/1vUohnuLBztDk Received: from .com (:50548 "EHLOį.com" rhost-flags-OK-OK-OK-OK) by Received: from ( )īy (Postfix) with ESMTP id 5C7A4223FDĭkim=pass (1024-bit key) header.d=ti.com header.b="Lqj+7k29" Received: from ( )īy (Postfix) with ESMTP id 98197C64E75 URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, X-Spam-Status: No, score=-18.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH,ĭKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, X-Spam-Checker-Version: SpamAssassin 3.4.0 () onĪ
0 kommentar(er)
