mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>,
	linux-mtd@lists.infradead.org, dregan@broadcom.com,
	miquel.raynal@bootlin.com, bcm-kernel-feedback-list@broadcom.com,
	rafal@milecki.pl, computersforpeace@gmail.com,
	kamal.dasu@broadcom.com, dan.beygelman@broadcom.com,
	william.zhang@broadcom.com, frieder.schrempf@kontron.de,
	linux-kernel@vger.kernel.org, vigneshr@ti.com, richard@nod.at,
	bbrezillon@kernel.org, kdasu.kdev@gmail.com,
	jaimeliao.tw@gmail.com, kilobyte@angband.pl,
	jonas.gorski@gmail.com, dgcbueu@gmail.com
Subject: Re: [PATCH v2] mtd: rawnand: brcmnand: legacy exec_op implementation
Date: Tue, 13 May 2025 10:42:24 +0200	[thread overview]
Message-ID: <a563cb0b-0bc5-4dbe-b570-4d45c1b14641@broadcom.com> (raw)
In-Reply-To: <20250513080151.565359-1-noltari@gmail.com>



On 5/13/2025 10:01 AM, Álvaro Fernández Rojas wrote:
> Commit 3c8260ce7663 ("mtd: rawnand: brcmnand: exec_op implementation")
> removed legacy interface functions, breaking < v5.0 controllers support.
> In order to fix older controllers we need to add an alternative exec_op
> implementation which doesn't rely on low level registers.
> 
> Fixes: 3c8260ce7663 ("mtd: rawnand: brcmnand: exec_op implementation")
> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
> ---
>   drivers/mtd/nand/raw/brcmnand/brcmnand.c | 160 ++++++++++++++++++++++-
>   1 file changed, 154 insertions(+), 6 deletions(-)
> 
>   v2: multiple improvements:
>    - Use proper native commands for checks.
>    - Fix NAND_CMD_PARAM/NAND_CMD_RNDOUT addr calculation.
>    - Remove host->last_addr usage.
>    - Remove sector_size_1k since it only applies to v5.0+ controllers.
>    - Remove brcmnand_wp since it doesn't exist for < v5.0 controllers.
>    - Use j instead of i for flash_cache loop.
> 
> diff --git a/drivers/mtd/nand/raw/brcmnand/brcmnand.c b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> index 17f6d9723df9..2b519dfcac5d 100644
> --- a/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> +++ b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
> @@ -2490,14 +2490,163 @@ static int brcmnand_op_is_reset(const struct nand_operation *op)
>   	return 0;
>   }
>   
> +static int brcmnand_exec_instructions(struct nand_chip *chip,
> +				      const struct nand_operation *op)
> +{
> +	struct brcmnand_host *host = nand_get_controller_data(chip);
> +	unsigned int i;
> +	int ret = 0;
> +
> +	for (i = 0; i < op->ninstrs; i++) {
> +		ret = brcmnand_exec_instr(host, i, op);
> +		if (ret)
> +			break;
> +	}
> +
> +	return ret;
> +}
> +
> +static int brcmnand_exec_instructions_legacy(struct nand_chip *chip,
> +					     const struct nand_operation *op)
> +{
> +	struct mtd_info *mtd = nand_to_mtd(chip);
> +	struct brcmnand_host *host = nand_get_controller_data(chip);
> +	struct brcmnand_controller *ctrl = host->ctrl;
> +	const struct nand_op_instr *instr;
> +	unsigned int i, j;
> +	int cmd = CMD_NULL, last_cmd = CMD_NULL;
> +	int ret = 0;
> +	u64 last_addr;
> +
> +	for (i = 0; i < op->ninstrs; i++) {
> +		instr = &op->instrs[i];
> +
> +		if (instr->type == NAND_OP_CMD_INSTR) {
> +			if (instr->ctx.cmd.opcode == NAND_CMD_READID) {
> +				cmd = CMD_DEVICE_ID_READ;
> +			} else if (instr->ctx.cmd.opcode == NAND_CMD_READOOB) {
> +				cmd = CMD_SPARE_AREA_READ;
> +			} else if (instr->ctx.cmd.opcode == NAND_CMD_ERASE1) {
> +				cmd = CMD_BLOCK_ERASE;
> +			} else if (instr->ctx.cmd.opcode == NAND_CMD_ERASE2) {
> +				cmd = CMD_NULL;
> +			} else if (instr->ctx.cmd.opcode == NAND_CMD_PARAM) {
> +				cmd = CMD_PARAMETER_READ;
> +			} else if (instr->ctx.cmd.opcode == NAND_CMD_RNDOUT) {
> +				cmd = CMD_PARAMETER_CHANGE_COL;
> +			} else if (instr->ctx.cmd.opcode == NAND_CMD_RNDOUTSTART) {
> +				cmd = CMD_NULL;
> +			} else {
> +				dev_err(ctrl->dev, "unsupported cmd=%d\n",
> +					instr->ctx.cmd.opcode);
> +				ret = -EOPNOTSUPP;
> +				break;
> +			}

You could probably use an associative array here to limit the amount of 
lines?

[snip]

> -	for (i = 0; i < op->ninstrs; i++) {
> -		ret = brcmnand_exec_instr(host, i, op);
> -		if (ret)
> -			break;
> -	}
> +	if (ctrl->nand_version >= 0x500)
> +		brcmnand_exec_instructions(chip, op);
> +	else
> +		brcmnand_exec_instructions_legacy(chip, op);

I would add a new function pointer member to brcmnand_controller in 
order to avoid doing this test every time we call brcmnand_exec_op().

Thanks for doing this work!
-- 
Florian


      reply	other threads:[~2025-05-13  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13  8:01 Álvaro Fernández Rojas
2025-05-13  8:42 ` Florian Fainelli [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=a563cb0b-0bc5-4dbe-b570-4d45c1b14641@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=bbrezillon@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=computersforpeace@gmail.com \
    --cc=dan.beygelman@broadcom.com \
    --cc=dgcbueu@gmail.com \
    --cc=dregan@broadcom.com \
    --cc=frieder.schrempf@kontron.de \
    --cc=jaimeliao.tw@gmail.com \
    --cc=jonas.gorski@gmail.com \
    --cc=kamal.dasu@broadcom.com \
    --cc=kdasu.kdev@gmail.com \
    --cc=kilobyte@angband.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=noltari@gmail.com \
    --cc=rafal@milecki.pl \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    --cc=william.zhang@broadcom.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

all inboxes | Powered by JetHome®