linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Rob Herring <robh@kernel.org>, soc@kernel.org
Cc: Nishanth Menon <nm@ti.com>, Andrew Lunn <andrew@lunn.ch>,
	Heiko Stuebner <heiko@sntech.de>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Fabio Estevam <festevam@gmail.com>,
	Jerome Brunet <jbrunet@baylibre.com>,
	Khuong Dinh <khuong@os.amperecomputing.com>,
	Kevin Hilman <khilman@baylibre.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Michal Simek <michal.simek@xilinx.com>,
	Wei Xu <xuwei5@hisilicon.com>,
	linux-rockchip@lists.infradead.org,
	Andy Gross <agross@kernel.org>,
	NXP Linux Team <linux-imx@nxp.com>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	devicetree@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
	Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	linux-arm-msm@vger.kernel.org,
	Sascha Hauer <s.hauer@pengutronix.de>,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	Li Yang <leoyang.li@nxp.com>, Tero Kristo <t-kristo@ti.com>,
	Robert Richter <rrichter@marvell.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>
Subject: Re: [PATCH] arm64: dts: Reformat PCI ranges/dma-ranges entries
Date: Thu, 20 Aug 2020 09:25:38 +0200	[thread overview]
Message-ID: <df3992e8-cf97-3b1b-06af-3b57cbce13dc@xilinx.com> (raw)
In-Reply-To: <20200819221750.2055932-1-robh@kernel.org>



On 20. 08. 20 0:17, Rob Herring wrote:
> While bracketing doesn't matter for a DTB, the DT schema checks rely on
> bracketing around each distinct entry. Reformat ranges and dma-ranges
> entries to fix warnings such as:
> 
> arch/arm64/boot/dts/rockchip/rk3399-sapphire-excavator.dt.yaml: pcie@f8000000: ranges: [[2197815296, 0, 4194304000, 0, 4194304000, 0, 31457280, 2164260864, 0, 4225761280, 0, 4225761280, 0, 1048576]] is not valid under any of the given schemas (Possible causes of the failure):
>         arch/arm64/boot/dts/rockchip/rk3399-sapphire-excavator.dt.yaml: pcie@f8000000: ranges: True was expected
>         arch/arm64/boot/dts/rockchip/rk3399-sapphire-excavator.dt.yaml: pcie@f8000000: ranges:0: [2197815296, 0, 4194304000, 0, 4194304000, 0, 31457280, 2164260864, 0, 4225761280, 0, 4225761280, 0, 1048576] is too long
>         arch/arm64/boot/dts/rockchip/rk3399-sapphire-excavator.dt.yaml: pcie@f8000000: ranges:0:0: 2197815296 is not one of [16777216, 33554432, 50331648, 1107296256, 1124073472]
> 
> Cc: Kevin Hilman <khilman@baylibre.com>
> Cc: Neil Armstrong <narmstrong@baylibre.com>
> Cc: Jerome Brunet <jbrunet@baylibre.com>
> Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Cc: Khuong Dinh <khuong@os.amperecomputing.com>
> Cc: Robert Richter <rrichter@marvell.com>
> Cc: Shawn Guo <shawnguo@kernel.org>
> Cc: Li Yang <leoyang.li@nxp.com>
> Cc: Sascha Hauer <s.hauer@pengutronix.de>
> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
> Cc: Fabio Estevam <festevam@gmail.com>
> Cc: NXP Linux Team <linux-imx@nxp.com>
> Cc: Wei Xu <xuwei5@hisilicon.com>
> Cc: Jason Cooper <jason@lakedaemon.net>
> Cc: Andrew Lunn <andrew@lunn.ch>
> Cc: Gregory Clement <gregory.clement@bootlin.com>
> Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> Cc: Andy Gross <agross@kernel.org>
> Cc: Bjorn Andersson <bjorn.andersson@linaro.org>
> Cc: Heiko Stuebner <heiko@sntech.de>
> Cc: Tero Kristo <t-kristo@ti.com>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Michal Simek <michal.simek@xilinx.com>
> Cc: linux-amlogic@lists.infradead.org
> Cc: linux-arm-msm@vger.kernel.org
> Cc: linux-rockchip@lists.infradead.org
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> SoC maintainers, please apply this directly.
> 
>  .../boot/dts/amlogic/meson-g12-common.dtsi    |  4 +-
>  arch/arm64/boot/dts/apm/apm-shadowcat.dtsi    | 20 ++++----
>  arch/arm64/boot/dts/apm/apm-storm.dtsi        | 50 +++++++++----------
>  arch/arm64/boot/dts/cavium/thunder2-99xx.dtsi |  4 +-
>  .../arm64/boot/dts/freescale/fsl-ls1012a.dtsi |  4 +-
>  .../arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 22 ++++----
>  .../boot/dts/freescale/fsl-ls1043a-qds.dts    |  6 +--
>  .../boot/dts/freescale/fsl-ls1043a-rdb.dts    |  6 +--
>  .../arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 12 ++---
>  .../boot/dts/freescale/fsl-ls1046a-qds.dts    |  6 +--
>  .../boot/dts/freescale/fsl-ls1046a-rdb.dts    |  4 +-
>  .../arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 12 ++---
>  .../boot/dts/freescale/fsl-ls1088a-qds.dts    |  6 +--
>  .../boot/dts/freescale/fsl-ls1088a-rdb.dts    |  4 +-
>  .../arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 16 +++---
>  .../arm64/boot/dts/freescale/fsl-ls2080a.dtsi | 16 +++---
>  .../arm64/boot/dts/freescale/fsl-ls2088a.dtsi | 16 +++---
>  .../boot/dts/freescale/fsl-ls208xa-qds.dtsi   |  6 +--
>  .../boot/dts/freescale/fsl-ls208xa-rdb.dtsi   |  6 +--
>  .../arm64/boot/dts/freescale/fsl-ls208xa.dtsi | 10 ++--
>  .../arm64/boot/dts/freescale/fsl-lx2160a.dtsi |  4 +-
>  arch/arm64/boot/dts/freescale/imx8mq.dtsi     |  8 +--
>  .../arm64/boot/dts/hisilicon/hi3798cv200.dtsi |  4 +-
>  arch/arm64/boot/dts/hisilicon/hip06.dtsi      |  5 +-
>  arch/arm64/boot/dts/hisilicon/hip07.dtsi      |  4 +-
>  arch/arm64/boot/dts/marvell/armada-37xx.dtsi  |  4 +-
>  arch/arm64/boot/dts/qcom/ipq8074.dtsi         | 12 ++---
>  arch/arm64/boot/dts/rockchip/rk3399.dtsi      |  4 +-
>  arch/arm64/boot/dts/ti/k3-am65-main.dtsi      |  8 +--
>  arch/arm64/boot/dts/xilinx/zynqmp.dtsi        |  4 +-

Reviewed-by: Michal Simek <michal.simek@xilinx.com> (zynqmp)

Thanks,
Michal

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-08-20  7:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19 22:17 [PATCH] arm64: dts: Reformat PCI ranges/dma-ranges entries Rob Herring
2020-08-20  7:25 ` Michal Simek [this message]
2020-08-20 11:44 ` Nishanth Menon
2020-08-21  1:12 ` Olof Johansson
2020-08-21 16:14   ` Rob Herring
2020-08-21 17:14     ` Olof Johansson
2020-08-21 21:40       ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=df3992e8-cf97-3b1b-06af-3b57cbce13dc@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=agross@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=gregory.clement@bootlin.com \
    --cc=heiko@sntech.de \
    --cc=jason@lakedaemon.net \
    --cc=jbrunet@baylibre.com \
    --cc=kernel@pengutronix.de \
    --cc=khilman@baylibre.com \
    --cc=khuong@os.amperecomputing.com \
    --cc=leoyang.li@nxp.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=narmstrong@baylibre.com \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=rrichter@marvell.com \
    --cc=s.hauer@pengutronix.de \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=shawnguo@kernel.org \
    --cc=soc@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=xuwei5@hisilicon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).