From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] dt-bindings: Arm CoreSight binding schema conversions
Date: Wed, 29 Jun 2022 10:28:31 -0600 [thread overview]
Message-ID: <20220629162831.GB2013207@p14s> (raw)
In-Reply-To: <20220628180118.GA703354-robh@kernel.org>
On Tue, Jun 28, 2022 at 12:01:18PM -0600, Rob Herring wrote:
> On Mon, Jun 20, 2022 at 10:55:41AM -0600, Mathieu Poirier wrote:
> > Hi Rob,
> >
> > On Thu, Jun 02, 2022 at 08:19:30PM -0500, Rob Herring wrote:
> > > This series converts all the CoreSight debug bindings to DT schema
> > > format. These bindings are at the top of the list of occurrences of
> > > bindings without a schema. For arm64 dts files:
> > >
> > > 702 ['arm,coresight-etm4x', 'arm,primecell']
> > > 536 ['arm,coresight-cpu-debug', 'arm,primecell']
> > > 509 ['arm,coresight-dynamic-funnel', 'arm,primecell']
> > > 213 ['arm,coresight-tmc', 'arm,primecell']
> > > 143 ['arm,coresight-dynamic-replicator', 'arm,primecell']
> > > 97 ['arm,coresight-stm', 'arm,primecell']
> > >
> > > I'll send a reply to these with the errors in dts files that this
> > > causes. I've reviewed them and they all look legit. Xilinx Zynq though
> > > has 3 clocks instead of 2.
> > >
> > > v2:
> > > - Rename other Coresight bindings to use compatible string for filename
> > > - Add missing arm,coresight-dynamic-replicator.yaml and
> > > arm,coresight-static-funnel.yaml
> > > - Update MAINTAINERS
> > > - Fix coresight.txt references
> >
> > What a massive undertaking... I have looked scrupulously and everything adds up.
> > Let me know if you were looking for me to pick this up. Otherwise:
> >
> > Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
>
> Can you apply. I think there was another series from QCom touching
> the MAINTAINERS entry that will conflict.
I just tried a rebased on today's linux-next and it didn't blow up.
>
> There's a couple of indentation fixups. Can you fix when applying or do
> you want me to resend?
Fixed and applied.
Thanks,
Mathieu
>
> Rob
prev parent reply other threads:[~2022-06-29 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 1:19 [PATCH v2 0/3] dt-bindings: Arm CoreSight binding schema conversions Rob Herring
2022-06-03 1:19 ` [PATCH v2 1/3] dt-bindings: arm: Rename Coresight filenames to match compatible Rob Herring
2022-06-03 1:19 ` [PATCH v2 2/3] dt-bindings: arm: Convert CoreSight bindings to DT schema Rob Herring
2022-06-20 17:17 ` Suzuki K Poulose
2022-06-27 20:11 ` Rob Herring
2022-06-27 21:55 ` Suzuki K Poulose
2022-06-03 1:19 ` [PATCH v2 3/3] dt-bindings: arm: Convert CoreSight CPU debug " Rob Herring
2022-06-27 21:56 ` Suzuki K Poulose
2022-06-20 16:55 ` [PATCH v2 0/3] dt-bindings: Arm CoreSight binding schema conversions Mathieu Poirier
2022-06-28 18:01 ` Rob Herring
2022-06-29 16:28 ` Mathieu Poirier [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=20220629162831.GB2013207@p14s \
--to=mathieu.poirier@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.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).