Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3569259ybl; Sun, 25 Aug 2019 19:18:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqw1j/8EtK9Qu3sz180ZsW6Z8Fl4MDGCg2TAca2Toke79KIAv1U+oChr8sbxqBuadBqAUvS8 X-Received: by 2002:a62:db86:: with SMTP id f128mr17286325pfg.159.1566785898628; Sun, 25 Aug 2019 19:18:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566785898; cv=none; d=google.com; s=arc-20160816; b=enAtZKjIgn4r4nOmnYVN2ioBmqvC6lDeiUelbZtYBz8YSYeHmkYw2H4IwyX4T7zxSy Yg5x50f+I64YRM1IO9kTqs/xBC2KifvI0DevPD0EldG1Rc5mvigg13MA5Za2y2a8UH+W FJqmeM9DUV16SHAFvkZMxNL5Mw5sD39ewGRNfJ7JtSOKd1Crbo5a8vYp2qvlFRFsD6lO uHudwIInS20AZGz0z+PB7sOAi/89+cuIbn541yedk7i5al2mhSSliV1qB3i4OcI5tmBA kXQi5odn+aMFHVwBHg0zwVWW+l7kEPg0B8pswnq3j9wGSGYvKCpZ1NJGyhiEzjR5UfdY jyqA== 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:mime-version :message-id:date:subject:cc:to:from:dkim-signature:dkim-signature; bh=5HH0SDUDjRUO/CjnMqxbLxtd9WvPtHdd1vX8IagkIVU=; b=rPb+uPvKW95i1m+KSWttci7ai+M6CfF2oa04vLftfw98GLyheV1uAT60j8D3hFR/Z0 VseSsjHVYUE6nFOYjCoG+Rhbm4Q2jJq5KaUhvriYdfSObC6FeVkP+XZSY0pBkfVBy3Y9 Q+JBurCztiq4O4Dx5pbJS+KCrGfu1jz0iNf0VS9IgiTH90Aq6+IvovpgLJ6cEaLyFXQ3 2DSHPYJaC1qemY7XM9wZUk1PVhRBQUaduBfcGdAA9LMYYlczqtCWqqLu96Xlk/YLrx57 BGnfgdbHETEOaJ1cY4brgLEZYY/MoSesYbPGAjf+SQsOMRRI0+6J7FHemr4Wf3OqPPwB RsJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm3 header.b=fQj6puKz; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=N4Jrnv7N; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g3si8693910pld.75.2019.08.25.19.18.02; Sun, 25 Aug 2019 19:18:18 -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=@aj.id.au header.s=fm3 header.b=fQj6puKz; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=N4Jrnv7N; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729114AbfHZCPy (ORCPT + 99 others); Sun, 25 Aug 2019 22:15:54 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:33525 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726434AbfHZCPx (ORCPT ); Sun, 25 Aug 2019 22:15:53 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C673621F18; Sun, 25 Aug 2019 22:15:52 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 25 Aug 2019 22:15:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h=from :to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=fm3; bh=5HH0SDUDjRUO/CjnMqxbLxtd9W vPtHdd1vX8IagkIVU=; b=fQj6puKz2T8eR411RhHtM0GGLu7IKaPpkIZcw5LLEy djuvXoAnCMjVSALDV6vxlPeDNsxB6UOcQiuFfezoN12Mos5C2yDhCiwkstD4tI6g ctDs5n6mvhc7u9KmHxWyKt0vlSmRio22Mmz5w/2FBYPxCMsXmrBexTbhsgKFIa7c QiX0hhb6tDoZLDAhZ8s6pc9mDLbi8PHe1IG51ErssC9JGhDcdSf3QYjaMNtb6jY8 mDYyfETSusbESJw6gTYRr3x6PmwvSfzWWMpj2gSTIP5uZzvviDj/2idQ87vP6o2V echX0LOopFfC1dPQ5YHlr7rcKi7srI08N6DTsOZx6GpA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=5HH0SDUDjRUO/CjnM qxbLxtd9WvPtHdd1vX8IagkIVU=; b=N4Jrnv7NNhn1eGNqUYS3qwdxiypPeW/6j rSIAdhu9HgDrfmjq0mwJJZ7M0EzfY6cvzHJvYVomrUnJQFxA/1PRRaJMtYIkOKjv T3oaFzbF6kyMsDdqKQHICCzpn3iaSrTrTYcgWC8nFzZt+N6u2HT5wUtGiGk1NQHP b3xv2vHtO3amFPLXBG7Ns1bPKcvAEgcTPLyJZhDlxsAuyX314FxbOfTcpDi/23k1 XU6+8hflfJzztEsBvYyAnrMYjj1ETxrXqM9q8cBlq9Q2J2LiGYe89nUc1fpxVNLK 55OnG/kjco8SjmQ5rKLfV1qSa8+D60/dfUj1zvGWmMWlPxefu69HA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudehfedgheekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkofgggfestdekredtre dttdenucfhrhhomheptehnughrvgifucflvghffhgvrhihuceorghnughrvgifsegrjhdr ihgurdgruheqnecuffhomhgrihhnpeguvghvihgtvghtrhgvvgdrohhrghdpohiilhgrsg hsrdhorhhgnecukfhppedvtdefrdehjedrvdduhedrudejkeenucfrrghrrghmpehmrghi lhhfrhhomheprghnughrvgifsegrjhdrihgurdgruhenucevlhhushhtvghrufhiiigvpe dt X-ME-Proxy: Received: from localhost.localdomain (203-57-215-178.dyn.iinet.net.au [203.57.215.178]) by mail.messagingengine.com (Postfix) with ESMTPA id 3C828D6005D; Sun, 25 Aug 2019 22:15:47 -0400 (EDT) From: Andrew Jeffery To: linux-mmc@vger.kernel.org Cc: Andrew Jeffery , ulf.hansson@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com, joel@jms.id.au, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org Subject: [PATCH] dt-bindings: mmc: aspeed: Update example ranges property Date: Mon, 26 Aug 2019 11:46:19 +0930 Message-Id: <20190826021620.11915-1-andrew@aj.id.au> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The example node in the binding uses the AST2500 compatible string for the SD controller with a 64kiB ranges property, but the SD controller is allocated 128kiB of MMIO space according to the AST2500 datasheet. Fix the example to correctly reflect the hardware in the AST2500, however it should be noted that the MMIO region is reduced to 64kiB in the AST2600 where a second SD controller block has been introduced into the address space. Also add the IBM copyright header that I left out of the initial patch. Suggested-by: Joel Stanley Signed-off-by: Andrew Jeffery --- Hi Ulf, this is the follow-up fix as discussed here: http://patchwork.ozlabs.org/patch/1143090/ Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml b/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml index 570f8c72662b..200de9396036 100644 --- a/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml +++ b/Documentation/devicetree/bindings/mmc/aspeed,sdhci.yaml @@ -1,4 +1,5 @@ # SPDX-License-Identifier: GPL-2.0-or-later +# Copyright 2019 IBM Corp. %YAML 1.2 --- $id: http://devicetree.org/schemas/mmc/aspeed,sdhci.yaml# @@ -84,7 +85,7 @@ examples: reg = <0x1e740000 0x100>; #address-cells = <1>; #size-cells = <1>; - ranges = <0 0x1e740000 0x10000>; + ranges = <0 0x1e740000 0x20000>; clocks = <&syscon ASPEED_CLK_GATE_SDCLK>; sdhci0: sdhci@100 { -- 2.20.1