From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: Jassi Brar <jaswinder.singh@linaro.org>,
Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: mailbox: Convert omap-mailbox.txt binding to YAML
Date: Wed, 19 May 2021 19:08:31 -0500 [thread overview]
Message-ID: <20210520000831.GA3927464@robh.at.kernel.org> (raw)
In-Reply-To: <c666919f-cc10-3ca5-a1e3-5062c260e827@ti.com>
On Wed, May 19, 2021 at 10:14:14AM -0500, Suman Anna wrote:
> On 5/18/21 12:20 PM, Suman Anna wrote:
> > Convert the current OMAP Mailbox binding from text format to YAML
> > format/DT schema, and delete the legacy text binding file.
> >
> > The new YAML binding conversion is an updated version compared to
> > the original. The descriptions for certain properties have been
> > improved to provide more clarity. Constraints are added to the
> > properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
> > The 'ti,hwmods' is a legacy property and is retained only to reflect
> > the existing usage on some older OMAP2 and OMAP3 platforms.
> >
> > All the existing examples have also been updated to reflect the
> > latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
> > and interrupts value updated for AM65x SoCs).
> >
> > Signed-off-by: Suman Anna <s-anna@ti.com>
> > ---
> > Hi,
> >
> > This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
> > nodes with the latest kernel. There are few left-over warnings when just
> > this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
> > fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
> > series for OMAP2+ SoCs. The dts patches can be picked up independently
> > of this patch.
>
> FYI, All the dtbs_check warnings will be gone with [1] and the OMAP2+ cleanup
> series [2].
Nice, though it is a moving target. :) Is that still true with the
undocumented compatible checks that's been added?
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Suman Anna <s-anna@ti.com>
Cc: Jassi Brar <jaswinder.singh@linaro.org>,
Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
devicetree@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: mailbox: Convert omap-mailbox.txt binding to YAML
Date: Wed, 19 May 2021 19:08:31 -0500 [thread overview]
Message-ID: <20210520000831.GA3927464@robh.at.kernel.org> (raw)
In-Reply-To: <c666919f-cc10-3ca5-a1e3-5062c260e827@ti.com>
On Wed, May 19, 2021 at 10:14:14AM -0500, Suman Anna wrote:
> On 5/18/21 12:20 PM, Suman Anna wrote:
> > Convert the current OMAP Mailbox binding from text format to YAML
> > format/DT schema, and delete the legacy text binding file.
> >
> > The new YAML binding conversion is an updated version compared to
> > the original. The descriptions for certain properties have been
> > improved to provide more clarity. Constraints are added to the
> > properties 'ti,mbox-num-users', 'ti,mbox-num-fifos' and 'interrupts'.
> > The 'ti,hwmods' is a legacy property and is retained only to reflect
> > the existing usage on some older OMAP2 and OMAP3 platforms.
> >
> > All the existing examples have also been updated to reflect the
> > latest dts nodes (ti,hwmods removed from OMAP4 and AM33xx examples,
> > and interrupts value updated for AM65x SoCs).
> >
> > Signed-off-by: Suman Anna <s-anna@ti.com>
> > ---
> > Hi,
> >
> > This patch does fix a number of dtbs_check warnings seen around OMAP Mailbox
> > nodes with the latest kernel. There are few left-over warnings when just
> > this patch is used on v5.13-rc1 or next-20210518. I have posted a separate
> > fix for a warning on TI K3 SoCs [1], and will be posting a separate cleanup
> > series for OMAP2+ SoCs. The dts patches can be picked up independently
> > of this patch.
>
> FYI, All the dtbs_check warnings will be gone with [1] and the OMAP2+ cleanup
> series [2].
Nice, though it is a moving target. :) Is that still true with the
undocumented compatible checks that's been added?
Rob
_______________________________________________
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:[~2021-05-20 0:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 17:20 [PATCH] dt-bindings: mailbox: Convert omap-mailbox.txt binding to YAML Suman Anna
2021-05-18 17:20 ` Suman Anna
2021-05-19 15:14 ` Suman Anna
2021-05-19 15:14 ` Suman Anna
2021-05-20 0:08 ` Rob Herring [this message]
2021-05-20 0:08 ` Rob Herring
2021-05-20 16:45 ` Suman Anna
2021-05-20 16:45 ` Suman Anna
2021-05-20 19:21 ` Rob Herring
2021-05-20 19:21 ` Rob Herring
2021-05-20 20:07 ` Suman Anna
2021-05-20 20:07 ` Suman Anna
2021-05-25 6:44 ` Tony Lindgren
2021-05-25 6:44 ` Tony Lindgren
2021-05-21 9:21 ` Tony Lindgren
2021-05-21 9:21 ` Tony Lindgren
2021-05-20 0:14 ` Rob Herring
2021-05-20 0:14 ` 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=20210520000831.GA3927464@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-anna@ti.com \
--cc=tony@atomide.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.