From: Michael Walle <michael@walle.cc>
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>,
Rob Herring <robh+dt@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: Tue, 16 Mar 2021 18:45:49 +0100 [thread overview]
Message-ID: <067c42f3726578ebe60d201a141dfdb6@walle.cc> (raw)
In-Reply-To: <20210315183051.ugvmz4zqrvuo6iqq@ti.com>
Am 2021-03-15 19:30, schrieb Pratyush Yadav:
..
>> +patternProperties:
>> + "@[0-9a-f]+":
Shouldn't this be "^.*@[0-9a-f]+$"?
>> + type: object
>> +
>> + properties:
>> + fsl,spi-cs-sck-delay:
>> + description:
>> + Delay in nanoseconds between activating chip select and the
>> start of
>> + clock signal, at the start of a transfer.
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> +
>> + fsl,spi-sck-cs-delay:
>> + description:
>> + Delay in nanoseconds between stopping the clock signal and
>> + deactivating chip select, at the end of a transfer.
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> +
..
-michael
next prev parent reply other threads:[~2021-03-16 17:46 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 [this message]
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
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=067c42f3726578ebe60d201a141dfdb6@walle.cc \
--to=michael@walle.cc \
--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 \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).