From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Kamal Dasu <kdasu.kdev@gmail.com>
Cc: linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
f.fainelli@gmail.com, bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH] mtd: brcmnand: Check flash write protect pin status
Date: Wed, 15 Feb 2017 09:51:19 +0100 [thread overview]
Message-ID: <20170215095119.3412108a@bbrezillon> (raw)
In-Reply-To: <1487089424-4354-1-git-send-email-kdasu.kdev@gmail.com>
Hi Kamal,
Can you Cc the MTD and NAND maintainers when you send NAND/MTD patches?
Also, for the subject prefix, I'd prefer 'mtd: nand: brcm:'.
On Tue, 14 Feb 2017 11:23:44 -0500
Kamal Dasu <kdasu.kdev@gmail.com> wrote:
> With v6.x and v7.x controller lets the driver to enable disable #WP pin.
> So to be safe let driver send flash status cmd whenever the #WP pin status
> is being changed and makes sure the controller and the the flash are both
> ready to accept new cmds by verifying the WP protect/unprotect bit is set
> correctly in the flash status byte. Modify enable/disable #WP register only
> when the nand controller is not ready.
You mean 'is ready' here, right?
I still have a hard time understanding what the problem is with this
commit message. Can you try to clarify that?
>
> Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
> ---
> drivers/mtd/nand/brcmnand/brcmnand.c | 75 +++++++++++++++++++++++++++++++-----
> 1 file changed, 65 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/mtd/nand/brcmnand/brcmnand.c b/drivers/mtd/nand/brcmnand/brcmnand.c
> index 42ebd73..6935bc1 100644
> --- a/drivers/mtd/nand/brcmnand/brcmnand.c
> +++ b/drivers/mtd/nand/brcmnand/brcmnand.c
> @@ -101,6 +101,9 @@ struct brcm_nand_dma_desc {
> #define BRCMNAND_MIN_BLOCKSIZE (8 * 1024)
> #define BRCMNAND_MIN_DEVSIZE (4ULL * 1024 * 1024)
>
> +#define FLASH_RDY (NAND_STATUS_READY)
> +#define NAND_CTRL_RDY (INTFC_CTLR_READY | INTFC_FLASH_READY)
> +
> /* Controller feature flags */
> enum {
> BRCMNAND_HAS_1K_SECTORS = BIT(0),
> @@ -765,13 +768,62 @@ enum {
> CS_SELECT_AUTO_DEVICE_ID_CFG = BIT(30),
> };
>
> -static inline void brcmnand_set_wp(struct brcmnand_controller *ctrl, bool en)
> +static int bcmnand_ctrl_busy_poll(struct brcmnand_controller *ctrl, u32 mask)
> +{
> + unsigned long timeout = jiffies + msecs_to_jiffies(200);
> +
> + if (!mask)
> + mask = INTFC_CTLR_READY;
Do you really need this check? All users of bcmnand_ctrl_busy_poll()
are passing mask != 0.
> +
> + while ((brcmnand_read_reg(ctrl, BRCMNAND_INTFC_STATUS) & mask) !=
> + mask) {
> + if (time_after(jiffies, timeout)) {
> + dev_warn(ctrl->dev, "timeout on ctrl_ready\n");
> + return -ETIMEDOUT;
> + }
> + cpu_relax();
> + }
> + return 0;
> +}
> +
> +static inline void brcmnand_set_wp_reg(struct brcmnand_controller *ctrl, int en)
> {
> u32 val = en ? CS_SELECT_NAND_WP : 0;
>
> brcmnand_rmw_reg(ctrl, BRCMNAND_CS_SELECT, CS_SELECT_NAND_WP, 0, val);
> }
>
> +static void brcmnand_set_wp(struct brcmnand_host *host, int en)
> +{
> + struct brcmnand_controller *ctrl = host->ctrl;
> + struct mtd_info *mtd = &host->mtd;
> + struct nand_chip *chip = mtd->priv;
> + u32 sts_reg;
> + bool is_wp;
> +
> + /*
> + * make sure ctrl/flash ready before and after
> + * changing state of WP PIN
> + */
> + bcmnand_ctrl_busy_poll(ctrl, NAND_CTRL_RDY | FLASH_RDY);
> + brcmnand_set_wp_reg(ctrl, en);
> + chip->cmdfunc(mtd, NAND_CMD_STATUS, -1, -1);
> + bcmnand_ctrl_busy_poll(ctrl, NAND_CTRL_RDY | FLASH_RDY);
> + sts_reg = brcmnand_read_reg(ctrl, BRCMNAND_INTFC_STATUS);
> + /* NAND_STATUS_WP 0x80 = not protected, 0x00 = protected */
> + is_wp = (sts_reg & NAND_STATUS_WP) ? false : true;
> +
> + if (is_wp != en) {
> + u32 nand_wp = brcmnand_read_reg(ctrl, BRCMNAND_CS_SELECT);
> +
> + nand_wp &= CS_SELECT_NAND_WP;
> + dev_err_ratelimited(&host->pdev->dev,
> + "#WP %s sts:0x%x expected %s NAND_WP 0x%x\n",
> + is_wp ? "On" : "Off", sts_reg & 0xff,
> + en ? "On" : "Off", nand_wp ? 1 : 0);
Hm, so this function can fail. Shouldn't you make it return a return
code instead of ignoring failures? This way, you can return an error
from the probe.
> + }
> +}
> +
> /***********************************************************************
> * Flash DMA
> ***********************************************************************/
> @@ -1029,7 +1081,7 @@ static void brcmnand_wp(struct mtd_info *mtd, int wp)
> dev_dbg(ctrl->dev, "WP %s\n", wp ? "on" : "off");
> old_wp = wp;
> }
> - brcmnand_set_wp(ctrl, wp);
> + brcmnand_set_wp(host, wp);
> }
> }
>
> @@ -1158,15 +1210,18 @@ static void brcmnand_send_cmd(struct brcmnand_host *host, int cmd)
> {
> struct brcmnand_controller *ctrl = host->ctrl;
> u32 intfc;
> + u32 mask = NAND_CTRL_RDY;
No need for this local variable...
>
> dev_dbg(ctrl->dev, "send native cmd %d addr_lo 0x%x\n", cmd,
> brcmnand_read_reg(ctrl, BRCMNAND_CMD_ADDRESS));
> BUG_ON(ctrl->cmd_pending != 0);
> ctrl->cmd_pending = cmd;
>
> + bcmnand_ctrl_busy_poll(ctrl, mask);
... just call
bcmnand_ctrl_busy_poll(ctrl, NAND_CTRL_RDY);
here.
> intfc = brcmnand_read_reg(ctrl, BRCMNAND_INTFC_STATUS);
> WARN_ON(!(intfc & INTFC_CTLR_READY));
>
> +
Drop this extra empty line.
> mb(); /* flush previous writes */
> brcmnand_write_reg(ctrl, BRCMNAND_CMD_START,
> cmd << brcmnand_cmd_shift(ctrl));
> @@ -2462,14 +2517,6 @@ int brcmnand_probe(struct platform_device *pdev, struct brcmnand_soc *soc)
> /* Disable XOR addressing */
> brcmnand_rmw_reg(ctrl, BRCMNAND_CS_XOR, 0xff, 0, 0);
>
> - if (ctrl->features & BRCMNAND_HAS_WP) {
> - /* Permanently disable write protection */
> - if (wp_on == 2)
> - brcmnand_set_wp(ctrl, false);
> - } else {
> - wp_on = 0;
> - }
> -
> /* IRQ */
> ctrl->irq = platform_get_irq(pdev, 0);
> if ((int)ctrl->irq < 0) {
> @@ -2522,6 +2569,14 @@ int brcmnand_probe(struct platform_device *pdev, struct brcmnand_soc *soc)
> }
>
> list_add_tail(&host->node, &ctrl->host_list);
> +
> + if (ctrl->features & BRCMNAND_HAS_WP) {
> + /* Permanently disable write protection */
> + if (wp_on == 2)
> + brcmnand_set_wp(host, false);
> + } else {
> + wp_on = 0;
> + }
Hm, this is not really related to the change you describe in your
commit message. This should probably go in a separate commit.
> }
> }
>
next prev parent reply other threads:[~2017-02-15 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 16:23 [PATCH] mtd: brcmnand: Check flash write protect pin status Kamal Dasu
2017-02-15 8:51 ` Boris Brezillon [this message]
2017-02-15 18:51 ` Kamal Dasu
2017-02-15 19:50 ` 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=20170215095119.3412108a@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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.