From: Marek Vasut <marek.vasut@gmail.com>
To: Yogesh Gaur <yogeshnarayan.gaur@nxp.com>, linux-mtd@lists.infradead.org
Cc: boris.brezillon@free-electrons.com, cyrille.pitchen@wedev4u.fr,
computersforpeace@gmail.com, han.xu@nxp.com, festevam@gmail.com,
frieder.schrempf@exceet.de, suresh.gupta@nxp.com
Subject: Re: [RFC PATCH 0/4] mtd: spi-nor: Add NXP FlexSPI driver
Date: Wed, 4 Apr 2018 12:28:30 +0200 [thread overview]
Message-ID: <8a8cf9f4-61ae-ebd3-cb0f-117206f5fac3@gmail.com> (raw)
In-Reply-To: <1522836371-2828-1-git-send-email-yogeshnarayan.gaur@nxp.com>
On 04/04/2018 12:06 PM, Yogesh Gaur wrote:
> Add NXP FlexSPI driver
>
> NXP uses FlexSPI controller.
> The FlexSPI(Flex Serial Peripheral controller) acts as an interface
> to external serial flash devices, maximum 4, each with upto 8 bidirectional
> data lines.
>
> (1) The FlexSPI controller is driven by the LUT(Look-up Table) registers.
> The LUT registers are a look-up-table for sequences of instructions.
> A valid sequence consists of four LUT registers.
>
> (2) The definition of the LUT register shows below:
> ---------------------------------------------------
> | INSTR1 | PAD1 | OPRND1 | INSTR0 | PAD0 | OPRND0 |
> ---------------------------------------------------
Is this IP somehow related todrivers/mtd/spi-nor/fsl-quadspi.c ?
--
Best regards,
Marek Vasut
prev parent reply other threads:[~2018-04-04 10:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 10:06 [RFC PATCH 0/4] mtd: spi-nor: Add NXP FlexSPI driver Yogesh Gaur
2018-04-04 10:06 ` [RFC PATCH 1/4] mtd: spi-nor: Add entry for mt35xu512aba flash Yogesh Gaur
2018-04-04 10:35 ` Marek Vasut
2018-04-04 10:06 ` [RFC PATCH 2/4] spi: add flags for octal I/O data transfer Yogesh Gaur
2018-04-04 10:06 ` [RFC PATCH 3/4] dt-bindings: Add binding file for NXP FlexSPI driver Yogesh Gaur
2018-04-04 10:37 ` Marek Vasut
2018-04-04 10:06 ` [RFC PATCH 4/4] mtd: spi-nor: Add " Yogesh Gaur
2018-04-04 10:58 ` Vignesh R
2018-04-04 10:28 ` Marek Vasut [this message]
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=8a8cf9f4-61ae-ebd3-cb0f-117206f5fac3@gmail.com \
--to=marek.vasut@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@exceet.de \
--cc=han.xu@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=suresh.gupta@nxp.com \
--cc=yogeshnarayan.gaur@nxp.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.