Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1283648ybl; Fri, 13 Dec 2019 12:37:11 -0800 (PST) X-Google-Smtp-Source: APXvYqyAnZK9KcWlNoY6LkeFCb23CprhtKLvQWjr2djOv8DrmfecW0tqAmD4WSfPfAqs/gCXNKTn X-Received: by 2002:a9d:518b:: with SMTP id y11mr15947563otg.349.1576269431051; Fri, 13 Dec 2019 12:37:11 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576269431; cv=none; d=google.com; s=arc-20160816; b=oqS0j1hokKak1RASlmqolWPH9twIP4whW33HlDYcy414BuCTyVfqm/qSNhpS6B9CmL 2eWd6EVEA7iPs00e9jvfMce4BQgNLCZ/cvPm1b5D7O6taa6887E3UYALOO4jUCvjqRLP S7lJXYrhMegH7PpLmKEsuy+hW0I+eb/77L+IXo1GXG/uKMMKtSt0kdaYgMmJRZRC+zk9 Lj6NOvaAYrnEzzM6cBLErhCAU9SHAeyvGpomTrmIGnMZpHNbcRYpAxUbOJTLjgMRFvIh JPIEVAGt2Wvtn21TK3FQtKI0rxbyGOtaZ47nTDM6qu2m5aPceScNCcjY0UVPM+Yu+7b1 v07Q== 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=P5TwpulYstNNd0cq7HfhmO8Yoxe2ksK4Z9t8jqMIjkg=; b=v8eYZWg/ltQ2W49pWPInOpgJf8huOcNetxnEY8EAfGB3713yARD6tizfW2oGyBHZcR w4gpzolkXL9DZrgLaHzXwT8XGC6kiLbQkB4P9psWUE+WhSCR3756l9ZPhwfJLFvFoKZi qqcsYkAld3M/wfBz4YCvJT8UF0hKC519/ZolnUNoPrwaGuqv9QCQutgENd5YtzsODjsv NdeE4gvs6hH4ZhWJIv4pF3qgFG8QgMChUKp7Ra+w+cKBTiPnnd37rYMcraPJVvG7a/Ke ziHhNwU0651xDRKouMBhkTnxOIHB02p1P9LNLwpsHJisaqOmXLWvF7v4gmrMfsckSyKb dzfQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="x/ScfOhL"; 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 c131si5283674oig.170.2019.12.13.12.36.59; Fri, 13 Dec 2019 12:37:11 -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=@kernel.org header.s=default header.b="x/ScfOhL"; 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 S1729112AbfLMUgK (ORCPT + 99 others); Fri, 13 Dec 2019 15:36:10 -0500 Received: from mail.kernel.org ([198.145.29.99]:47884 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729067AbfLMUgF (ORCPT ); Fri, 13 Dec 2019 15:36:05 -0500 Received: from mail-qk1-f176.google.com (mail-qk1-f176.google.com [209.85.222.176]) (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 8C54E246E0; Fri, 13 Dec 2019 20:36:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576269363; bh=TD0vlyaaEUltY3uhgJ1XIdZNPofDo4T5Xxo/vcYOCwY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=x/ScfOhLMLfLSOxK98g5I1CSfHCvGY8HkFL/pbJrRsktxxOZFqLEFBhiV5wU2WRJN wrMijQLeCDJ0+/5Gf3VRdeM4RfREKcGKQHDOeystLL6jmmznSYZQ317HO5Hj2gFMvG 7MCWp2IyA61/qrqAS2yk3WEW+zO96cbyO5994S8E= Received: by mail-qk1-f176.google.com with SMTP id x1so267197qkl.12; Fri, 13 Dec 2019 12:36:04 -0800 (PST) X-Gm-Message-State: APjAAAWfG8iJtaCznxj4UTCAv42KaVQ91sahk9pg5aTICADg2k+iRNjB yIhYTFKrRnxCDapIugMrJK1Ydw4kTJhq4hG3qg== X-Received: by 2002:a37:85c4:: with SMTP id h187mr14127413qkd.223.1576249641042; Fri, 13 Dec 2019 07:07:21 -0800 (PST) MIME-Version: 1.0 References: <20191213084748.11210-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20191213084748.11210-4-prabhakar.mahadev-lad.rj@bp.renesas.com> In-Reply-To: <20191213084748.11210-4-prabhakar.mahadev-lad.rj@bp.renesas.com> From: Rob Herring Date: Fri, 13 Dec 2019 09:07:07 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [v2 3/6] of: address: add support to parse PCI outbound-ranges To: Lad Prabhakar Cc: Bjorn Helgaas , Mark Rutland , Geert Uytterhoeven , Magnus Damm , Kishon Vijay Abraham I , Marek Vasut , Yoshihiro Shimoda , PCI , Catalin Marinas , Will Deacon , Lorenzo Pieralisi , Arnd Bergmann , Greg Kroah-Hartman , Andrew Murray , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , "open list:MEDIA DRIVERS FOR RENESAS - FCP" , Chris Paterson , Frank Rowand , Gustavo Pimentel , Jingoo Han , Simon Horman , Shawn Lin , Tom Joseph , Heiko Stuebner , "open list:ARM/Rockchip SoC..." , "Lad, Prabhakar" 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 Fri, Dec 13, 2019 at 2:48 AM Lad Prabhakar wrote: > > From: "Lad, Prabhakar" > > this patch adds support to parse PCI outbound-ranges, the > outbound-regions are similar to pci ranges except it doesn't > have pci address, below is the format for bar-ranges: > > outbound-ranges = upper32_size lower32_size>; You can't just make up a new ranges property. Especially one that doesn't follow how 'ranges' works. We already have 'dma-ranges' to translate device to memory addresses. Explain the problem or feature you need, not the solution you came up with. Why do you need this and other endpoint bindings haven't? Rob