Received: by 2002:ac0:e34a:0:0:0:0:0 with SMTP id g10csp858092imn; Tue, 26 Jul 2022 11:12:39 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vjisirgJZKXl1S4oDmhiwBQjywQZy5kTaYKBuuwY0O6APhOL0On7dnmws9DcKNUQyXrZv6 X-Received: by 2002:a17:907:97cd:b0:72f:2df:274f with SMTP id js13-20020a17090797cd00b0072f02df274fmr14601977ejc.766.1658859159187; Tue, 26 Jul 2022 11:12:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658859159; cv=none; d=google.com; s=arc-20160816; b=PS0ZxE5Ec7dH/UGpPrNi/RKo1D9+rSerVa1uOeiNcezSZCCqrx2eg4PeOQef+q/en/ uRZwsL9LTKKi1Diup8AU267Cts3AIojIkEwJn79uCcJRZu0BjsR8vpJ5bDHzeJ5QKlWw IwCBZNu/MwoX8/cxYUTo2F7s1byHdxdf9O/yNyCZ0lqrHgm/Ye+C1UAIZ9iQ0KDN7a1d zevRZOMRU76nMX8tQOPOiNOK8NgSCARgJKTJoymCLC9TNE3zUs1zlsUCd7EBFL4N9CsB vvn8Cpb2DnMdR/Yg594dCSestgXswQOmbtykwVCUmfz6miQ3d5Ad9W9x2A8x7mmZvHBZ LM8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=F+HDDqObfng+U02lfgXmn7OnwfgF8WXJW/VqBzOllp0=; b=ZO8kDvSmnpQL3XJJzAus8gH7VLdzA9SF/cI/txZpUgTuxL/PcOtwW9/EmXCGG5p7Oa lR2CHnLQI7xqa7ypSoLbxJv0MSw0VGg0OeGsr7wZEaw2fBBrc/zMmmPRiZSZlqrWCDCU JamQx/DjEoKyZkuOP9X4IyaRghcDibmu0vChWpl1D/qREUlKQUlqZfoUK20OWThpWzC4 Cs2AHAq3NM34ue8cxza2ehgwWuW3DLs9GJkMS8kO2N6ZfdwguBfnibIb4ex6DG8hMkNQ H4WkOVq05C8LQfAKTwO6Zbydpq8ld7RiLjMaVEUzGseY8F8Beg8MOl7OZ3rZvgHdPFkY pYqQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="a6C/xNGk"; 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=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id n12-20020aa7c68c000000b004356df8591csi1111728edq.373.2022.07.26.11.12.14; Tue, 26 Jul 2022 11:12:39 -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=@linaro.org header.s=google header.b="a6C/xNGk"; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239861AbiGZRws (ORCPT + 99 others); Tue, 26 Jul 2022 13:52:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44896 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239789AbiGZRwT (ORCPT ); Tue, 26 Jul 2022 13:52:19 -0400 Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E6B3A30F7D for ; Tue, 26 Jul 2022 10:51:21 -0700 (PDT) Received: by mail-pl1-x633.google.com with SMTP id c13so7292716pla.6 for ; Tue, 26 Jul 2022 10:51:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=F+HDDqObfng+U02lfgXmn7OnwfgF8WXJW/VqBzOllp0=; b=a6C/xNGkJ/tlLE0z3lbgDiMjtLnG5+Pk8v16J19Ed/b/HkF9kRw3644iZJI3sVXXck K3unqotJOeqeBY1NWvUL99rUbwAEe2NSwXyXfqZneH2ZKVcfSeOjISAgzCC9BNWZ4Vp7 kAGl8zXGFWT0O8NqB88HQboq76Vwk5/sZehKLY2wxOUgEVDp7Eo3v2fvf4EgTVQ03c4A WDTxcq7JmkkWldjlEBbX3TdMeuI0HZr/gSl4uCbcXlZ/4CMsSryEleWhwBPADIHZoXyE +rIJe5O4oaHfAFT/JN2b7wz3cJeEiJ1JFIxx3+SMH0oQ4UT9nuXcZF5HDFTICDn8LS7X dIzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=F+HDDqObfng+U02lfgXmn7OnwfgF8WXJW/VqBzOllp0=; b=TTFghhp4V18gHHAex8L7E5U65c1dyINZqUbAb4Hvh/uobYUSJ9SLw/N056zpqMUzvo 36VgEDQ/nJlxdFrJl2n1Vl3ZU0HX5JR5lpDOmpAvLapzJVTpDRp2yZ+qwXigp/efbK/Q iqXw3mI8zsQoR8Zr0gcvq6+jjuh0MJ50p8j6TsfmDtFVc5ZRhMONpvt870gpn9d7CLIZ RP1sjGSwA4vxA7Lqfpi99s977nSQ1GAwBxWAkH96jlhbS8e26LYLV/D7bmNMzoOX99KG Rsf20HfayPRt//bSrmvWlNFHfhC/xQMXuv5nSbjXy/tsqybuS+CxnPbbbiiBZwJrPPYG o4XQ== X-Gm-Message-State: AJIora9QSOZNcJlUeg6KHQIBV/OMeZfmvNERgqi9RDIb44OYeMorQc8w fdYlPFWljoz8lmj+EtbY4P+hRQ== X-Received: by 2002:a17:903:20e:b0:16d:4d0b:5408 with SMTP id r14-20020a170903020e00b0016d4d0b5408mr17552661plh.161.1658857881433; Tue, 26 Jul 2022 10:51:21 -0700 (PDT) Received: from p14s (S0106889e681aac74.cg.shawcable.net. [68.147.0.187]) by smtp.gmail.com with ESMTPSA id n1-20020a170902d2c100b0016a565f3f34sm12010223plc.168.2022.07.26.10.51.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Jul 2022 10:51:20 -0700 (PDT) Date: Tue, 26 Jul 2022 11:51:18 -0600 From: Mathieu Poirier To: Chris Lew Cc: bjorn.andersson@linaro.org, linux-remoteproc@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/4] Introduction of rpmsg_rx_done Message-ID: <20220726175118.GA113917@p14s> References: <1654651005-15475-1-git-send-email-quic_clew@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1654651005-15475-1-git-send-email-quic_clew@quicinc.com> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS 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 On Tue, Jun 07, 2022 at 06:16:41PM -0700, Chris Lew wrote: > This series proposes an implementation for the rpmsg framework to do > deferred cleanup of buffers provided in the rx callback. The current > implementation assumes that the client is done with the buffer after > returning from the rx callback. > > In some cases where the data size is large, the client may want to > avoid copying the data in the rx callback for later processing. This > series proposes two new facilities for signaling that they want to > hold on to a buffer after the rx callback. > They are: > - New API rpmsg_rx_done() to tell the rpmsg framework the client is > done with the buffer > - New return codes for the rx callback to signal that the client will > hold onto a buffer and later call rpmsg_rx_done() > > This series implements the qcom_glink_native backend for these new > facilities. > > Chris Lew (4): > rpmsg: core: Add rx done hooks > rpmsg: char: Add support to use rpmsg_rx_done > rpmsg: glink: Try to send rx done in irq > rpmsg: glink: Add support for rpmsg_rx_done > > drivers/rpmsg/qcom_glink_native.c | 112 ++++++++++++++++++++++++++++++-------- > drivers/rpmsg/rpmsg_char.c | 50 ++++++++++++++++- > drivers/rpmsg/rpmsg_core.c | 20 +++++++ > drivers/rpmsg/rpmsg_internal.h | 1 + > include/linux/rpmsg.h | 24 ++++++++ > 5 files changed, 183 insertions(+), 24 deletions(-) I have started reviewing this set. Comments to come later today or tomorrow. Thanks, Mathieu > > -- > 2.7.4 >