Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp167766ybc; Mon, 11 Nov 2019 22:47:02 -0800 (PST) X-Google-Smtp-Source: APXvYqyCjjT/te6zBi0Sq+GLuBptCxc4wM4si9vDzwc9DyI05DgYakZaxeIe6LBzEshUcxsmZ7SL X-Received: by 2002:a50:9908:: with SMTP id k8mr30537698edb.75.1573541222369; Mon, 11 Nov 2019 22:47:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573541222; cv=none; d=google.com; s=arc-20160816; b=NdLV2OnZN1nTOz+x93VOVG2pRVX5YOvAKxJXFKfSKu81JeabxgZ/yB91aQSC+nEKDF bIRjOAFJZeb6QoMrCP3B8ZC1TZzMlbZRnKwpKsCMBH522zgUEIGYCdENeKEZwGP6y5tB 6yiMwRAVNQESwICrCEGJluxLmYsKpxDSgtyCcOvUzBmmLY63EE4xj0+sEfGO/I3dKe3o QOwOtO4BHOm1Va5WoYLJfxbAJb3z1OBist7RJ/a5H9QI4SXfAn1PYjdL1q44+nn7vf6r KZfQ5w785yrBbnO1LS1R2FB3W3EGRPBNG8NAfNRzW1a+xFLCIArVvjC2oGnMGPTGQTE7 Vxaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=6gu94hk6ViXZU/1pF57c89Mz0JcKl1j3IzzPZmTPjtQ=; b=kQgBrT6aB2HNAeASLUF3mMPYfpPcdgQXPKouRcGxbH5QmwFUM/QG7yns9Y+j45OZP8 FZwWXDE4iN/kEwKFBrsV/TM3op6WkyMz+6yuTyHGnm2ZhYR/MsZsNG8cop682cNoGBRi O+JaI7TTLxFzA+d4xGQ81YtBuW44iBk4HOKto3sxdheOArVsg5IYkix8KlJZ4tUfY69D 1HtF/AIKtCnb2QIcnfRijOoZQYn/3jbmhmGDtit4Hok7ikNl9ZsK3n6pqdxgWMMo9k5V E05JMt/iJKD2uXrPvfwFjLFqfhtNBsH8uvRZvl/2mywFXeYA0NevCvTg4wbsDi3iFrHH dpsg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=LDDUyvLA; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r3si15524144edb.245.2019.11.11.22.46.38; Mon, 11 Nov 2019 22:47:02 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=LDDUyvLA; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726188AbfKLGnZ (ORCPT + 99 others); Tue, 12 Nov 2019 01:43:25 -0500 Received: from mail-ed1-f67.google.com ([209.85.208.67]:36294 "EHLO mail-ed1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725821AbfKLGnZ (ORCPT ); Tue, 12 Nov 2019 01:43:25 -0500 Received: by mail-ed1-f67.google.com with SMTP id f7so14022640edq.3 for ; Mon, 11 Nov 2019 22:43:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6gu94hk6ViXZU/1pF57c89Mz0JcKl1j3IzzPZmTPjtQ=; b=LDDUyvLAAr/FgJFV0ODv1fscc3tceNs7i1JvEsFi9SbeCOxeMyJWafdRgYIlNqWV49 ro79eCq++su+3IaTvSt6MwgL4SEwWPUZp7cEzIY5lMEh0+Vi4K+fFmiFNMR56+eI/hDL YUlIauWUKVBysNq/DieSbYjanJaQapqZXiAkA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6gu94hk6ViXZU/1pF57c89Mz0JcKl1j3IzzPZmTPjtQ=; b=qlxty6EFibUHNPx2vw7D7zR+Z1Lqs8ya8q1pBjycW1x+ZymhboYvoB0rUrbjv0vY+z MuqG4DUJ1dPxQ22Mex6rTka+hF4UJimzaWJgUFOEy4lKPoha+4tk/k0e16SgI+jWUI9S anguF3iaRV253FRFQJGc0nGToeHuhlHY9MesquFzjrVKS6ubwemukrrRS6vyVt14Ep1M hJyRPTUih3WLdPbISmNG3+mJSmRbDAip07yTo5+e38Xkhhd9gVV88RKCC1QX/4PyvQUw n0V3NybxCQWfnBrmBAiviBJusCGdFI4dhX4Tv2nXRceFKkzv1AN6AlNJKHSmwwZEFrew Po2Q== X-Gm-Message-State: APjAAAXcXoA0wEyWZfQiF3fb0Mifa5PcpRbk6JX0C+k3sHLuXfMM2bY8 Ho8YVm4O5GrlffwNx7hdepQC6a5tT0/h7iYngKSh8A== X-Received: by 2002:a17:906:1d19:: with SMTP id n25mr25947734ejh.151.1573541003705; Mon, 11 Nov 2019 22:43:23 -0800 (PST) MIME-Version: 1.0 References: <20191014075812.181942-1-pihsun@chromium.org> <20191014075812.181942-4-pihsun@chromium.org> <20191111231023.GD3108315@builder> In-Reply-To: <20191111231023.GD3108315@builder> From: Pi-Hsun Shih Date: Tue, 12 Nov 2019 14:42:47 +0800 Message-ID: Subject: Re: [PATCH v20 3/4] rpmsg: add rpmsg support for mt8183 SCP. To: Bjorn Andersson Cc: Ohad Ben-Cohen , Matthias Brugger , open list , "open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM" , "moderated list:ARM/Mediatek SoC support" , "moderated list:ARM/Mediatek SoC support" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Thanks for the review, I'll address them in the next version. Some inline comment below. On Tue, Nov 12, 2019 at 7:10 AM Bjorn Andersson wrote: > > On Mon 14 Oct 00:58 PDT 2019, Pi-Hsun Shih wrote: > > > Add a simple rpmsg support for mt8183 SCP, that use IPI / IPC directly. > > > > Hi Pi-Hsun, > > Sorry for not reviewing this in a timely manner! This looks good, just > some very minor comments below. > > > Signed-off-by: Pi-Hsun Shih > [..] > > diff --git a/drivers/remoteproc/mtk_scp.c b/drivers/remoteproc/mtk_scp.c > > index f2e5e70a58f2..7896cefb2dc0 100644 > > --- a/drivers/remoteproc/mtk_scp.c > > +++ b/drivers/remoteproc/mtk_scp.c > > @@ -15,6 +15,7 @@ > > #include > > #include > > #include > > +#include > > > > #include "mtk_common.h" > > #include "remoteproc_internal.h" > > @@ -407,6 +408,31 @@ static void scp_unmap_memory_region(struct mtk_scp *scp) > > of_reserved_mem_device_release(scp->dev); > > } > > > > +static struct mtk_rpmsg_info mtk_scp_rpmsg_info = { > > + .send_ipi = scp_ipi_send, > > + .register_ipi = scp_ipi_register, > > + .unregister_ipi = scp_ipi_unregister, > > These are exported symbols, so unless you see a need to support > alternative implementations in the near future just skip the function > pointers and call them directly. > Yes there is request from MTK that they do want to reuse the mtk_rpmsg driver for things other than mtk_scp, so there's a need to support alternative implementations for this. > > + struct rpmsg_device *rpdev, rpmsg_rx_cb_t cb, void *priv, > > + u32 id) > > +{ > > Regards, > Bjorn Regards, Pi-Hsun