Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp4557013imj; Tue, 12 Feb 2019 19:16:42 -0800 (PST) X-Google-Smtp-Source: AHgI3IaV+f7c87/0RN6Wfye2oZS/Lq2OSpEeVtqZR0zsydfDJ8k7NphVfDab3IGwLZiA6ENieH6m X-Received: by 2002:a62:569b:: with SMTP id h27mr7194720pfj.163.1550027802527; Tue, 12 Feb 2019 19:16:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550027802; cv=none; d=google.com; s=arc-20160816; b=z6bE/E0vjlBz3Tvfouholb3seX8Fpi6TKedPIKcpxOIGMLD5M4Ebx4q8bNC7WXeiGp +XJyAq01ILXcE0eJyT5TkfjnHNkslw4+NzFOBnTGFOR8nvr3d0eemcf3WW+3xVVe+GPF v2eIyaXGUFkHZ9zlDAQOxhtBZ7yu9CdmOOHMbH1HadBWl21fVrpOq+bZbjvA0UVanq+K bSa9sp//LI7AtuiCWYMXRv1sMYPrai+mZk3ZQ7tOkHgrIQI7LMiVSIUcbYjQY6Utn2TU oj4XKwf2YjvbNB12uVP2iLPs77SngNJDpOgK5jYaySSD18M8lI/yKmXbeGq7BMXdkno2 TKBw== 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=xGLmxX5ZZsqNrzRqmlY+znpV0Tv4SjK3drY64f4I7RQ=; b=bG8pUXZcoMbs8OA2OVVaw14MwvYKTeUrJjQZlirNFB1+niHPBJ/mckcMUQCvgsJAlh kkVnfxe+JiOGS/ZBd2sAjc3aGAhesmjUpHdCh3LoUMi6aD5w4UVvgMoJOI3r0Zcgrb1z t6V7VGvcaL9vGdfiOdSzlBeHTJ5gjq7v5ySrJp535ta1LUReG/eLS9oGXu1YGMLV7HET gQ+43g8BnKxykXQJIVOXneGS9HTxTD38/Oo42r4i49xaufnU6HFMqRIFEFeUNJkCdo3t PPeui6kenIex8XG5K0OeLr+IezT4f95gklGWPJD0c05NoDYJGRa+0wBSiTrvD3DT1ewx KRqA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=NdjRV2Ak; 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 i90si4096211pli.135.2019.02.12.19.16.26; Tue, 12 Feb 2019 19:16:42 -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=NdjRV2Ak; 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 S1732465AbfBMDQU (ORCPT + 99 others); Tue, 12 Feb 2019 22:16:20 -0500 Received: from mail-ed1-f68.google.com ([209.85.208.68]:36854 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728626AbfBMDQU (ORCPT ); Tue, 12 Feb 2019 22:16:20 -0500 Received: by mail-ed1-f68.google.com with SMTP id o59so687299edb.3 for ; Tue, 12 Feb 2019 19:16:18 -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=xGLmxX5ZZsqNrzRqmlY+znpV0Tv4SjK3drY64f4I7RQ=; b=NdjRV2AkBoCYs4CMtMmZD1P7f5lG91kzbO5Lpi23lRhde68jxHuElkaSkE5xJpRTou zD/pFfZAkm07OoViak8OAXUqPabC5YldpllHiV1sEqSD0YAY3uxpWwcjpYKqmCJ57j8a ObxWXA8lpCxg0x5Qmu+6dBRFnTK/btn/sannI= 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=xGLmxX5ZZsqNrzRqmlY+znpV0Tv4SjK3drY64f4I7RQ=; b=T0O0xbBzYX50N/ZqPKluneG5k5eqslqfUwezGUi0WJ5RAj8w0d6J2ZzwRQfTWV4fAl wdA18zFh1muvhKB+/bjC49q4hTbk26xxWZ2k4bnmIza9OhHcGLLpotjHFoxtX8EwE2oT Vi7IGRn8xUMbDMioa9iBy4vPcqMGRwTxwFtzsmDBaTYk/IRKqZ9NQ7jcYCkWcEtkb5Xr JW/qCwXahzojRu9oUl/skN4DPxmGTZZbXyxUyFSBHNHNG9J2rGxqCo2vPOKcYyFFCqUH vJobJ01t0tc8EOiQv/8msqtD2gEjlc7E+98PUubZJxUszedKeZHLFIx1Trd1yaTdWjuW aLpg== X-Gm-Message-State: AHQUAuaXvTUOE0M1IkwcZ0LGxtl/Vt0JfWqjw2NMWAMCd5ZA0X6et5B3 YkmVFWG3iXbO2Sdw+6u59v0fRC3SKOXCnXfr5NC/iA== X-Received: by 2002:a17:906:5501:: with SMTP id r1mr4927214ejp.167.1550027777901; Tue, 12 Feb 2019 19:16:17 -0800 (PST) MIME-Version: 1.0 References: <20190131093131.245531-1-pihsun@chromium.org> <20190131093131.245531-3-pihsun@chromium.org> <20190202001749.GT81583@google.com> In-Reply-To: From: Pi-Hsun Shih Date: Wed, 13 Feb 2019 11:16:07 +0800 Message-ID: Subject: Re: [PATCH v4 2/6] remoteproc/mediatek: add SCP support for mt8183 To: Matthias Brugger Cc: Matthias Kaehlcke , Erin Lo , Nicolas Boichat , Ohad Ben-Cohen , Bjorn Andersson , 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 On Tue, Feb 5, 2019 at 2:02 AM Matthias Brugger wrote: > > > > On 02/02/2019 01:17, Matthias Kaehlcke wrote: > > Hi Pi-Hsun, > > > > a few comments inline. > > > > It's the first time I dabble into remoteproc, I don't claim to have a > > complete understanding of the driver at this point ;-) > > > > On Thu, Jan 31, 2019 at 05:31:27PM +0800, Pi-Hsun Shih wrote: > >> From: Erin Lo > >> > >> Provide a basic driver to control Cortex M4 co-processor > >> > >> Signed-off-by: Erin Lo > >> Signed-off-by: Nicolas Boichat > >> --- > >> Changes from v3: > >> - Fix some issue found by checkpatch. > >> - Make writes aligned in scp_ipi_send. > >> > >> Changes from v2: > >> - Squash patch 3 from v2 (separate the ipi interface) into this patch. > >> - Remove unused name argument from scp_ipi_register. > >> - Add scp_ipi_unregister for proper cleanup. > >> - Move IPI ids in sync with firmware. > >> - Add mb() in proper place, and correctly clear the run->signaled. > >> > >> Changes from v1: > >> - Extract functions and rename variables in mtk_scp.c. > >> --- > >> drivers/remoteproc/Kconfig | 9 + > >> drivers/remoteproc/Makefile | 1 + > >> drivers/remoteproc/mtk_common.h | 73 +++++ > >> drivers/remoteproc/mtk_scp.c | 441 ++++++++++++++++++++++++++ > >> drivers/remoteproc/mtk_scp_ipi.c | 157 +++++++++ > >> include/linux/platform_data/mtk_scp.h | 135 ++++++++ > >> 6 files changed, 816 insertions(+) > >> create mode 100644 drivers/remoteproc/mtk_common.h > >> create mode 100644 drivers/remoteproc/mtk_scp.c > >> create mode 100644 drivers/remoteproc/mtk_scp_ipi.c > >> create mode 100644 include/linux/platform_data/mtk_scp.h > >> > >> diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig > >> index f0abd260804473..ee0bda23768938 100644 > >> --- a/drivers/remoteproc/Kconfig > >> +++ b/drivers/remoteproc/Kconfig > >> @@ -22,6 +22,15 @@ config IMX_REMOTEPROC > >> > >> It's safe to say N here. > >> > >> +config MTK_SCP > >> + tristate "Mediatek SCP support" > >> + depends on ARCH_MEDIATEK > >> + help > >> + Say y here to support Mediatek's SCP (Cortex M4 > >> + on MT8183) via the remote processor framework. > > > > It would be good to spell out SCP somewhere, e.g. > > > > "... support Mediatek's system control processor (SCP) via ..." > > > > the example is less important IMO, though it's prefectly fine if you > > can still squeeze it in ;-) > > > > In which way is this different from > drivers/soc/mediatek/mtk-scpsys.c ? > > Regards, > Matthias (the other one ;) drivers/remoteprocs/mtk_scp.c is for SCP (System Companion Processor) on MTK's platform, and drivers/soc/mediatek/mtk-scpsys.c is for SCPSYS (System Control Processor System). Despite the similar name, they're not relevant.