From: Frank Li <Frank.li@nxp.com>
To: Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
"open list:MEMORY CONTROLLER DRIVERS"
<linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH v2 1/1] dt-binding: memory-controllers: fsl,ifc: add compatible string fsl,ifc-nand
Date: Tue, 20 Aug 2024 14:11:26 -0400 [thread overview]
Message-ID: <ZsTcTt3Fu9ttcoYw@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20240818153914.GA120816-robh@kernel.org>
On Sun, Aug 18, 2024 at 09:39:14AM -0600, Rob Herring wrote:
> On Wed, Aug 14, 2024 at 05:29:57PM -0400, Frank Li wrote:
> > ifc can connect nor, nand and fpag. Add child node "nand@" under fsl,ifc
> > and compatible string "fsl,ifc-nand" when ifc connect to nand flash.
> >
> > Fix below warning:
> > arch/arm64/boot/dts/freescale/fsl-ls1043a-qds.dtb: /soc/memory-controller@1530000/nand@1,0:
> > failed to match any schema with compatible: ['fsl,ifc-nand']
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> > Change from v1 to v2
> > - add address-cells and size-cells
> > ---
> > .../memory-controllers/fsl/fsl,ifc.yaml | 21 +++++++++++++++++++
> > 1 file changed, 21 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/memory-controllers/fsl/fsl,ifc.yaml b/Documentation/devicetree/bindings/memory-controllers/fsl/fsl,ifc.yaml
> > index d1c3421bee107..c12bb7f51db62 100644
> > --- a/Documentation/devicetree/bindings/memory-controllers/fsl/fsl,ifc.yaml
> > +++ b/Documentation/devicetree/bindings/memory-controllers/fsl/fsl,ifc.yaml
> > @@ -58,6 +58,27 @@ properties:
> > access window as configured.
> >
> > patternProperties:
> > + "^nand@[a-f0-9]+(,[a-f0-9]+)+$":
> > + type: object
> > + properties:
> > + compatible:
> > + const: fsl,ifc-nand
> > +
> > + reg:
> > + maxItems: 1
> > +
> > + "#address-cells":
> > + const: 1
> > +
> > + "#size-cells":
> > + const: 1
>
> These only apply to child nodes, but you've disabled any child nodes.
I will add mtd partition for it.
>
> > +
> > + required:
> > + - compatible
> > + - reg
> > +
> > + additionalProperties: false
>
> You could minimally make this 'type: object' instead of false.
Sorry, I have not understood your means. I already set nand@*** as object.
nand@[a-f0-9]+(,[a-f0-9]+)+$":
type: object
>
> Or does this follow the nand controller and chip bindings? May not being
> older binding.
I check if-nand driver, which have not parse other nand controller's
property yet.
Frank
>
> > +
> > "^.*@[a-f0-9]+(,[a-f0-9]+)+$":
> > type: object
> > description: |
> > --
> > 2.34.1
> >
next prev parent reply other threads:[~2024-08-20 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 21:29 [PATCH v2 1/1] dt-binding: memory-controllers: fsl,ifc: add compatible string fsl,ifc-nand Frank Li
2024-08-18 15:39 ` Rob Herring
2024-08-20 18:11 ` Frank Li [this message]
2024-08-19 19:57 ` Krzysztof Kozlowski
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=ZsTcTt3Fu9ttcoYw@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
/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