From: Nishanth Menon <nm@ti.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>, Faiz Abbas <faiz_abbas@ti.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <t-kristo@ti.com>,
<robh+dt@kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH 1/3] arm64: dts: ti: k3-j7200-main: Add gpio nodes in main domain
Date: Fri, 13 Nov 2020 14:55:52 -0600 [thread overview]
Message-ID: <20201113205552.p63u2gxgw4pfxil5@stunning> (raw)
In-Reply-To: <c6267288-581e-3b34-cec5-d5879f3d1283@ti.com>
On 00:39-20201114, Sekhar Nori wrote:
>
> I was using the latest schema from master. But I changed to 2020.08.1
> also, and still don't see the warning.
>
> $ dt-doc-validate --version
> 2020.12.dev1+gab5a73fcef26
>
> I dont have a system-wide dtc installed. One in kernel tree is updated.
>
> $ scripts/dtc/dtc --version
> Version: DTC 1.6.0-gcbca977e
>
> Looking at your logs, it looks like you have more patches than just this
> applied. I wonder if thats making a difference. Can you check with just
> these patches applied to linux-next or share your tree which includes
> other patches?
>
> In your logs, you have such error for other interrupt controller nodes
> as well. For example:
>
> arch/arm64/boot/dts/ti/k3-j7200-main.dtsi:
> /bus@100000/bus@30000000/interrupt-controller1: Missing #address-cells
> in interrupt provider
>
> Which I don't see in my logs. My guess is some other patch(es) in your
> patch stack either uncovers this warning or causes it.
Oh boy! I sent you and myself on wild goose chase! Really sorry about
messing up in the report of bug.
It is not dtbs_check, it is building dtbs with W=2 that generates this
warning. dtc 1.6.0 is sufficient to reproduce this behavior.
Using v5.10-rc1 as baseline (happens the same with next-20201113 as
well.
v5.10-rc1: https://pastebin.ubuntu.com/p/Pn9HDqRjQ4/ (recording:
https://asciinema.org/a/55YVpql9Bq8rh8fePTxI2xObO)
v5.10-rc1 + 1st patch in the series(since we are testing):
https://pastebin.ubuntu.com/p/QWQRMSv565/ (recording:
https://asciinema.org/a/ZSKZkOY13l4lmZ2xWH34jMlM1)
Diff: https://pastebin.ubuntu.com/p/239sYYT2QY/
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: devicetree@vger.kernel.org,
Grygorii Strashko <grygorii.strashko@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
t-kristo@ti.com, Faiz Abbas <faiz_abbas@ti.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: ti: k3-j7200-main: Add gpio nodes in main domain
Date: Fri, 13 Nov 2020 14:55:52 -0600 [thread overview]
Message-ID: <20201113205552.p63u2gxgw4pfxil5@stunning> (raw)
In-Reply-To: <c6267288-581e-3b34-cec5-d5879f3d1283@ti.com>
On 00:39-20201114, Sekhar Nori wrote:
>
> I was using the latest schema from master. But I changed to 2020.08.1
> also, and still don't see the warning.
>
> $ dt-doc-validate --version
> 2020.12.dev1+gab5a73fcef26
>
> I dont have a system-wide dtc installed. One in kernel tree is updated.
>
> $ scripts/dtc/dtc --version
> Version: DTC 1.6.0-gcbca977e
>
> Looking at your logs, it looks like you have more patches than just this
> applied. I wonder if thats making a difference. Can you check with just
> these patches applied to linux-next or share your tree which includes
> other patches?
>
> In your logs, you have such error for other interrupt controller nodes
> as well. For example:
>
> arch/arm64/boot/dts/ti/k3-j7200-main.dtsi:
> /bus@100000/bus@30000000/interrupt-controller1: Missing #address-cells
> in interrupt provider
>
> Which I don't see in my logs. My guess is some other patch(es) in your
> patch stack either uncovers this warning or causes it.
Oh boy! I sent you and myself on wild goose chase! Really sorry about
messing up in the report of bug.
It is not dtbs_check, it is building dtbs with W=2 that generates this
warning. dtc 1.6.0 is sufficient to reproduce this behavior.
Using v5.10-rc1 as baseline (happens the same with next-20201113 as
well.
v5.10-rc1: https://pastebin.ubuntu.com/p/Pn9HDqRjQ4/ (recording:
https://asciinema.org/a/55YVpql9Bq8rh8fePTxI2xObO)
v5.10-rc1 + 1st patch in the series(since we are testing):
https://pastebin.ubuntu.com/p/QWQRMSv565/ (recording:
https://asciinema.org/a/ZSKZkOY13l4lmZ2xWH34jMlM1)
Diff: https://pastebin.ubuntu.com/p/239sYYT2QY/
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-13 20:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 19:11 [PATCH 0/3] Add gpio support for TI's J7200 platform Faiz Abbas
2020-11-02 19:11 ` Faiz Abbas
2020-11-02 19:11 ` [PATCH 1/3] arm64: dts: ti: k3-j7200-main: Add gpio nodes in main domain Faiz Abbas
2020-11-02 19:11 ` Faiz Abbas
2020-11-12 16:39 ` Nishanth Menon
2020-11-12 16:39 ` Nishanth Menon
2020-11-13 18:29 ` Sekhar Nori
2020-11-13 18:29 ` Sekhar Nori
2020-11-13 18:40 ` Nishanth Menon
2020-11-13 18:40 ` Nishanth Menon
2020-11-13 19:09 ` Sekhar Nori
2020-11-13 19:09 ` Sekhar Nori
2020-11-13 20:55 ` Nishanth Menon [this message]
2020-11-13 20:55 ` Nishanth Menon
2020-11-14 4:15 ` Grygorii Strashko
2020-11-14 4:15 ` Grygorii Strashko
2020-11-14 5:56 ` Sekhar Nori
2020-11-14 5:56 ` Sekhar Nori
2020-11-02 19:11 ` [PATCH 2/3] arm64: dts: ti: k3-j7200: Add gpio nodes in wakeup domain Faiz Abbas
2020-11-02 19:11 ` Faiz Abbas
2020-11-02 19:11 ` [PATCH 3/3] arm64: dts: ti: k3-j7200-common-proc-board: Disable unused gpio modules Faiz Abbas
2020-11-02 19:11 ` Faiz Abbas
2020-11-04 11:40 ` [PATCH 0/3] Add gpio support for TI's J7200 platform Lokesh Vutla
2020-11-04 11:40 ` Lokesh Vutla
2020-11-12 16:42 ` Nishanth Menon
2020-11-12 16:42 ` Nishanth Menon
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=20201113205552.p63u2gxgw4pfxil5@stunning \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.