Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp27419img; Wed, 27 Mar 2019 16:08:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqx9klw8yTmaZ81TAgehcHbuoH/UIM9w1wCj5a8no9AwUHz2zXRD139k0M2ttOej/7QCNfhi X-Received: by 2002:a65:6283:: with SMTP id f3mr37624437pgv.108.1553728101643; Wed, 27 Mar 2019 16:08:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553728101; cv=none; d=google.com; s=arc-20160816; b=0T1wkn0yFx85VRfox2tkSH5QwoMISLuS4T5j0jh+wiWb7jpmAgSLSxU10TJVNHcGDk 8+bF2SC/fiOv1ZIRf2pVrjppSn2P+8/UpuPb2u9rII1/XG/Wv0WR4zfiqwOnimb9zGs2 0jN+96VPsz/d14hRskqMjKJuUjhAGiH72DH0cVRpOthg5sOvyjH3J+VGaKOkQghwpjCV cJa0V8i2V02QBgmmCPaXx+olsuIcua4DezADPz2JUGaYO6vfjoPWH/sQQflMpw7zayME pfiQNaTo1fW8RLShLD+HoIym0SYnQJ67heg6uGIpVcdlQ47VztbvqH05hBIaxi1F+Tzc bWGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=WOIvTZkyBewSM9hPCcfz1BOCmh+9VTusdQO/GI6NhU4=; b=uL8F0FrPFUpC23Y+Gvvq3N7wc0ibf3rlJuKEx2peHRpMFvs88Haa36izjmfdKFqw/y IbpqYU5XWXjrLwE0tOznrsu3DgJawrztHnUZMVFPFWsfvPPWQk54WKFk78IjjgYBCkdQ rTy4eG8Dg+5ms8I5T+X/2oWoe3WmJF5da8FR6uxfihfilfi7ax5O6h3/X5lv+NDXpHvF U4PGCbELZu6x0v7f1VSWsD/CYKDsPhA5WPvAgcLiPdnjipp9RL928E8frXMyUfPfzxoH Qa3PKsunVGvI88woMZSYH/gXCAyNK+33p7lO3rTtoxxoxE7YbKgcABlichEv39Frl6BG I5Bg== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (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 k6si20649551pla.409.2019.03.27.16.08.04; Wed, 27 Mar 2019 16:08:21 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728120AbfC0XHZ (ORCPT + 99 others); Wed, 27 Mar 2019 19:07:25 -0400 Received: from mail-ot1-f68.google.com ([209.85.210.68]:46561 "EHLO mail-ot1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726176AbfC0XHY (ORCPT ); Wed, 27 Mar 2019 19:07:24 -0400 Received: by mail-ot1-f68.google.com with SMTP id s24so7076196otk.13; Wed, 27 Mar 2019 16:07:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=WOIvTZkyBewSM9hPCcfz1BOCmh+9VTusdQO/GI6NhU4=; b=jcgKJXMYo2EocpuliClm7cm1KuHyzpeaYNGH/l2Ba8Cl47J1/A9M2IHFySxkEbMZO+ sqTDQdE96wEE4YQetldPDzi2gII2J1khEXIJmK1GbCzk8A47pRmyacZb+6SxlgQle8e1 VGA6OvcmMasSSD9ER3dfY7V7TU/1DEVDLdAQ6vHJUbjHcRxIio2gion8LLonvpnU70LV Ox/4qh/4yVlWmR3MP7g3lupUoR7wDIbyn87C5/o67N1Nmhy4y6tL1UP+a7PANmgS4R4+ MU0uVpvp6iSI9+bfddLIb4u2M1x1T2lXOnlvAwa7AZKNuPgi4L6MIh7R3F8ekqySAhQT B4BQ== X-Gm-Message-State: APjAAAU4LYv2zVMlPVLGMLoyFk5ZmjNY9e/YATBdEwz01hePzPbycBcR J4QXj26ozX8cfxuif4PoQJgpt6g= X-Received: by 2002:a9d:6408:: with SMTP id h8mr26065756otl.68.1553728043646; Wed, 27 Mar 2019 16:07:23 -0700 (PDT) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id y1sm4430728ota.38.2019.03.27.16.07.22 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 27 Mar 2019 16:07:22 -0700 (PDT) Date: Wed, 27 Mar 2019 18:07:22 -0500 From: Rob Herring 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 Subject: Re: [PATCH 1/8] dt-bindings: stm32: add bindings for ML-AHB interconnect Message-ID: <20190327230722.GA13708@bogus> References: <1551795849-13672-1-git-send-email-fabien.dessenne@st.com> <1551795849-13672-2-git-send-email-fabien.dessenne@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1551795849-13672-2-git-send-email-fabien.dessenne@st.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 05, 2019 at 03:24:02PM +0100, Fabien Dessenne wrote: > Document the ML-AHB interconnect for stm32 SoCs. > > Signed-off-by: Fabien Dessenne > --- > .../devicetree/bindings/arm/stm32/mlahb.txt | 30 ++++++++++++++++++++++ > 1 file changed, 30 insertions(+) > create mode 100644 Documentation/devicetree/bindings/arm/stm32/mlahb.txt > > diff --git a/Documentation/devicetree/bindings/arm/stm32/mlahb.txt b/Documentation/devicetree/bindings/arm/stm32/mlahb.txt > new file mode 100644 > index 0000000..880cb38 > --- /dev/null > +++ b/Documentation/devicetree/bindings/arm/stm32/mlahb.txt > @@ -0,0 +1,30 @@ > +ML-AHB interconnect bindings > + > +These bindings describe the STM32 SoCs ML-AHB interconnect bus which connects > +a Cortex-M subsystem with dedicated memories. > + > +Required properties: > +- compatible: should be "simple-bus" A binding for simple-bus was the first thing that looked odd. > +- ranges: describes memory addresses translation between the local CPU and the > + remote Cortex-M processor. Each memory region, is declared with 3 > + parameters: > + - param 1: device base address (Cortex-M processor address) > + - param 2: physical base address (local CPU address) > + - param 3: size of the memory region. Given that the driver is parsing ranges itself, this looks like abuse of ranges. What exactly is address 0 supposed to be here? If it is the M4's view of memory, then dma-ranges is what you want to use here. > + > +The Cortex-M remote processor accessed via the mlahb interconnect is described > +by a child node. > + > +Example: > +mlahb: mlahb@0 { Note that the unit-address is wrong here as it should be 38000000. > + compatible = "simple-bus"; > + #address-cells = <1>; > + #size-cells = <1>; > + ranges = <0x00000000 0x38000000 0x10000>, > + <0x10000000 0x10000000 0x60000>, > + <0x30000000 0x30000000 0x60000>; > + > + m4_rproc: m4@0 { > + ... > + }; > +}; > -- > 2.7.4 >