From: "Ramuthevar, Vadivel MuruganX" <vadivel.muruganx.ramuthevar@linux.intel.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
broonie@kernel.org, robh+dt@kernel.org
Cc: devicetree@vger.kernel.org, boris.brezillon@free-electrons.com,
simon.k.r.goldschmidt@gmail.com, dinguyen@kernel.org,
tien.fong.chee@intel.com, marex@denx.de,
linux-mtd@lists.infradead.org, dwmw2@infradead.org,
richard@nod.at, computersforpeace@gmail.com,
cyrille.pitchen@atmel.com, david.oberhollenzer@sigma-star.at,
miquel.raynal@bootlin.com, tudor.ambarus@gmail.com,
cheol.yong.kim@intel.com, qi-ming.wu@intel.com
Subject: Re: [PATCH v12 1/4] dt-bindings: spi: Add schema for Cadence QSPI Controller driver
Date: Fri, 20 Mar 2020 14:19:37 +0800 [thread overview]
Message-ID: <13a92ddd-b7dd-0465-d747-cda9bca21dbf@linux.intel.com> (raw)
In-Reply-To: <c2ad909e-9042-6ba0-7213-83346c6b9908@ti.com>
Hi,
On 20/3/2020 2:05 pm, Vignesh Raghavendra wrote:
>
> On 10/03/20 7:22 am, Ramuthevar,Vadivel MuruganX wrote:
>> From: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>>
>> Add dt-bindings documentation for Cadence-QSPI controller to support
>> spi based flash memories.
>>
>> Signed-off-by: Ramuthevar Vadivel Murugan <vadivel.muruganx.ramuthevar@linux.intel.com>
>> ---
>> .../devicetree/bindings/mtd/cadence-quadspi.txt | 67 -----------
>> .../devicetree/bindings/spi/cdns,qspi-nor.yaml | 127 +++++++++++++++++++++
>> 2 files changed, 127 insertions(+), 67 deletions(-)
>> delete mode 100644 Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
>> create mode 100644 Documentation/devicetree/bindings/spi/cdns,qspi-nor.yaml
>>
> [...]
>
>> +
>> +# subnode's properties
>> +patternProperties:
>> + "^.*@[0-9a-fA-F]+$":
>> + type: object
>> + description:
>> + flash device uses the subnodes below defined properties.
>> +
>> + cdns,read-delay:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description:
>> + Delay in 4 microseconds, read capture logic, in clock cycles.
>
> Not its not... See the old binding description please:
>
> -- cdns,read-delay : Delay for read capture logic, in clock cycles
>
> There is no mention of 4us. Range is 0x0 - 0xF
Sure, will update as you have suggested.
>> +
>> + cdns,tshsl-ns:
>> + description: |
>> + Delay in 50 nanoseconds, for the length that the master mode chip select
>> + outputs are de-asserted between transactions.
> Again see the description in old binding file:
>
> cdns,tshsl-ns : Delay in nanoseconds for the length that the master
> mode chip select outputs are de-asserted between
> transactions.
>
> Need not be 50ns or its multiple
Sure, will update as you have suggested.
>> +
>> + cdns,tsd2d-ns:
>> + description: |
>> + Delay in 50 nanoseconds, between one chip select being de-activated
>> + and the activation of another.
>> +
> same here
>
>> + cdns,tchsh-ns:
>> + description: |
>> + Delay in 4 nanoseconds, between last bit of current transaction and
>> + deasserting the device chip select (qspi_n_ss_out).
>> +
> Same here... Need not be 4ns...
>
>> + cdns,tslch-ns:
>> + description: |
>> + Delay in 4 nanoseconds, between setting qspi_n_ss_out low and
>> + first bit transfer.
>
> Same here...
>
> Above four values ( cdns,*-ns) come directly from the flash datasheets.
>
> These values are converted appropriate number of cycles depending upon
> the QSPI ref_clk frequency. So, there is no easy way to express the
> constraint (or range) in DT schema. I would recommend to just stick with
> the description that is there in the old binding file without any
> modifications.
Noted, will update.
Regards
Vadivel
>
> Regards
> Vignesh
next prev parent reply other threads:[~2020-03-20 6:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 1:52 [PATCH v12 0/4] spi: cadence-quadspi: Add support for the Cadence QSPI controller Ramuthevar,Vadivel MuruganX
2020-03-10 1:52 ` [PATCH v12 1/4] dt-bindings: spi: Add schema for Cadence QSPI Controller driver Ramuthevar,Vadivel MuruganX
2020-03-19 18:44 ` Rob Herring
2020-03-20 2:33 ` Ramuthevar, Vadivel MuruganX
2020-03-20 6:05 ` Vignesh Raghavendra
2020-03-20 6:19 ` Ramuthevar, Vadivel MuruganX [this message]
2020-03-10 1:52 ` [PATCH v12 2/4] mtd: spi-nor: add spi-mem support in cadence-quadspi controller driver Ramuthevar,Vadivel MuruganX
2020-03-19 8:09 ` Tudor.Ambarus
2020-03-19 9:30 ` Vignesh Raghavendra
2020-03-10 1:52 ` [PATCH v12 3/4] spi: cadence-quadspi: Add support for the Cadence QSPI controller Ramuthevar,Vadivel MuruganX
2020-03-10 1:52 ` [PATCH v12 4/4] spi: cadence-quadspi: Add qspi support for Intel LGM SoC Ramuthevar,Vadivel MuruganX
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=13a92ddd-b7dd-0465-d747-cda9bca21dbf@linux.intel.com \
--to=vadivel.muruganx.ramuthevar@linux.intel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=cheol.yong.kim@intel.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=david.oberhollenzer@sigma-star.at \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=marex@denx.de \
--cc=miquel.raynal@bootlin.com \
--cc=qi-ming.wu@intel.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=tien.fong.chee@intel.com \
--cc=tudor.ambarus@gmail.com \
--cc=vigneshr@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).