Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1144559ybl; Wed, 8 Jan 2020 11:49:06 -0800 (PST) X-Google-Smtp-Source: APXvYqy0VLybJLygTTe0ZtG7HoLk8I/1QDvJYCtIcfXwjPOR2lpgVJaB1f5iC4TlWyAO81nqGCev X-Received: by 2002:aca:b608:: with SMTP id g8mr228817oif.142.1578512946812; Wed, 08 Jan 2020 11:49:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578512946; cv=none; d=google.com; s=arc-20160816; b=RseXVP6+f0aUX4er0Giy2laF2HUwuwMHB6iNLBNne/E0E9itNKtAvO0PdVUKqoUHGh nPSfOPsBn3Ema78FmLFQR5NTPR9Lc+mDw0wlUKHH0hWiv12cpV6DfAObNPqNNDkBJIHU gLz1MykMKypDoCNnAwj+fGm2Dp7UbTUWdew7cY0EEvKsVmR2gqaTHHLmwFSlJU4VDOe0 5BNSShbVeLSwjVDdwLD/3gWxvpVxthDO1REeUBAKObc6xuzj0iCdxQWMwQwxrUjbNpRa GCKtuiT03NqRVidNfapYIs7GmmouWl7+KEDOcvmWtX0B8K+Gno83Ggb/4xegxmSNJ9mB GqSg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=bHFjR8d1UYUJRl5AKmj24PoLYe+ucNsxv9xlg6vZtkw=; b=kg4hoS0ivVHGNS6y6/Pqb2QKATqSbKznIOCvhHJhnGJvDMSCLsh7bm+IfZKz7jTGVK ZeZkjs6uIPt/CQZ6Ls29EndB8GIVSb8mQSyvb4jycZwDwHjLNSL/OCh8yvluVtURuEOC BfJ3XebrcqnIMnXeYmbPAjzBDwPQcD7QJ8WQCYlpfX2TTDUdDtiIwDF7vQXuukcl3U5p gfSuSzi+u9pE0EK6T5zAsLefN2Pb0LZorqQBToefadG/0j1uRtq4pmQDe6j/gskCEE10 tHV6U0/3huQTdZ+14FX/za6N20oh+LfdVVuL0Knc1Dy/Hg9uIS2w57WPa0HbCuFSd31n 5LQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=lfNDBYTU; 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=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 c79si2378230oig.208.2020.01.08.11.48.55; Wed, 08 Jan 2020 11:49:06 -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=@ti.com header.s=ti-com-17Q1 header.b=lfNDBYTU; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730048AbgAHTkC (ORCPT + 99 others); Wed, 8 Jan 2020 14:40:02 -0500 Received: from lelv0142.ext.ti.com ([198.47.23.249]:34922 "EHLO lelv0142.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727247AbgAHTkC (ORCPT ); Wed, 8 Jan 2020 14:40:02 -0500 Received: from lelv0265.itg.ti.com ([10.180.67.224]) by lelv0142.ext.ti.com (8.15.2/8.15.2) with ESMTP id 008JdxrD131006; Wed, 8 Jan 2020 13:39:59 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1578512399; bh=bHFjR8d1UYUJRl5AKmj24PoLYe+ucNsxv9xlg6vZtkw=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=lfNDBYTUWZCoynFVmYZdJJpfmZEERQuQ4MEHQAgqzkMqN4Bif4MVA9cfD9HDbCuD0 kRifZPxCoBsc/jo2GoeW82MSUQuxFpXMERvfgENqDGR+YnwnCzt3EASmJHVXkEF/zF GKxduOGRzTm4lBGAOUGVv2mBeB2kndKOHFApPvt0= Received: from DFLE103.ent.ti.com (dfle103.ent.ti.com [10.64.6.24]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 008Jdx4Y020954 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 8 Jan 2020 13:39:59 -0600 Received: from DFLE111.ent.ti.com (10.64.6.32) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3; Wed, 8 Jan 2020 13:39:58 -0600 Received: from fllv0039.itg.ti.com (10.64.41.19) by DFLE111.ent.ti.com (10.64.6.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3 via Frontend Transport; Wed, 8 Jan 2020 13:39:58 -0600 Received: from [128.247.58.153] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 008JdwEG070338; Wed, 8 Jan 2020 13:39:58 -0600 Subject: Re: [PATCHv4 07/14] remoteproc/omap: Add support for DRA7xx remote processors To: Tero Kristo , , , CC: , , References: <20200102131845.12992-1-t-kristo@ti.com> <20200102131845.12992-8-t-kristo@ti.com> From: Suman Anna Message-ID: <7ff029a9-20bd-2fec-9bcf-f97cd1bd5f85@ti.com> Date: Wed, 8 Jan 2020 13:39:58 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20200102131845.12992-8-t-kristo@ti.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Tero, On 1/2/20 7:18 AM, Tero Kristo wrote: > From: Suman Anna > > DRA7xx/AM57xx SoCs have two IPU and up to two DSP processor subsystems > for offloading different computation algorithms. The IPU processor > subsystem contains dual-core ARM Cortex-M4 processors, and is very > similar to those on OMAP5. The DSP processor subsystem is based on > the TI's standard TMS320C66x DSP CorePac core. > > Support has been added to the OMAP remoteproc driver through new > DRA7xx specific compatibles for properly probing and booting all > the different processor subsystem instances on DRA7xx/AM57xx > SoCs - IPU1, IPU2, DSP1 & DSP2. A build dependency with SOC_DRA7XX > is added to enable the driver to be built in DRA7xx-only configuration. > > The DSP boot address programming needed enhancement for DRA7xx as the > boot register fields are different on DRA7 compared to OMAP4 and OMAP5 > SoCs. The register on DRA7xx contains additional fields within the > register and the boot address bit-field is right-shifted by 10 bits. > The internal memory parsing logic has also been updated to compute > the device addresses for the L2 RAM for DSP devices using relative > addressing logic, and to parse two additional RAMs at L1 level - L1P > and L1D. This allows the remoteproc driver to support loading into > these regions for a small subset of firmware images requiring as > such. The most common usage would be to use the L1 programmable > RAMs as L1 Caches. > > The firmware lookup logic also has to be adjusted for DRA7xx as > there are (can be) more than one instance of both the IPU and DSP > remote processors for the first time in OMAP4+ SoCs. > > Signed-off-by: Suman Anna > [t-kristo@ti.com: moved address translation quirks to pdata] > Signed-off-by: Tero Kristo > --- > v4: > - data format change due to device data changes to mem layout > > drivers/remoteproc/Kconfig | 2 +- > drivers/remoteproc/omap_remoteproc.c | 38 +++++++++++++++++++++++++++- > 2 files changed, 38 insertions(+), 2 deletions(-) > > diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig > index 94afdde4bc9f..d6450d7fcf92 100644 > --- a/drivers/remoteproc/Kconfig > +++ b/drivers/remoteproc/Kconfig > @@ -25,7 +25,7 @@ config IMX_REMOTEPROC > > config OMAP_REMOTEPROC > tristate "OMAP remoteproc support" > - depends on ARCH_OMAP4 || SOC_OMAP5 > + depends on ARCH_OMAP4 || SOC_OMAP5 || SOC_DRA7XX > depends on OMAP_IOMMU > select MAILBOX > select OMAP2PLUS_MBOX > diff --git a/drivers/remoteproc/omap_remoteproc.c b/drivers/remoteproc/omap_remoteproc.c > index 8a6dd742a8b1..9140c528c416 100644 > --- a/drivers/remoteproc/omap_remoteproc.c > +++ b/drivers/remoteproc/omap_remoteproc.c > @@ -34,10 +34,13 @@ > * struct omap_rproc_boot_data - boot data structure for the DSP omap rprocs > * @syscon: regmap handle for the system control configuration module > * @boot_reg: boot register offset within the @syscon regmap > + * @boot_reg_shift: bit-field shift required for the boot address value in > + * @boot_reg > */ > struct omap_rproc_boot_data { > struct regmap *syscon; > unsigned int boot_reg; > + unsigned int boot_reg_shift; > }; > > /** > @@ -159,6 +162,8 @@ static int omap_rproc_write_dsp_boot_addr(struct rproc *rproc) > struct omap_rproc *oproc = rproc->priv; > struct omap_rproc_boot_data *bdata = oproc->boot_data; > u32 offset = bdata->boot_reg; > + u32 value; > + u32 mask; > > if (rproc->bootaddr & (SZ_1K - 1)) { > dev_err(dev, "invalid boot address 0x%x, must be aligned on a 1KB boundary\n", > @@ -166,7 +171,10 @@ static int omap_rproc_write_dsp_boot_addr(struct rproc *rproc) > return -EINVAL; > } > > - regmap_write(bdata->syscon, offset, rproc->bootaddr); > + value = rproc->bootaddr >> bdata->boot_reg_shift; > + mask = ~(SZ_1K - 1) >> bdata->boot_reg_shift; > + > + regmap_update_bits(bdata->syscon, offset, mask, value); > > return 0; > } > @@ -296,6 +304,13 @@ static const struct omap_rproc_mem_data ipu_mems[] = { > { }, > }; > > +static const struct omap_rproc_mem_data dra7_dsp_mems[] = { > + { .name = "l2ram", .dev_addr = 0x800000 }, > + { .name = "l1pram", .dev_addr = 0xe00000 }, > + { .name = "l1dram", .dev_addr = 0xf00000 }, > + { }, > +}; > + > static const struct omap_rproc_dev_data omap4_dsp_dev_data = { > .device_name = "dsp", > }; > @@ -314,6 +329,16 @@ static const struct omap_rproc_dev_data omap5_ipu_dev_data = { > .mems = ipu_mems, > }; > > +static const struct omap_rproc_dev_data dra7_dsp_dev_data = { > + .device_name = "dsp", > + .mems = dra7_dsp_mems, > +}; > + > +static const struct omap_rproc_dev_data dra7_ipu_dev_data = { > + .device_name = "ipu", > + .mems = ipu_mems, > +}; > + > static const struct of_device_id omap_rproc_of_match[] = { > { > .compatible = "ti,omap4-dsp", > @@ -331,6 +356,14 @@ static const struct of_device_id omap_rproc_of_match[] = { > .compatible = "ti,omap5-ipu", > .data = &omap5_ipu_dev_data, > }, > + { > + .compatible = "ti,dra7-dsp", > + .data = &dra7_dsp_dev_data, > + }, > + { > + .compatible = "ti,dra7-ipu", > + .data = &dra7_ipu_dev_data, > + }, > { > /* end */ > }, > @@ -383,6 +416,9 @@ static int omap_rproc_get_boot_data(struct platform_device *pdev, > return -EINVAL; > } > > + of_property_read_u32(np, "ti,bootreg-shift", > + &oproc->boot_data->boot_reg_shift); Missing error checks, guess you will have to change this anyway when you address Rob's comments. regards Suman > + > return 0; > } > >