From: Rob Herring <robh@kernel.org>
To: Pratyush Yadav <p.yadav@ti.com>
Cc: Kuldeep Singh <kuldeep.singh@nxp.com>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Vladimir Oltean <olteanv@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: spi: Convert Freescale DSPI to json schema
Date: Wed, 24 Mar 2021 12:10:37 -0600 [thread overview]
Message-ID: <20210324181037.GB3320002@robh.at.kernel.org> (raw)
In-Reply-To: <20210315183051.ugvmz4zqrvuo6iqq@ti.com>
On Tue, Mar 16, 2021 at 12:00:52AM +0530, Pratyush Yadav wrote:
> +Cc mtd list
>
> Hi,
>
> On 15/03/21 05:45PM, Kuldeep Singh wrote:
> > Convert the Freescale DSPI binding to DT schema format using json-schema.
> >
> > Signed-off-by: Kuldeep Singh <kuldeep.singh@nxp.com>
> > ---
> > Hi Rob,
> > This patch is checked with following commands with no warnings observed.
> > make distclean; make allmodconfig;
> > make dt_binding_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/spi/fsl,spi-fsl-dspi.yaml;
> > make dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/spi/fsl,spi-fsl-dspi.yaml
>
> When I add the "fsl,spi-cs-sck-delay" property under the flash@0 node in
> the example and run dt_binding_check, I see the below error:
>
> /home/pratyush/src/linux/Documentation/devicetree/bindings/spi/fsl,spi-fsl-dspi.example.dt.yaml: flash@0: 'fsl,spi-cs-sck-delay' does not match any of the regexes: '^partition@', 'pinctrl-[0-9]+'
> From schema: /home/pratyush/src/lin/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
>
> I am trying to solve a similar problem for the Cadence QSPI controller
> binding and I wonder what the best solution for this is. The obvious one
> would be to add these properties to jedec,spi-nor.yaml. I haven't
> managed to come up with any other solution to this problem.
>
> Rob, all, any suggestions on how to best model this?
I'm aware of the issue, but I don't have a solution for this situation.
It's a problem anywhere we have a parent or bus binding defining
properties for child nodes. For now, I'd just avoid it in the examples
and we'll figure out how to deal with actual dts files later.
For this one in particular, CS to clock timing isn't any FSL or
controller specific, but is device specific. So this probably should
have been a generic spi bus property (if not implicit). That's somewhat
easier to work-around than potentially adding controller specific
properties to every slave device schema.
Rob
next prev parent reply other threads:[~2021-03-24 18:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 12:15 [PATCH] dt-bindings: spi: Convert Freescale DSPI to json schema Kuldeep Singh
2021-03-15 18:30 ` Pratyush Yadav
2021-03-16 5:56 ` [EXT] " Kuldeep Singh
2021-03-16 17:45 ` Michael Walle
2021-03-16 18:06 ` Pratyush Yadav
2021-03-16 18:22 ` Michael Walle
2021-03-24 17:51 ` Rob Herring
2021-03-22 13:20 ` Pratyush Yadav
2021-03-24 18:10 ` Rob Herring [this message]
2021-03-15 20:54 ` Vladimir Oltean
2021-03-16 6:08 ` [EXT] " Kuldeep Singh
2021-03-16 10:15 ` Vladimir Oltean
2021-03-24 18:14 ` Rob Herring
2021-03-24 18:53 ` Vladimir Oltean
2021-03-24 19:20 ` Rob Herring
2021-03-25 1:06 ` Vladimir Oltean
2021-03-24 18:18 ` 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=20210324181037.GB3320002@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuldeep.singh@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=p.yadav@ti.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).