Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp129215ybz; Fri, 24 Apr 2020 13:03:33 -0700 (PDT) X-Google-Smtp-Source: APiQypIpMN+6hgzJ7afqWAM6+MYfcOF+VahiHL6/BoCJh7LZC+FDIr1nqCaVUiWbWzBeCK7l4hd7 X-Received: by 2002:a17:906:3502:: with SMTP id r2mr8401215eja.67.1587758612842; Fri, 24 Apr 2020 13:03:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587758612; cv=none; d=google.com; s=arc-20160816; b=SWtRgPSZ9o7aLkQA+gbyoYRF+buXNgYTl6JeZtqON389lEtQAHQ3epadO1vHM3bNyE nJMwvTfMOGimHVHKIBX41k5rjmdQjbhIdp3WaWIl5jPM81fACB2ix/GoOKRLJjjAeIk9 wCPTtqqP0YyUgYJk4+WYPvDxCLavC2StF+Pbi92ZPMs8Sd2LjcACumMr3ycM05U+QG/2 JFJXHkT+57jS7h5u4IBD046+JSLau0GkHbuaVVa1ufy+82F7JfB7PHwsLohOsHoH33Pj GAev9p8lA2BEB8LNhFzq8ZPAKWh95+YtJCLIpueicWklUKSB/e8HnXuhXOvru4VpF6x8 JodQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=d4lr59kGFtiMrlzsTXv7Cap04Be+amSXDo3Nxu+OOcI=; b=mPzooZiFx8TO5cTGOfGRGAppAsh69gtUvH3JaAUNIWidKIyw5SV+5M6QqZ8lQj/1+A EDBAsuxhcUMsTQlqUcmjVH7OaHHJz+JRaz/zvK2l5Nnt2n80pjX4jcVgbc2dtqrzOPBn eZHBKyD/s8CKQh4DZaz0ARrcH4YzKpMhUVWnSxcOEEP8WbpJD3od6+vVNZ0nX5jMWJU5 AE/e0d9jUyxbBYvNt25wtjaPiwrYcdou5OzQ2xneELP5ZZ9XUH2zd6kNHKH6TFibsyy6 NzklhGKEbc6phZCryKyARpsEPOWzgKXTq+jxRZSXMucnLgzQSyWlM0pfb2+wDS0sSNr0 A2yQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=vvhLTHmA; 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=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id cw22si3612973edb.418.2020.04.24.13.03.01; Fri, 24 Apr 2020 13:03:32 -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=@linaro.org header.s=google header.b=vvhLTHmA; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727021AbgDXUBi (ORCPT + 99 others); Fri, 24 Apr 2020 16:01:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39226 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725970AbgDXUBi (ORCPT ); Fri, 24 Apr 2020 16:01:38 -0400 Received: from mail-pj1-x1044.google.com (mail-pj1-x1044.google.com [IPv6:2607:f8b0:4864:20::1044]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 03B93C09B048 for ; Fri, 24 Apr 2020 13:01:37 -0700 (PDT) Received: by mail-pj1-x1044.google.com with SMTP id mq3so4306623pjb.1 for ; Fri, 24 Apr 2020 13:01:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=d4lr59kGFtiMrlzsTXv7Cap04Be+amSXDo3Nxu+OOcI=; b=vvhLTHmAX7oCwPA3JTybbFNPIyIJXpmAdyxRXLqIO00QVc/Qidha5keDn8/QfKpkcM b8PACjozzS0KNo9x+oWJGBBfsJR/OB+yMax+49l+waXRh9XwI1XaOh4aryRA5trrALrP a498acMlafLtVyY5g9SmRj4GB/o8m8SWZ86kfyCEmm1PrGTLkWnnEiYCKN8Q6gvj6dqc KzKPkefMxBfrKL4CHY+vpQfKHFylosj+ee7xzjrAuodLyhllwry6De1bUu4EkNTGZL9A /eBmJ9GsfRv+ELnvdOoSETh1D2fhxq+fUF2QGI+Z4RQ4aL+YdlZ5IwwLKdoCQDvRj7hk 6j6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=d4lr59kGFtiMrlzsTXv7Cap04Be+amSXDo3Nxu+OOcI=; b=Kb2u5OCFki524X8GTJh9T1bk9Nx2jww2lreVblIZL5k7w7d5uWCFoKl+vcuigYH3jE qwser/voLmU6/eydSIkBoZQGC1sA3YQRqM/k2igTyPb1TspK0UkeR3tzUDozw13CCx3x lM8GWOaZeeBNp5XGTujuS8fDpNSFwYu+g6yePYCrhfkYo6olZ0qs/6w7fQdl32PcYCOw Uc2PcjHAlr/ogEQLG8B4LduFbeIxYlbSsA8MEofbcTBCRRxXlW+dosNak4yqGh41tpoE ALO7JbBfQ0eSyFh6G7kp7y4ah5YDUsZyY5NQCpxV4Q+IbOOo+/ph3i4CaGiEURXHG4A7 SCFg== X-Gm-Message-State: AGi0PuYW3NaWDaLRV4cgtvdrq9vRq2edtCv970kzaE75neZTdo3vJ2Js R8RYvekXVOUnZNmcu/dxyKCUXw== X-Received: by 2002:a17:902:7082:: with SMTP id z2mr11055219plk.43.1587758497295; Fri, 24 Apr 2020 13:01:37 -0700 (PDT) Received: from xps15.cg.shawcable.net (S0106002369de4dac.cg.shawcable.net. [68.147.8.254]) by smtp.gmail.com with ESMTPSA id o11sm5532224pgd.58.2020.04.24.13.01.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Apr 2020 13:01:36 -0700 (PDT) From: Mathieu Poirier To: bjorn.andersson@linaro.org, ohad@wizery.com Cc: loic.pallardy@st.com, arnaud.pouliquen@st.com, s-anna@ti.com, linux-remoteproc@vger.kernel.org, corbet@lwn.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 00/14] remoteproc: Add support for synchronisaton with rproc Date: Fri, 24 Apr 2020 14:01:21 -0600 Message-Id: <20200424200135.28825-1-mathieu.poirier@linaro.org> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This is the third revision of this series that tries to address the problem of synchronising with a remote processor with as much flexibility as possible. Two things to pay attention to: 1) Function rproc_actuate() has been abandoned to avoid creating another way to start a remote processor from a kernel driver. Arnaud expressed the opinion that it is semantically questionnable to synchronise with a remote processor when calling rproc_boot(). We could rename rproc_boot() to rproc_actuate() but I'll wait to see what other people think before doing so. 2) The allocation of the synchronisation states has been split from the remote processor allocation. A new function rproc_set_state_machine() does all the work now. Proceeding this way has made the patchset a lot more simple. Other than the above I have tried to address all the comments made on the second revision. If a comment was not addressed it simply fell through the cracks rather than ignored. In such a case please reiterate your point of view and I'll be sure to address it. Applies cleanly on rproc-next (305ac5a766b1). Best regards, Mathieu Mathieu Poirier (14): remoteproc: Make core operations optional remoteproc: Introduce function rproc_alloc_internals() remoteproc: Add new operation and flags for synchronistation remoteproc: Refactor function rproc_boot() remoteproc: Refactor function rproc_fw_boot() remoteproc: Refactor function rproc_trigger_auto_boot() remoteproc: Introducting new start and stop functions remoteproc: Call core functions based on synchronisation flag remoteproc: Deal with synchronisation when crashing remoteproc: Deal with synchronisation when shutting down remoteproc: Deal with synchronisation when changing FW image remoteproc: Introducing function rproc_set_state_machine() remoteproc: Document function rproc_set_state_machine() remoteproc: Expose synchronisation flags via debugfs Documentation/remoteproc.txt | 17 ++ drivers/remoteproc/remoteproc_core.c | 197 +++++++++++++++++++---- drivers/remoteproc/remoteproc_debugfs.c | 21 +++ drivers/remoteproc/remoteproc_internal.h | 123 +++++++++++++- drivers/remoteproc/remoteproc_sysfs.c | 24 ++- include/linux/remoteproc.h | 27 ++++ 6 files changed, 372 insertions(+), 37 deletions(-) -- 2.20.1