From patchwork Mon Oct 28 12:42:30 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Tero Kristo X-Patchwork-Id: 177916 Delivered-To: patch@linaro.org Received: by 2002:a92:409a:0:0:0:0:0 with SMTP id d26csp3339289ill; Mon, 28 Oct 2019 05:43:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqxvlNTl2HP0Eh/lSuIblHPPJdwCETrJB4Q2YXrkS45IlMUcF+Vp7MjYTJM0HE405CgYqYKN X-Received: by 2002:a50:9269:: with SMTP id j38mr19129533eda.5.1572266596137; Mon, 28 Oct 2019 05:43:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572266596; cv=none; d=google.com; s=arc-20160816; b=iFN1qJqgZhJp1osVKaZx3MXebCP/ghuJDwuhOxhUt9dpxJ8VxoQr3vHDdP4+Enawtm wSFnrZD6i7CPghCfjI4COZP+9E/mMulNh3S+qO3/l+cZ8d7CmJCSvXKnLT1dsAoZxf+4 maHmnoEJoRmdl4OfpDBsZipTLr87k4VViSryZVOkG7GbQ2U+d9wSHwMLwsmi8g9dkgGf /a/SUzi5enSfbqdIXAZFMeAQqIF3AMsrf+siyNpgBb5FahmdUD4sJlK81O1CIyXizq2w 0JT2ioM17u7cWLMSY9QdnKCfCyMZJrq8hLrINQio099CX2m0AmlBNPZG1rxEhpvaJa4R Li3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:dkim-signature; bh=+vxhIXyc/GT5P7zxyphEpVcZECI2GZVgNs5s8U8O+pQ=; b=kEtPPg/9MBwXCH3+bCM05RrpmWxdsjhfbV7mipPNCkHIf2hlhC3XYZZdHat3GSmNQs woUhPzuaKQV1KQOPiV4bos326dKErmMTxF7eL7DLUHtrGo8DsftmSNhEbZH0DC+BA4GT d7eqoN+Dn1Z8B94c8VpDYnCkTfWG0HwB/ufjd2RIT8TEMEqfvQeKmkSGI8eoAEB/bY/r PQy6jlpBB312GF3Cw9Rw0aPR0tKrscVKYLmISIiIlr0MZ/OfzIP+2Iu5Hy1WI3KhkLaW T92lyQOZStn5OGKsTA9U7BqZkprVJKYozcjC+kXyZMsRM+v4kHa2kZwTEbpIesxGj9qD r6HQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=u0Qzlixe; spf=pass (google.com: best guess record for domain of linux-omap-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-omap-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id ce3si625614edb.441.2019.10.28.05.43.15; Mon, 28 Oct 2019 05:43:16 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-omap-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=@ti.com header.s=ti-com-17Q1 header.b=u0Qzlixe; spf=pass (google.com: best guess record for domain of linux-omap-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-omap-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389347AbfJ1MnO (ORCPT + 5 others); Mon, 28 Oct 2019 08:43:14 -0400 Received: from lelv0143.ext.ti.com ([198.47.23.248]:54500 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389339AbfJ1MnO (ORCPT ); Mon, 28 Oct 2019 08:43:14 -0400 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id x9SChC52067164; Mon, 28 Oct 2019 07:43:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1572266593; bh=+vxhIXyc/GT5P7zxyphEpVcZECI2GZVgNs5s8U8O+pQ=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=u0QzlixeDwNvypkxpLzvPQj+vw0UwhdJv1lvJ87HrOQ7rePOORO0j9yiSQznNsJOg iN5aenQeznZuxbUzuZgGGg+7PdfqpNtxE0GTqOhr/XgOTVeh4wqOd+Yw2hz/XC2LfF HVpZsE+yz+L7H0dJkxTxZIeGmGN1Zn2qszC4vrw4= Received: from DLEE104.ent.ti.com (dlee104.ent.ti.com [157.170.170.34]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x9SChCIi040394 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 28 Oct 2019 07:43:12 -0500 Received: from DLEE114.ent.ti.com (157.170.170.25) by DLEE104.ent.ti.com (157.170.170.34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Mon, 28 Oct 2019 07:43:00 -0500 Received: from fllv0040.itg.ti.com (10.64.41.20) by DLEE114.ent.ti.com (157.170.170.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Mon, 28 Oct 2019 07:43:00 -0500 Received: from sokoban.ti.com (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id x9SCgoh1063574; Mon, 28 Oct 2019 07:43:10 -0500 From: Tero Kristo To: , , CC: , , , Tero Kristo Subject: [PATCH 09/17] remoteproc/omap: Remove the unused fields from platform data Date: Mon, 28 Oct 2019 14:42:30 +0200 Message-ID: <20191028124238.19224-10-t-kristo@ti.com> X-Mailer: git-send-email 2.17.1 In-Reply-To: <20191028124238.19224-1-t-kristo@ti.com> References: <20191028124238.19224-1-t-kristo@ti.com> MIME-Version: 1.0 X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-omap-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-omap@vger.kernel.org From: Suman Anna The following fields: .name, .oh_name, .oh_name_opt, .mbox_name, .firmware, .ops and .set_bootaddr, are removed from the platform data, as these are no longer needed after the addition of DT support to the OMAP remoteproc driver. The .name field was used to give a name to the remoteproc, and this is replaced with the device name. The .ops field was never used by the OMAP remoteproc driver. The .mbox_name was used to define the sub-mailbox node used for communication with the remote processor, and is retrieved using the 'mboxes' property in the DT node. The .firmware field is encoded directly in the OMAP remoteproc driver and is retrieved using driver match data. The .set_bootaddr ops was used for using a OMAP Control Module API to configure the boot address for the processor, and is now implemented within the driver using a syscon property. The .oh_name field is used to define the primary hwmod for the processor node, and is represented using the 'ti,hwmods' property in the DT node. The .oh_name_opt field was primarily defined to identify the hwmod for the second cpu in a dual Cortex-M3/M4 IPU processor sub-system. This hwmod entry is no longer defined usually, but rather a single hwmod representing both the processors in the IPU sub-system is defined. A single firmware image (either in SMP-mode or a combined image for non-SMP mode) is used, with both the resets released together always as part of the device management. Any power management and recovery aspects require that both the processors be managed as one entity due to the presence of shared MMU and unicache within the IPU sub-system. The OMAP remoteproc platform data structure is eventually expected to be removed completely once the other dependencies with the mach-omap layer are met. Signed-off-by: Suman Anna Signed-off-by: Tero Kristo --- include/linux/platform_data/remoteproc-omap.h | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) -- 2.17.1 -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki Reviewed-by: Bjorn Andersson diff --git a/include/linux/platform_data/remoteproc-omap.h b/include/linux/platform_data/remoteproc-omap.h index 7e3a16097672..6bea01e199fe 100644 --- a/include/linux/platform_data/remoteproc-omap.h +++ b/include/linux/platform_data/remoteproc-omap.h @@ -2,38 +2,23 @@ /* * Remote Processor - omap-specific bits * - * Copyright (C) 2011 Texas Instruments, Inc. + * Copyright (C) 2011-2018 Texas Instruments Incorporated - http://www.ti.com/ * Copyright (C) 2011 Google, Inc. */ #ifndef _PLAT_REMOTEPROC_H #define _PLAT_REMOTEPROC_H -struct rproc_ops; struct platform_device; /* * struct omap_rproc_pdata - omap remoteproc's platform data - * @name: the remoteproc's name - * @oh_name: omap hwmod device - * @oh_name_opt: optional, secondary omap hwmod device - * @firmware: name of firmware file to load - * @mbox_name: name of omap mailbox device to use with this rproc - * @ops: start/stop rproc handlers * @device_enable: omap-specific handler for enabling a device * @device_shutdown: omap-specific handler for shutting down a device - * @set_bootaddr: omap-specific handler for setting the rproc boot address */ struct omap_rproc_pdata { - const char *name; - const char *oh_name; - const char *oh_name_opt; - const char *firmware; - const char *mbox_name; - const struct rproc_ops *ops; int (*device_enable)(struct platform_device *pdev); int (*device_shutdown)(struct platform_device *pdev); - void (*set_bootaddr)(u32); }; #if defined(CONFIG_OMAP_REMOTEPROC) || defined(CONFIG_OMAP_REMOTEPROC_MODULE)