[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230706-syndrome-wise-c1097518f2c6@wendy>
Date: Thu, 6 Jul 2023 07:44:42 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: 运辉崔 <cuiyunhui@...edance.com>
CC: Conor Dooley <conor@...nel.org>, <robh+dt@...nel.org>,
<krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
<devicetree@...r.kernel.org>, <sunilvl@...tanamicro.com>,
<ardb@...nel.org>, <palmer@...belt.com>,
<paul.walmsley@...ive.com>, <aou@...s.berkeley.edu>,
<linux-riscv@...ts.infradead.org>, <rminnich@...il.com>,
<mark.rutland@....com>, <lpieralisi@...nel.org>,
<rafael@...nel.org>, <lenb@...nel.org>, <jdelvare@...e.com>,
<yc.hung@...iatek.com>, <angelogioacchino.delregno@...labora.com>,
<allen-kh.cheng@...iatek.com>,
<pierre-louis.bossart@...ux.intel.com>,
<tinghan.shen@...iatek.com>, <linux-kernel@...r.kernel.org>,
<linux-acpi@...r.kernel.org>, <geshijian@...edance.com>,
<weidong.wd@...edance.com>
Subject: Re: [External] Re: [PATCH v3 4/4] dt-bindings: firmware: Document
ffitbl binding
On Thu, Jul 06, 2023 at 11:43:55AM +0800, 运辉崔 wrote:
> On Wed, Jul 5, 2023 at 11:07 PM Conor Dooley <conor@...nel.org> wrote:
> > On Wed, Jul 05, 2023 at 07:42:51PM +0800, Yunhui Cui wrote:
> > > Add the description for ffitbl subnode.
> > >
> > > Signed-off-by: Yunhui Cui <cuiyunhui@...edance.com>
> > > ---
> > > .../devicetree/bindings/firmware/ffitbl.txt | 27 +++++++++++++++++++
> > > MAINTAINERS | 1 +
> > > 2 files changed, 28 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/firmware/ffitbl.txt
> > >
> > > diff --git a/Documentation/devicetree/bindings/firmware/ffitbl.txt b/Documentation/devicetree/bindings/firmware/ffitbl.txt
> > > new file mode 100644
> > > index 000000000000..c42368626199
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/firmware/ffitbl.txt
> >
> > Firstly, new dt-bindings need to be done in yaml, not in text form.
> > Secondly, you didn't re-run get_maintainer.pl after adding this binding,
> > so you have not CCed any of the other dt-binding maintainers nor the
> > devicetree mailing list.
>
> Re-run get_maintainer.pl and added maintainers into the maillist.
> emm.. There is some *txt in
> Documentation/devicetree/bindings/firmware/, isn't it?
There might be, but that's not an excuse for adding _new_ ones, sorry.
> > > +FFI(FDT FIRMWARE INTERFACE) driver
> > > +
> > > +Required properties:
> > > + - entry : acpi or smbios root pointer, u64
> > > + - reg : acpi or smbios version, u32
> >
> > Please go look at any other dt-binding (or the example schema) as to how
> > these properties should be used. A "reg" certainly should not be being
> > used to store the revision...
>
> Okay, If so,I'll add a property "version" into the dts instead of
> "reg", just like, WDYT?
> ffitbl {
Firstly, I'd much rather you spelt this out, like "ffi-table".
> smbios {
> entry = "";
I still don't understand why "entry", which is an address, is being
represented by an empty string.
I also don't really get why you have not used "reg" to describe its
start address and size.
> version = < 0x02 >;
Probably missing a vendor prefix, and the spaces are unusual, but better
than it was, yes.
> }
> acpi {
> entry = "";
> version = < 0x06 >;
> }
> }
Thanks,
Conor.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists