Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5368972yba; Tue, 30 Apr 2019 13:38:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqx/TarGxadmoFz50H0R4eOUOvp12IY97Na+zIWOYzsVkXlzohHhc+KcOQUvx/2wZNLRoaOY X-Received: by 2002:a63:f212:: with SMTP id v18mr64316313pgh.231.1556656737316; Tue, 30 Apr 2019 13:38:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556656737; cv=none; d=google.com; s=arc-20160816; b=RI72pkKCJek4GLZmZpDYYU72GH7D/1dt6YgoZA9Xke6O2g8FdSVV+YmvZiMi6zOCKT 9ooVGfTHhw/rYPl+5adF4WxkJS4BbJ/qyhEOlhpjOx+0ynmOYLaFAiQYpAIOTrk10GiG TStGV8VYNr5zBzdTL9a54v5ZeogM4eHjMQmf5uC1a7YLzWe35aEeS46u+rlSPJ9HQGkk HKK/yavBewYCF/TvnH6lrT0TZo2T0YHmYu0TAsqwzI2hpyDOt+7MkA0F02g7Lho1EFmU nz93r/grwWudHKEal28TuFTWMfvOk7jpJlYATK3uLJID4jBm63ZQblUH1kygT9dsaeUx LTlg== 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=clcChE8883UqIXxGTreiImUbJ17Khq2OVjfHdN2fnQc=; b=D8OmvP11teGRWTHzhxjecXsrcB5E+bcwbA5HnmwD2RjLocvX7FrfRn//459y42U9dc oO2DQDocLzFaC0ez+SkTicdcSYcqB9IW5wWj0WI3w4TII9AaPmo/AGEr4U62JAP4pUEP cZoXnbTnv3CBX4nCnEGrVpXAdyCNgAWP5J+lpSb7CciuXVa2hRc7O4hprutcs0TZGOvW dmatd5Vdr0P7GqKpJSVAsDc1lL/jRFI/TpqdIC3gbnXxG7j426SNjhEHet7ZBSqGDse6 E6fbukzCZkW640Ll7CwtgrXGN0pEB9doYoWKHS7mDZE7cvb9xagd/LYDr66QkP8GnHiJ E6og== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=D0l93wFA; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c24si40204474plo.220.2019.04.30.13.38.41; Tue, 30 Apr 2019 13:38:57 -0700 (PDT) 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=@kernel.org header.s=default header.b=D0l93wFA; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726945AbfD3Uhj (ORCPT + 99 others); Tue, 30 Apr 2019 16:37:39 -0400 Received: from mail.kernel.org ([198.145.29.99]:39076 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726326AbfD3Uhj (ORCPT ); Tue, 30 Apr 2019 16:37:39 -0400 Received: from mail-qt1-f179.google.com (mail-qt1-f179.google.com [209.85.160.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5E0D2217D4; Tue, 30 Apr 2019 20:37:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1556656657; bh=ZEkaWl3bqlpN5zzBHSyjdUuA6td/ImB+VcUu5ceXrrg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=D0l93wFAe+/YN05cfhvTTgYM2RMcBCdm1owCHx5HUWwwPu3jqbGwSdgpwwQg/sRS2 bigpXK1w2fl6yGiGYF6RN3GzyJhfpfNjJVx2I32Fz06iXjnzMgKLm6V/Og61HScmDf g7Za+xaTyAU2Tcrxm1vsdglqnMepM1F9Las23Yqs= Received: by mail-qt1-f179.google.com with SMTP id y49so12219056qta.7; Tue, 30 Apr 2019 13:37:37 -0700 (PDT) X-Gm-Message-State: APjAAAX8xF3ARN+4CEqTaynsEc0bIRE4ZLcM2SL+l/d8w0266iNvxjda NaRFviknidxHD1T+GcypmPOUUr+MaGPLR331dQ== X-Received: by 2002:ac8:610f:: with SMTP id a15mr47505444qtm.257.1556656656572; Tue, 30 Apr 2019 13:37:36 -0700 (PDT) MIME-Version: 1.0 References: <1555426699-5340-1-git-send-email-fabien.dessenne@st.com> <1555426699-5340-3-git-send-email-fabien.dessenne@st.com> <20190430004051.GA7391@bogus> In-Reply-To: From: Rob Herring Date: Tue, 30 Apr 2019 15:37:25 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/8] dt-bindings: remoteproc: add bindings for stm32 remote processor driver To: Fabien DESSENNE Cc: Mark Rutland , Maxime Coquelin , Alexandre TORGUE , Ohad Ben-Cohen , Bjorn Andersson , "devicetree@vger.kernel.org" , "linux-stm32@st-md-mailman.stormreply.com" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "linux-remoteproc@vger.kernel.org" , Loic PALLARDY , Arnaud POULIQUEN , Ludovic BARRE , Benjamin GAIGNARD 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, Apr 30, 2019 at 9:15 AM Fabien DESSENNE wrote: > > Hi Rob, > > > On 30/04/2019 2:40 AM, Rob Herring wrote: > > On Tue, Apr 16, 2019 at 04:58:13PM +0200, Fabien Dessenne wrote: > >> Add the device tree bindings document for the stm32 remoteproc devices. > >> > >> Signed-off-by: Fabien Dessenne > >> --- > >> .../devicetree/bindings/remoteproc/stm32-rproc.txt | 64 ++++++++++++++++++++++ > >> 1 file changed, 64 insertions(+) > >> create mode 100644 Documentation/devicetree/bindings/remoteproc/stm32-rproc.txt > >> > >> diff --git a/Documentation/devicetree/bindings/remoteproc/stm32-rproc.txt b/Documentation/devicetree/bindings/remoteproc/stm32-rproc.txt > >> new file mode 100644 > >> index 0000000..430132c > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/remoteproc/stm32-rproc.txt > >> @@ -0,0 +1,64 @@ > >> +STMicroelectronics STM32 Remoteproc > >> +----------------------------------- > >> +This document defines the binding for the remoteproc component that loads and > >> +boots firmwares on the ST32MP family chipset. > >> + > >> +Required properties: > >> +- compatible: Must be "st,stm32mp1-m4" > >> +- reg: Address ranges of the remote processor dedicated memories. > >> + The parent node should provide an appropriate ranges property > >> + for properly translating these into bus addresses. > > dma-ranges, but that's independent of 'reg'. > > > > It needs to list how many reg regions and what they are. > > The "reg" property needs to be removed since it is not used by the > driver : the "memory-region" property (defined below) provides with all > the needed memory information. I'm not sure that's the right direction. reserved-memory nodes generally should be in the range of system memory (i.e. what /memory nodes define). > Unfortunately, when I remove this "reg" property from the DeviceTree, I > have this warning when building (W=123) the DTB: > > "Warning (avoid_unnecessary_addr_size): /mlahb: unnecessary > #address-cells/#size-cells without "ranges" or child "reg" property" > > IMHO, there is something wrong in the dtc script which seems to ignore > the "dma-ranges" property that needs to have #address-cells/#size-cells > defined. Just like "ranges". Perhaps. > > The quick patch below (add check for "dma-ranges" ) in > scripts/dtc/checks.c solves this issue. > > static void check_avoid_unnecessary_addr_size(struct check *c, struct > dt_info *dti, > struct node *node) > { > ... > if (get_property(node, "ranges") || get_property(node, > "dma-ranges") || !node->children) > return; > ... > > Can you confirm that I can remove the "reg" property and ignore the warning? That should cause another warning because the 'simple-bus' checks expect to have nodes with addresses as 'simple-bus' means MMIO bus. That may have been the check which was broken for a while and I just fixed not too long ago. Rob