From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com,
linux-mtd@lists.infradead.org, john@phrozen.org
Subject: Re: [PATCH v3 1/8] MTD: xway: add some more documentation
Date: Sun, 19 Jun 2016 18:14:43 +0200 [thread overview]
Message-ID: <20160619181443.07ea27ba@bbrezillon> (raw)
In-Reply-To: <1466352497-6806-2-git-send-email-hauke@hauke-m.de>
On Sun, 19 Jun 2016 18:08:10 +0200
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> This adds some register documentation which should make it easier to
> understand how this controller works.
This commits also adds some new definitions and replace (1 << x) by
BIT(x).
Can you update the commit description accordingly?
>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
> drivers/mtd/nand/xway_nand.c | 21 +++++++++++++++------
> 1 file changed, 15 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/mtd/nand/xway_nand.c b/drivers/mtd/nand/xway_nand.c
> index 0cf0ac0..2d74637 100644
> --- a/drivers/mtd/nand/xway_nand.c
> +++ b/drivers/mtd/nand/xway_nand.c
> @@ -16,20 +16,29 @@
> #define EBU_ADDSEL1 0x24
> #define EBU_NAND_CON 0xB0
> #define EBU_NAND_WAIT 0xB4
> +#define NAND_WAIT_RD BIT(0) /* NAND flash status output */
> +#define NAND_WAIT_WR_C BIT(3) /* NAND Write/Read complete */
> #define EBU_NAND_ECC0 0xB8
> #define EBU_NAND_ECC_AC 0xBC
>
> -/* nand commands */
> -#define NAND_CMD_ALE (1 << 2)
> -#define NAND_CMD_CLE (1 << 3)
> -#define NAND_CMD_CS (1 << 4)
> +/*
> + * nand commands
> + * The pins of the NAND chip are selected based on the address bits of the
> + * "register" read and write. There are no special registers, but an
> + * address range and the lower address bits are used to activate the
> + * correct line. For example when the bit (1 << 2) is set in the address
> + * the ALE pin will be activated.
> + */
> +#define NAND_CMD_ALE BIT(2) /* address latch enable */
> +#define NAND_CMD_CLE BIT(3) /* command latch enable */
> +#define NAND_CMD_CS BIT(4) /* chip select */
> +#define NAND_CMD_SE BIT(5) /* spare area access latch */
> +#define NAND_CMD_WP BIT(6) /* write protect */
> #define NAND_WRITE_CMD_RESET 0xff
> #define NAND_WRITE_CMD (NAND_CMD_CS | NAND_CMD_CLE)
> #define NAND_WRITE_ADDR (NAND_CMD_CS | NAND_CMD_ALE)
> #define NAND_WRITE_DATA (NAND_CMD_CS)
> #define NAND_READ_DATA (NAND_CMD_CS)
> -#define NAND_WAIT_WR_C (1 << 3)
> -#define NAND_WAIT_RD (0x1)
>
> /* we need to tel the ebu which addr we mapped the nand to */
> #define ADDSEL1_MASK(x) (x << 4)
next prev parent reply other threads:[~2016-06-19 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 16:08 [PATCH v3 0/8] MTD: xway: fix driver Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 1/8] MTD: xway: add some more documentation Hauke Mehrtens
2016-06-19 16:14 ` Boris Brezillon [this message]
2016-06-19 16:32 ` Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 2/8] MTD: xway: convert to normal platform driver Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 3/8] MTD: xway: the latched command should be persistent Hauke Mehrtens
2016-06-19 16:22 ` Boris Brezillon
2016-06-19 16:08 ` [PATCH v3 4/8] MTD: xway: use generic reset function Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 5/8] MTD: xway: fix nand locking Hauke Mehrtens
2016-06-19 16:26 ` Boris Brezillon
2016-06-19 16:34 ` Hauke Mehrtens
2016-06-19 16:40 ` Boris Brezillon
2016-06-19 16:08 ` [PATCH v3 6/8] MTD: xway: extract read and write function Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 7/8] MTD: xway: add nandaddr to own struct Hauke Mehrtens
2016-06-19 16:29 ` Boris Brezillon
2016-06-19 16:32 ` Boris Brezillon
2016-06-19 16:35 ` Hauke Mehrtens
2016-06-19 16:08 ` [PATCH v3 8/8] MTD: xway: add missing write_buf and read_buf to nand driver Hauke Mehrtens
2016-06-19 16:32 ` Boris Brezillon
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=20160619181443.07ea27ba@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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.