From: vikas <vikas.manocha@st.com>
To: Marek Vasut <marex@denx.de>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Graham Moore <grmoore@opensource.altera.com>,
Alan Tull <atull@opensource.altera.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Dinh Nguyen <dinguyen@opensource.altera.com>,
Yves Vandervennet <yvanderv@opensource.altera.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver.
Date: Thu, 27 Aug 2015 13:18:58 -0700 [thread overview]
Message-ID: <55DF70B2.3070204@st.com> (raw)
In-Reply-To: <201508272012.51185.marex@denx.de>
Hi,
On 08/27/2015 11:12 AM, Marek Vasut wrote:
> On Thursday, August 27, 2015 at 07:44:34 PM, vikas wrote:
>> Hi,
>>
>> On 08/21/2015 02:20 AM, Marek Vasut wrote:
>>> From: Graham Moore <grmoore@opensource.altera.com>
>>>
>>> Add binding document for the Cadence QSPI controller.
>>>
>>> Signed-off-by: Graham Moore <grmoore@opensource.altera.com>
>>> Signed-off-by: Marek Vasut <marex@denx.de>
>>> Cc: Alan Tull <atull@opensource.altera.com>
>>> Cc: Brian Norris <computersforpeace@gmail.com>
>>> Cc: David Woodhouse <dwmw2@infradead.org>
>>> Cc: Dinh Nguyen <dinguyen@opensource.altera.com>
>>> Cc: Graham Moore <grmoore@opensource.altera.com>
>>> Cc: Vikas MANOCHA <vikas.manocha@st.com>
>>> Cc: Yves Vandervennet <yvanderv@opensource.altera.com>
>>> Cc: devicetree@vger.kernel.org
>>> ---
>>>
>>> .../devicetree/bindings/mtd/cadence-quadspi.txt | 56
>>> ++++++++++++++++++++++ 1 file changed, 56 insertions(+)
>>> create mode 100644
>>> Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
>>>
>>> V2: Add cdns prefix to driver-specific bindings.
>>> V3: Use existing property "is-decoded-cs" instead of creating a
>>>
>>> duplicate, "ext-decoder". Timing parameters are in nanoseconds,
>>> not master reference clocks. Remove bus-num completely.
>>>
>>> V4: Add new properties fifo-width and trigger-address
>>> V7: - Prefix all of the Cadence-specific properties with cdns prefix,
>>>
>>> those are in particular "cdns,is-decoded-cs", "cdns,fifo-depth",
>>> "cdns,fifo-width", "cdns,trigger-address".
>>>
>>> - Drop bogus properties which were not used and were incorrect.
>>>
>>> V8: Align lines to 80 chars.
>>>
>>> diff --git a/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
>>> b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt new file
>>> mode 100644
>>> index 0000000..f248056
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
>>> @@ -0,0 +1,56 @@
>>> +* Cadence Quad SPI controller
>>> +
>>> +Required properties:
>>> +- compatible : Should be "cdns,qspi-nor".
>>> +- reg : Contains two entries, each of which is a tuple consisting of a
>>> + physical address and length. The first entry is the address and
>>> + length of the controller register set. The second entry is the
>>> + address and length of the QSPI Controller data area.
>>
>> still hooked up with "Controller data area", it is ambiguous.
>> Use something which is more clear: Nor Flash memory mapped address.
>
> I have to disagree, I will call it whatever it is called in the datasheet
> and it is called "controller data area".
It is preferable to use terminology which readers understand & that is the purpose
of explaining it here otherwise we could have just pasted the doc link.
I have to stop here for this point.
>
>>> +- interrupts : Unit interrupt specifier for the controller interrupt.
>>> +- clocks : phandle to the Quad SPI clock.
>>> +- cdns,fifo-depth : Size of the data FIFO in words.
>>> +- cdns,fifo-width : Bus width of the data FIFO in bytes.
>>> +- cdns,trigger-address : 32-bit indirect AHB trigger address.
>>> +
>>
>>> +Optional properties:
>> again, is it optional ? can the driver be used without these properties ?
>
> Why wouldn't it be possible to use the driver with no SPI NOR attached to
> it? It's a cornercase, but still a valid one.
that's not right, this controller is only spi flash controller.
>
>>> +- cdns,is-decoded-cs : Flag to indicate whether decoder is used or not.
>>
>> again, add info what the decoder is for ?
>
> This is something Graham has to clarify. Based on the code (I'm sure you did
> check the code), it's a 4:16 demuxer.
Please clarify if possible & add the info for others benefit. This part is not common in other spi/nor controllers.
>
>>> +
>>> +Optional subnodes:
>>> +Subnodes of the Cadence Quad SPI controller are spi slave nodes with
>>> additional +custom properties:
>>> +- cdns,read-delay : Delay for read capture logic, in clock cycles
>>> +- cdns,tshsl-ns : Delay in nanoseconds for the length that the master
>>> + mode chip select outputs are de-asserted between
>>> + transactions.
>>> +- cdns,tsd2d-ns : Delay in nanoseconds between one chip select being
>>> + de-activated and the activation of another.
>>> +- cdns,tchsh-ns : Delay in nanoseconds between last bit of current
>>> + transaction and deasserting the device chip select
>>> + (qspi_n_ss_out).
>>> +- cdns,tslch-ns : Delay in nanoseconds between setting qspi_n_ss_out low
>>> + and first bit transfer.
>>> +
>>> +Example:
>>> +
>>> + qspi: spi@ff705000 {
>>> + compatible = "cdns,qspi-nor";
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> + reg = <0xff705000 0x1000>,
>>> + <0xffa00000 0x1000>;
>>> + interrupts = <0 151 4>;
>>> + clocks = <&qspi_clk>;
>>> + cdns,is-decoded-cs;
>>
>> flag value ?
>
> Sorry, I don't quite understand the question. If you mean why there is no
> value, it's because this is a boolean OF node, which just does't need to
> have a value ; it's either present or not.
you are right, thanks.
Cheers,
Vikas
>
> Best regards,
> Marek Vasut
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: vikas <vikas.manocha-qxv4g6HH51o@public.gmane.org>
To: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
Cc: "linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Graham Moore
<grmoore-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>,
Alan Tull
<atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>,
Brian Norris
<computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Dinh Nguyen
<dinguyen-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>,
Yves Vandervennet
<yvanderv-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver.
Date: Thu, 27 Aug 2015 13:18:58 -0700 [thread overview]
Message-ID: <55DF70B2.3070204@st.com> (raw)
In-Reply-To: <201508272012.51185.marex-ynQEQJNshbs@public.gmane.org>
Hi,
On 08/27/2015 11:12 AM, Marek Vasut wrote:
> On Thursday, August 27, 2015 at 07:44:34 PM, vikas wrote:
>> Hi,
>>
>> On 08/21/2015 02:20 AM, Marek Vasut wrote:
>>> From: Graham Moore <grmoore-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
>>>
>>> Add binding document for the Cadence QSPI controller.
>>>
>>> Signed-off-by: Graham Moore <grmoore-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
>>> Signed-off-by: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
>>> Cc: Alan Tull <atull-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
>>> Cc: Brian Norris <computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>>> Cc: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
>>> Cc: Dinh Nguyen <dinguyen-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
>>> Cc: Graham Moore <grmoore-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
>>> Cc: Vikas MANOCHA <vikas.manocha-qxv4g6HH51o@public.gmane.org>
>>> Cc: Yves Vandervennet <yvanderv-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
>>> Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>>> ---
>>>
>>> .../devicetree/bindings/mtd/cadence-quadspi.txt | 56
>>> ++++++++++++++++++++++ 1 file changed, 56 insertions(+)
>>> create mode 100644
>>> Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
>>>
>>> V2: Add cdns prefix to driver-specific bindings.
>>> V3: Use existing property "is-decoded-cs" instead of creating a
>>>
>>> duplicate, "ext-decoder". Timing parameters are in nanoseconds,
>>> not master reference clocks. Remove bus-num completely.
>>>
>>> V4: Add new properties fifo-width and trigger-address
>>> V7: - Prefix all of the Cadence-specific properties with cdns prefix,
>>>
>>> those are in particular "cdns,is-decoded-cs", "cdns,fifo-depth",
>>> "cdns,fifo-width", "cdns,trigger-address".
>>>
>>> - Drop bogus properties which were not used and were incorrect.
>>>
>>> V8: Align lines to 80 chars.
>>>
>>> diff --git a/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
>>> b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt new file
>>> mode 100644
>>> index 0000000..f248056
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/mtd/cadence-quadspi.txt
>>> @@ -0,0 +1,56 @@
>>> +* Cadence Quad SPI controller
>>> +
>>> +Required properties:
>>> +- compatible : Should be "cdns,qspi-nor".
>>> +- reg : Contains two entries, each of which is a tuple consisting of a
>>> + physical address and length. The first entry is the address and
>>> + length of the controller register set. The second entry is the
>>> + address and length of the QSPI Controller data area.
>>
>> still hooked up with "Controller data area", it is ambiguous.
>> Use something which is more clear: Nor Flash memory mapped address.
>
> I have to disagree, I will call it whatever it is called in the datasheet
> and it is called "controller data area".
It is preferable to use terminology which readers understand & that is the purpose
of explaining it here otherwise we could have just pasted the doc link.
I have to stop here for this point.
>
>>> +- interrupts : Unit interrupt specifier for the controller interrupt.
>>> +- clocks : phandle to the Quad SPI clock.
>>> +- cdns,fifo-depth : Size of the data FIFO in words.
>>> +- cdns,fifo-width : Bus width of the data FIFO in bytes.
>>> +- cdns,trigger-address : 32-bit indirect AHB trigger address.
>>> +
>>
>>> +Optional properties:
>> again, is it optional ? can the driver be used without these properties ?
>
> Why wouldn't it be possible to use the driver with no SPI NOR attached to
> it? It's a cornercase, but still a valid one.
that's not right, this controller is only spi flash controller.
>
>>> +- cdns,is-decoded-cs : Flag to indicate whether decoder is used or not.
>>
>> again, add info what the decoder is for ?
>
> This is something Graham has to clarify. Based on the code (I'm sure you did
> check the code), it's a 4:16 demuxer.
Please clarify if possible & add the info for others benefit. This part is not common in other spi/nor controllers.
>
>>> +
>>> +Optional subnodes:
>>> +Subnodes of the Cadence Quad SPI controller are spi slave nodes with
>>> additional +custom properties:
>>> +- cdns,read-delay : Delay for read capture logic, in clock cycles
>>> +- cdns,tshsl-ns : Delay in nanoseconds for the length that the master
>>> + mode chip select outputs are de-asserted between
>>> + transactions.
>>> +- cdns,tsd2d-ns : Delay in nanoseconds between one chip select being
>>> + de-activated and the activation of another.
>>> +- cdns,tchsh-ns : Delay in nanoseconds between last bit of current
>>> + transaction and deasserting the device chip select
>>> + (qspi_n_ss_out).
>>> +- cdns,tslch-ns : Delay in nanoseconds between setting qspi_n_ss_out low
>>> + and first bit transfer.
>>> +
>>> +Example:
>>> +
>>> + qspi: spi@ff705000 {
>>> + compatible = "cdns,qspi-nor";
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> + reg = <0xff705000 0x1000>,
>>> + <0xffa00000 0x1000>;
>>> + interrupts = <0 151 4>;
>>> + clocks = <&qspi_clk>;
>>> + cdns,is-decoded-cs;
>>
>> flag value ?
>
> Sorry, I don't quite understand the question. If you mean why there is no
> value, it's because this is a boolean OF node, which just does't need to
> have a value ; it's either present or not.
you are right, thanks.
Cheers,
Vikas
>
> Best regards,
> Marek Vasut
> .
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-08-27 20:18 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 9:20 [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver Marek Vasut
2015-08-21 9:20 ` Marek Vasut
2015-08-21 9:20 ` [PATCH 2/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller Marek Vasut
2015-08-21 9:20 ` Marek Vasut
2015-08-25 22:09 ` vikas
2015-08-25 22:09 ` vikas
2015-08-26 6:19 ` Marek Vasut
2015-08-26 6:19 ` Marek Vasut
2015-08-26 15:47 ` vikas
2015-08-26 15:47 ` vikas
2015-08-26 16:39 ` Marek Vasut
2015-08-26 16:39 ` Marek Vasut
2015-08-26 18:06 ` Brian Norris
2015-08-26 18:06 ` Brian Norris
2015-08-26 23:05 ` vikas
2015-08-26 23:05 ` vikas
2015-08-31 17:30 ` Graham Moore
2015-08-31 17:30 ` Graham Moore
2015-08-31 22:36 ` Marek Vasut
2015-08-31 22:36 ` Marek Vasut
2015-09-04 23:45 ` vikas
2015-09-04 23:45 ` vikas
2015-09-06 15:16 ` Marek Vasut
2015-09-06 15:16 ` Marek Vasut
2015-09-07 18:56 ` vikas
2015-09-07 18:56 ` vikas
2015-09-07 20:27 ` vikas
2015-09-07 20:27 ` vikas
2015-10-15 14:10 ` Graham Moore
2015-10-15 14:10 ` Graham Moore
2015-10-15 14:27 ` Marek Vasut
2015-10-15 14:27 ` Marek Vasut
2016-01-11 4:14 ` [2/2] " R, Vignesh
2016-01-11 4:14 ` R, Vignesh
2016-01-11 4:50 ` Marek Vasut
2016-01-11 4:50 ` Marek Vasut
2016-01-12 4:59 ` Vignesh R
2016-01-12 4:59 ` Vignesh R
2016-01-12 13:50 ` Marek Vasut
2016-01-12 13:50 ` Marek Vasut
2015-08-27 17:44 ` [PATCH V8 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver vikas
2015-08-27 17:44 ` vikas
2015-08-27 18:12 ` Marek Vasut
2015-08-27 18:12 ` Marek Vasut
2015-08-27 20:18 ` vikas [this message]
2015-08-27 20:18 ` vikas
-- strict thread matches above, loose matches on Subject: below --
2016-01-11 4:34 Marek Vasut
2016-01-11 4:34 ` Marek Vasut
2016-01-11 16:06 ` Dinh Nguyen
2016-01-11 16:06 ` Dinh Nguyen
2016-01-11 16:32 ` Marek Vasut
2016-01-11 16:32 ` Marek Vasut
2016-01-11 17:03 ` Dinh Nguyen
2016-01-11 17:03 ` Dinh Nguyen
2016-01-11 17:27 ` Marek Vasut
2016-01-11 17:27 ` Marek Vasut
2016-01-13 2:26 ` Rob Herring
2016-01-13 2:26 ` Rob Herring
2016-01-13 2:39 ` Marek Vasut
2016-01-13 2:39 ` Marek Vasut
2016-02-01 21:03 ` Brian Norris
2016-02-01 21:03 ` Brian Norris
2016-02-01 21:13 ` Marek Vasut
2016-02-01 21:13 ` Marek Vasut
2016-02-04 7:38 ` Vignesh R
2016-02-04 7:38 ` Vignesh R
2016-02-04 11:25 ` Marek Vasut
2016-02-04 11:25 ` Marek Vasut
2016-02-04 17:04 ` Dinh Nguyen
2016-02-04 17:04 ` Dinh Nguyen
2016-02-06 7:42 ` Marek Vasut
2016-02-06 7:42 ` Marek Vasut
2016-02-04 17:30 ` R, Vignesh
2016-02-04 17:30 ` R, Vignesh
2016-02-06 7:42 ` Marek Vasut
2016-02-06 7:42 ` Marek Vasut
2016-02-08 11:19 ` Vignesh R
2016-02-08 11:19 ` Vignesh R
2016-02-08 15:27 ` Marek Vasut
2016-02-08 15:27 ` Marek Vasut
2016-02-10 16:10 ` Graham Moore
2016-02-10 16:10 ` Graham Moore
2016-02-10 16:17 ` Marek Vasut
2016-02-10 16:17 ` Marek Vasut
2016-03-10 20:55 ` Graham Moore
2016-03-10 20:55 ` Graham Moore
2016-03-10 21:10 ` Marek Vasut
2016-03-10 21:10 ` Marek Vasut
2016-03-14 18:17 ` Graham Moore
2016-03-14 18:17 ` Graham Moore
2016-03-14 22:47 ` Marek Vasut
2016-03-14 22:47 ` Marek Vasut
2016-06-04 0:39 Marek Vasut
2016-06-04 0:39 ` Marek Vasut
2016-06-07 14:00 ` Rob Herring
2016-06-07 14:00 ` Rob Herring
2016-07-18 17:00 ` Brian Norris
2016-07-18 17:00 ` Brian Norris
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=55DF70B2.3070204@st.com \
--to=vikas.manocha@st.com \
--cc=atull@opensource.altera.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@opensource.altera.com \
--cc=dwmw2@infradead.org \
--cc=grmoore@opensource.altera.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=yvanderv@opensource.altera.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.