devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Chunyan Zhang <zhang.lyra@gmail.com>
Cc: Chunyan Zhang <chunyan.zhang@unisoc.com>,
	Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-kernel@lists.infradead.org, soc@kernel.org,
	devicetree@vger.kernel.org,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Orson Zhai <orsonzhai@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: Add support for Unisoc's UMS512
Date: Tue, 7 Feb 2023 09:40:16 +0100	[thread overview]
Message-ID: <20133e17-78da-d5f6-39bb-0031745fa294@linaro.org> (raw)
In-Reply-To: <CAAfSe-tiF4--dYuKWgHUm52bMX3uSwxvWKKNRd=DFJTZZ=1x8A@mail.gmail.com>

On 07/02/2023 09:21, Chunyan Zhang wrote:
>>>> Non-unit-address nodes cannot be mixed with unit address ones. Something
>>>> is wrong here.
>>>
>>> To make sure I understand correctly, did you mean non-unit-address
>>> nodes shouldn't be the parent of unit-address nodes?
>>>
>>> Does that mean the bus node should have a unique base address like:
>>>         ap-apb@70000000 {
>>
>> No. I mean, run dtbs W=1 or dtbs_check DT_SCHEMA_FILES=simple-bus
> 
> Ok, I will fix that according to the report.
> 
> BTW, where can I see what W=1 means?

In standard kernel documentation or make help.

Best regards,
Krzysztof


      reply	other threads:[~2023-02-07  8:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  8:40 [PATCH] arm64: dts: Add support for Unisoc's UMS512 Chunyan Zhang
2023-01-19 11:40 ` Krzysztof Kozlowski
2023-02-06  9:28   ` Chunyan Zhang
2023-02-06 10:34     ` Krzysztof Kozlowski
2023-02-07  2:19   ` Chunyan Zhang
2023-02-07  7:59     ` Krzysztof Kozlowski
2023-02-07  8:21       ` Chunyan Zhang
2023-02-07  8:40         ` Krzysztof Kozlowski [this message]

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=20133e17-78da-d5f6-39bb-0031745fa294@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=arnd@arndb.de \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=chunyan.zhang@unisoc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=orsonzhai@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=soc@kernel.org \
    --cc=zhang.lyra@gmail.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).