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 X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E761BC433E0 for ; Mon, 1 Jun 2020 17:51:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C449D206E2 for ; Mon, 1 Jun 2020 17:51:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="FPnJ+2iq" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727096AbgFARvm (ORCPT ); Mon, 1 Jun 2020 13:51:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35124 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726073AbgFARvl (ORCPT ); Mon, 1 Jun 2020 13:51:41 -0400 Received: from mail-pl1-x643.google.com (mail-pl1-x643.google.com [IPv6:2607:f8b0:4864:20::643]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6E4BEC08C5C0 for ; Mon, 1 Jun 2020 10:51:41 -0700 (PDT) Received: by mail-pl1-x643.google.com with SMTP id t7so261855plr.0 for ; Mon, 01 Jun 2020 10:51:41 -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=WlrUKklQ4wWdbnRY/ut1RE+n38DuD/sUC9c4AFrauXE=; b=FPnJ+2iquw+8js0IWILUf5shb1WdAiPhMfhoogI3ZHlWPUX2RdYAta2sliwALjQwFL CFzTVo1pTBwJnhOHFA2dZ3NARW6KzRdq8uRxgn79DZGw7hP4RwQZcst1Om6VcVPZR+1A mf60HQym79P7n0ZfkX4/C49gRg3IsjqcL2MfUNBz2sOXWI6cBob/k12FXm0S5192M2jn UdZ2JRqXAzuVuWzjwd4hGiZ/Db5NCQ2rUEprJgs00cdXWyUKrAadPmxzrNqZUo/mcrPR gfmh51A0Nka5JUh9RGFN0ZAaFDMEQslDMPevjJjr11LXU+hpph5bUBW2jhBQtDpxK5zD Jt8Q== 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=WlrUKklQ4wWdbnRY/ut1RE+n38DuD/sUC9c4AFrauXE=; b=UCseBZbue/6ap2AUtY3Yrr2SRNwIKHMh0brDQxdzYZ+RFm+EtRVFRf6B7J52sEAIN1 YA+A0z0wcoN6KAsBnbzTdrlUD0LGkYkJAfR7MTQ7kQc8lhCUX2zCXoBUvV3RwXeUXwHV CReE8YwJU/TwVRbG/LM+T2mjSTU0x4pgD4lv8aHpavCwTak2+DqRzsmDmCYywdfvsMOf H/skQPGNxjV+0ln+nfHHGKbTfZSd4Z7m0iRgCM+nroTI+A79t/WSX2i0W5z0RTBxThwh NWaTrlsd1ApRmKdnuhGj9XxRZRysD2LRIWi6cSvquWe/5AzSUyBPJtUuY2M4qWWVXlEG 07rQ== X-Gm-Message-State: AOAM532TkJ8PiE5H6grnY0sBJav3+mGVJX1NAmLmLCIvCL4NDkXAKJwl 1Rf+AiW6ceh57tTI+s9JLJ+5QZFgVPM= X-Google-Smtp-Source: ABdhPJzrmAlwErX9nfKyZG414r2Y+njbOGMCox8QTVlu/FwCy6ZPrMJHkVn6d1CJrGbUfkkgRPJ5Xg== X-Received: by 2002:a17:902:bb86:: with SMTP id m6mr20919601pls.341.1591033900861; Mon, 01 Jun 2020 10:51:40 -0700 (PDT) Received: from xps15.cg.shawcable.net (S0106002369de4dac.cg.shawcable.net. [68.147.8.254]) by smtp.gmail.com with ESMTPSA id k12sm58219pfg.177.2020.06.01.10.51.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 01 Jun 2020 10:51:40 -0700 (PDT) From: Mathieu Poirier To: bjorn.andersson@linaro.org, ohad@wizery.com Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, loic.pallardy@st.com, arnaud.pouliquen@st.com, s-anna@ti.com Subject: [PATCH v4 0/9] remoteproc: Add support for attaching with rproc Date: Mon, 1 Jun 2020 11:51:30 -0600 Message-Id: <20200601175139.22097-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 fourth iteration implements a solution that is fairly different from what was proposed in V3 and earlier versions. Three aspects have been revisited: 1) Only the scenario where the remoteproc core is attaching to the remote processor is implemented. Other scenarios where actions need to be taken when the remote processor is stopped or crashes will be considered in subsequent versions. 2) The introduction of a new RPROC_DETACHED state to be set by platform drivers when needing to attach to an already running remote processor. 3) New functions are introduced to replicate the functionality provided by rproc_fw_boot() and rproc_start(), minus operations related to firmware management. Enhancement to the documentation has been left out intentionally until it is agreed to move forward with this implementation. Applies cleanly on rproc-next(7dcef3988eed) and will be rebased on v5.8-rc1 when it comes out in two weeks. Thanks, Mathieu Mathieu Poirier (9): remoteproc: Add new RPROC_DETACHED state remoteproc: Add new attach() remoteproc operation remoteproc: Introducing function rproc_attach() remoteproc: Introducing function rproc_actuate() remoteproc: Introducing function rproc_validate() remoteproc: Refactor function rproc_boot() remoteproc: Refactor function rproc_trigger_auto_boot() remoteproc: Refactor function rproc_free_vring() remoteproc: Properly handle firmware name when attaching drivers/remoteproc/remoteproc_core.c | 226 +++++++++++++++++++++-- drivers/remoteproc/remoteproc_internal.h | 8 + drivers/remoteproc/remoteproc_sysfs.c | 17 +- include/linux/remoteproc.h | 9 +- 4 files changed, 243 insertions(+), 17 deletions(-) -- 2.20.1