From: ChiaWei Wang <chiawei_wang@aspeedtech.com>
To: Rob Herring <robh@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"yulei.sh@bytedance.com" <yulei.sh@bytedance.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"osk@google.com" <osk@google.com>
Subject: RE: [PATCH v3 1/3] dt-bindings: aspeed: Add UART routing controller
Date: Mon, 13 Sep 2021 01:15:58 +0000 [thread overview]
Message-ID: <HK0PR06MB3779641C22C5A07EAFCE91EB91D99@HK0PR06MB3779.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <CAL_JsqLdT3U2k8Znjo0LHUtC41vPidR4ZDDhcRPpxDC7atgEug@mail.gmail.com>
> From: Rob Herring <robh@kernel.org>
> Sent: Friday, September 10, 2021 11:58 PM
>
> On Thu, Sep 9, 2021 at 8:38 PM ChiaWei Wang
> <chiawei_wang@aspeedtech.com> wrote:
> >
> > Hi Rob,
> >
> > > From: Rob Herring <robh@kernel.org>
> > > Sent: Thursday, September 9, 2021 8:33 PM
> > >
> > > On Thu, 09 Sep 2021 18:29:05 +0800, Chia-Wei Wang wrote:
> > > > Add dt-bindings for Aspeed UART routing controller.
> > > >
> > > > Signed-off-by: Oskar Senft <osk@google.com>
> > > > Signed-off-by: Chia-Wei Wang <chiawei_wang@aspeedtech.com>
> > > > ---
> > > > .../bindings/soc/aspeed/uart-routing.yaml | 70
> > > +++++++++++++++++++
> > > > 1 file changed, 70 insertions(+)
> > > > create mode 100644
> > > > Documentation/devicetree/bindings/soc/aspeed/uart-routing.yaml
> > > >
> > >
> > > My bot found errors running 'make DT_CHECKER_FLAGS=-m
> > > dt_binding_check'
> > > on your patch (DT_CHECKER_FLAGS is new in v5.13):
> > >
> > > yamllint warnings/errors:
> > >
> > > dtschema/dtc warnings/errors:
> > >
> Documentation/devicetree/bindings/soc/aspeed/uart-routing.example.dt.yaml:
> > > 0:0: /example-0/lpc@1e789000: failed to match any schema with
> compatible:
> > > ['aspeed,ast2600-lpc-v2', 'simple-mfd', 'syscon']
> >
> > The "aspeed,ast2600-lpc-v2" compatible string is described in the .txt file
> 'aspeed-lpc.txt'.
> > Do we have to firstly convert the text file into YAML one to resolve this
> dependency issue?
>
> Yes. This is a significant change to the LPC block binding.
Understood. Will send a v4 patch which includes the YAML conversion.
Thanks.
Chiawei
next prev parent reply other threads:[~2021-09-13 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 10:29 [PATCH v3 0/3] arm: aspeed: Add UART routing support Chia-Wei Wang
2021-09-09 10:29 ` [PATCH v3 1/3] dt-bindings: aspeed: Add UART routing controller Chia-Wei Wang
2021-09-09 12:32 ` Rob Herring
2021-09-10 1:38 ` ChiaWei Wang
2021-09-10 15:57 ` Rob Herring
2021-09-13 1:15 ` ChiaWei Wang [this message]
2021-09-09 10:29 ` [PATCH v3 2/3] soc: aspeed: Add UART routing support Chia-Wei Wang
2021-09-09 10:29 ` [PATCH v3 3/3] ARM: dts: aspeed: Add uart routing to device tree Chia-Wei Wang
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=HK0PR06MB3779641C22C5A07EAFCE91EB91D99@HK0PR06MB3779.apcprd06.prod.outlook.com \
--to=chiawei_wang@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=osk@google.com \
--cc=robh@kernel.org \
--cc=yulei.sh@bytedance.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).