From: Gabor Juhos <j4g8y7@gmail.com>
To: Md Sadre Alam <quic_mdalam@quicinc.com>,
manivannan.sadhasivam@linaro.org, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, broonie@kernel.org,
bbrezillon@kernel.org, linux-mtd@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-spi@vger.kernel.org
Subject: Re: [PATCH v3 4/4] spi: spi-qpic-snand: set nandc_offset for ipq9574
Date: Tue, 18 Mar 2025 15:58:02 +0100 [thread overview]
Message-ID: <a72f0db0-fd49-4cff-bffe-671fc757a219@gmail.com> (raw)
In-Reply-To: <20250310120906.1577292-5-quic_mdalam@quicinc.com>
2025. 03. 10. 13:09 keltezéssel, Md Sadre Alam írta:
> The BAM block expects NAND register addresses to be computed based on
> the NAND register offset from QPIC base. This value is 0x30000 for
> ipq9574. Update the 'nandc_offset' value in the qcom_nandc_props
> appropriately.
>
> Signed-off-by: Md Sadre Alam <quic_mdalam@quicinc.com>
> ---
>
> Change in [v3]
>
> * Added nand_offset for proper address calculation
> for newer Socs
>
> Change in [v2]
>
> * This patch was not part of v2
>
> Change in [v1]
>
> * This patch was not part of v1
>
> drivers/spi/spi-qpic-snand.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/spi/spi-qpic-snand.c b/drivers/spi/spi-qpic-snand.c
> index 8c413a6a5152..85a742e21cf9 100644
> --- a/drivers/spi/spi-qpic-snand.c
> +++ b/drivers/spi/spi-qpic-snand.c
> @@ -1604,6 +1604,7 @@ static void qcom_spi_remove(struct platform_device *pdev)
> static const struct qcom_nandc_props ipq9574_snandc_props = {
> .dev_cmd_reg_start = 0x7000,
> .supports_bam = true,
> + .nandc_offset = 0x30000,
> };
Applying the first patch alone results in the following error on IPQ9574:
[ 3.596403] qcom_snand 79b0000.spi: failure in submitting cmd descriptor
[ 3.596490] spi-nand spi0.0: probe with driver spi-nand failed with error -110
So this change should be integrated into the first patch. Otherwise, SPI NAND
support would be broken on IPQ9574 temporarily between the first and the
current patch.
Regards,
Gabor
next prev parent reply other threads:[~2025-03-18 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 12:09 [PATCH v3 0/4] QPIC v2 fixes for SDX75 Md Sadre Alam
2025-03-10 12:09 ` [PATCH v3 1/4] mtd: rawnand: qcom: Pass 18 bit offset from QPIC base address to BAM Md Sadre Alam
2025-03-18 7:33 ` Manivannan Sadhasivam
2025-03-20 5:53 ` Md Sadre Alam
2025-03-25 14:32 ` Manivannan Sadhasivam
2025-03-18 14:52 ` Gabor Juhos
2025-03-20 5:59 ` Md Sadre Alam
2025-03-10 12:09 ` [PATCH v3 2/4] mtd: rawnand: qcom: Fix last codeword read in qcom_param_page_type_exec() Md Sadre Alam
2025-03-10 12:09 ` [PATCH v3 3/4] mtd: rawnand: qcom: Fix read len for onfi param page Md Sadre Alam
2025-03-18 7:34 ` Manivannan Sadhasivam
2025-03-10 12:09 ` [PATCH v3 4/4] spi: spi-qpic-snand: set nandc_offset for ipq9574 Md Sadre Alam
2025-03-13 12:59 ` Mark Brown
2025-03-18 7:35 ` Manivannan Sadhasivam
2025-03-18 14:58 ` Gabor Juhos [this message]
2025-03-20 6:10 ` Md Sadre Alam
2025-03-18 7:41 ` [PATCH v3 0/4] QPIC v2 fixes for SDX75 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=a72f0db0-fd49-4cff-bffe-671fc757a219@gmail.com \
--to=j4g8y7@gmail.com \
--cc=bbrezillon@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=miquel.raynal@bootlin.com \
--cc=quic_mdalam@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