From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Md Sadre Alam <quic_mdalam@quicinc.com>
Cc: miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
bbrezillon@kernel.org, linux-mtd@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_srichara@quicinc.com, quic_varada@quicinc.com,
quic_nainmeht@quicinc.com, quic_laksd@quicinc.com
Subject: Re: [PATCH v2 3/3] mtd: rawnand: qcom: Fix read len for onfi param page
Date: Tue, 26 Nov 2024 11:15:29 +0530 [thread overview]
Message-ID: <20241126054529.ewoajuaor4wpa4xe@thinkpad> (raw)
In-Reply-To: <20241122085933.2663927-4-quic_mdalam@quicinc.com>
On Fri, Nov 22, 2024 at 02:29:33PM +0530, Md Sadre Alam wrote:
> The minimum size to fetch the data from device to QPIC buffer
> is 512-bytes. If size is less than 512-bytes the data will not be
> protected by ECC as per QPIC standard. So while reading onfi parameter
> page from NAND device setting nandc->buf_count = 512.
s/setting/set
>
> Cc: stable@vger.kernel.org
> Fixes: 89550beb098e ("mtd: rawnand: qcom: Implement exec_op()")
> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
- Mani
> ---
>
> Change in [v2]
>
> * Set buf_count to 512 in the parameter page read
>
> Change in [v1]
>
> * This patch was not included in v1
>
> drivers/mtd/nand/raw/qcom_nandc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/raw/qcom_nandc.c b/drivers/mtd/nand/raw/qcom_nandc.c
> index 31ec3db1246d..e1dca4857754 100644
> --- a/drivers/mtd/nand/raw/qcom_nandc.c
> +++ b/drivers/mtd/nand/raw/qcom_nandc.c
> @@ -2926,7 +2926,7 @@ static int qcom_param_page_type_exec(struct nand_chip *chip, const struct nand_
> write_reg_dma(nandc, NAND_DEV_CMD1, 1, NAND_BAM_NEXT_SGL);
> }
>
> - nandc->buf_count = len;
> + nandc->buf_count = 512;
> memset(nandc->data_buffer, 0xff, nandc->buf_count);
>
> config_nand_single_cw_page_read(chip, false, 0);
> --
> 2.34.1
>
--
மணிவண்ணன் சதாசிவம்
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-11-26 5:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 8:59 [PATCH v2 0/3] QPIC v2 fixes for SDX75 Md Sadre Alam
2024-11-22 8:59 ` [PATCH v2 1/3] mtd: rawnand: qcom: Pass 18 bit offset from QPIC base address to BAM Md Sadre Alam
2024-11-26 5:30 ` Manivannan Sadhasivam
2024-11-27 9:05 ` Md Sadre Alam
2024-11-22 8:59 ` [PATCH v2 2/3] mtd: rawnand: qcom: Fix onfi param page read Md Sadre Alam
2024-11-26 5:41 ` Manivannan Sadhasivam
2024-11-27 9:11 ` Md Sadre Alam
2024-11-22 8:59 ` [PATCH v2 3/3] mtd: rawnand: qcom: Fix read len for onfi param page Md Sadre Alam
2024-11-26 5:45 ` Manivannan Sadhasivam [this message]
2024-11-26 5:49 ` Manivannan Sadhasivam
2024-11-22 17:44 ` [PATCH v2 0/3] QPIC v2 fixes for SDX75 Lakshmi Sowjanya D (QUIC)
2024-12-20 9:30 ` Manivannan Sadhasivam
2024-12-24 5:22 ` Md Sadre Alam
2024-12-24 8:09 ` Miquel Raynal
2024-12-24 11:53 ` Md Sadre Alam
2025-01-06 14:04 ` Manivannan Sadhasivam
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=20241126054529.ewoajuaor4wpa4xe@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bbrezillon@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=quic_laksd@quicinc.com \
--cc=quic_mdalam@quicinc.com \
--cc=quic_nainmeht@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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