From: Marek Vasut <marex@denx.de>
To: vikas <vikas.manocha@st.com>
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 V7 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver.
Date: Tue, 18 Aug 2015 06:47:30 +0200 [thread overview]
Message-ID: <201508180647.30119.marex@denx.de> (raw)
In-Reply-To: <55D29A0B.20408@st.com>
On Tuesday, August 18, 2015 at 04:35:55 AM, vikas wrote:
> Hi Marek,
>
> On 08/13/2015 08:28 PM, 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 | 50
> > ++++++++++++++++++++++ 1 file changed, 50 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.
> >
> > diff --git a/Documentation/devicetree/bindings/mtd/cadence_quadspi.txt
> > b/Documentation/devicetree/bindings/mtd/cadence_quadspi.txt new file
> > mode 100644
> > index 0000000..ebaf1fd
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mtd/cadence_quadspi.txt
> > @@ -0,0 +1,50 @@
> > +* 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.
>
> "Controller data area", i think it means mapped NOR Flash address ?
Probably ; Graham ?
> If yes, it would be more clear with "Physical base address & size of NOR
> Flash".
This is the Direct mode thing, correct ? We don't support this, so I think
we should drop this bit altogether and keep only one single address in this
field.
> > +- 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.
>
> It actually is sram-depth, better would be "sram-depth" to avoid confusion.
Is there any documentation for this piece to which you can point me ?
> > +- cdns,fifo-width: Bus width of the data FIFO in bytes.
> > +- cdns,trigger-address : 32-bit indirect AHB trigger address.
>
> we might make trigger-address also part of property "reg".
No, we cannot, it's not part of the controller's base address, is it ?
> > +
> > +Optional properties:
> > +- cdns,is-decoded-cs : Flag to indicate whether decoder is used or not.
>
> Not clear about the usage of decoder, if it does not make sense we might
> remove it from driver.
Graham ? SoCFPGA uses this decoded-cs thing, so we absolutely can not remove
it from the driver.
> > +Optional subnodes:
> I think flash subnode is mandatory.
You can have a controller with no SPI NORs on it.
next prev parent reply other threads:[~2015-08-18 4:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 3:28 [PATCH V7 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver Marek Vasut
2015-08-14 3:28 ` [PATCH V7 2/2] mtd: spi-nor: Add driver for Cadence Quad SPI Flash Controller Marek Vasut
2015-08-14 3:32 ` Marek Vasut
2015-08-18 2:47 ` Brian Norris
2015-08-21 5:32 ` Marek Vasut
2015-08-18 2:34 ` vikas
2015-08-18 19:17 ` Graham Moore
2015-08-18 20:35 ` vikas
2015-08-21 4:04 ` Marek Vasut
2015-08-21 7:09 ` Vikas MANOCHA
2015-08-18 2:35 ` [PATCH V7 1/2] mtd: spi-nor: Bindings for Cadence Quad SPI Flash Controller driver vikas
2015-08-18 4:47 ` Marek Vasut [this message]
2015-08-18 5:48 ` Vikas MANOCHA
2015-08-18 19:03 ` Graham Moore
2015-08-18 20:18 ` vikas
2015-08-20 4:03 ` Marek Vasut
2015-08-20 16:06 ` vikas
2015-08-21 3:46 ` Marek Vasut
2015-08-21 7:00 ` Vikas MANOCHA
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=201508180647.30119.marex@denx.de \
--to=marex@denx.de \
--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=vikas.manocha@st.com \
--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 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).