From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Naman Jain <quic_namajain@quicinc.com>
Subject: [PATCH v2 1/2] nvmem: qfprom: Ensure access to qfprom is word aligned
Date: Sun, 27 Oct 2024 01:42:33 +0300 [thread overview]
Message-ID: <20241027-sar2130p-nvmem-v2-1-743c1271bf2d@linaro.org> (raw)
In-Reply-To: <20241027-sar2130p-nvmem-v2-0-743c1271bf2d@linaro.org>
From: Naman Jain <quic_namajain@quicinc.com>
Add logic for alignment of address for reading in qfprom driver to avoid
NOC error issues due to unaligned access. The problem manifests on the
SAR2130P platform, but in msm-5.x kernels the fix is applied
uncoditionally. Follow this approach and uncoditionally perform aligned
reads.
Fixes: 4ab11996b489 ("nvmem: qfprom: Add Qualcomm QFPROM support.")
Signed-off-by: Naman Jain <quic_namajain@quicinc.com>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
drivers/nvmem/qfprom.c | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/nvmem/qfprom.c b/drivers/nvmem/qfprom.c
index 116a39e804c70b4a0374f8ea3ac6ba1dd612109d..cad319e7bfcf34c9b9ab15eb331efda822699cce 100644
--- a/drivers/nvmem/qfprom.c
+++ b/drivers/nvmem/qfprom.c
@@ -322,15 +322,28 @@ static int qfprom_reg_read(void *context,
{
struct qfprom_priv *priv = context;
u8 *val = _val;
- int i = 0, words = bytes;
+ int buf_start, buf_end, index, i = 0;
void __iomem *base = priv->qfpcorrected;
+ char *buffer = NULL;
+ u32 read_val;
if (read_raw_data && priv->qfpraw)
base = priv->qfpraw;
+ buf_start = ALIGN_DOWN(reg, 4);
+ buf_end = ALIGN(reg + bytes, 4);
+ buffer = kzalloc(buf_end - buf_start, GFP_KERNEL);
+ if (!buffer) {
+ pr_err("memory allocation failed in %s\n", __func__);
+ return -ENOMEM;
+ }
- while (words--)
- *val++ = readb(base + reg + i++);
+ for (index = buf_start; index < buf_end; index += 4, i += 4) {
+ read_val = readl_relaxed(base + index);
+ memcpy(buffer + i, &read_val, 4);
+ }
+ memcpy(val, buffer + reg % 4, bytes);
+ kfree(buffer);
return 0;
}
--
2.39.5
next prev parent reply other threads:[~2024-10-26 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 22:42 [PATCH v2 0/2] nvmem: qfprom: add Qualcomm SAR2130P support Dmitry Baryshkov
2024-10-26 22:42 ` Dmitry Baryshkov [this message]
2024-12-09 9:55 ` [PATCH v2 1/2] nvmem: qfprom: Ensure access to qfprom is word aligned Srinivas Kandagatla
2024-12-09 10:53 ` Dmitry Baryshkov
2024-12-30 7:43 ` Akhil P Oommen
2025-01-04 7:40 ` Dmitry Baryshkov
2025-01-06 19:56 ` Akhil P Oommen
2024-10-26 22:42 ` [PATCH v2 2/2] dt-bindings: nvmem: qcom,qfprom: Add SAR2130P compatible Dmitry Baryshkov
2024-10-27 19:48 ` Krzysztof Kozlowski
2024-11-15 7:59 ` [PATCH v2 0/2] nvmem: qfprom: add Qualcomm SAR2130P support Dmitry Baryshkov
2024-11-30 22:35 ` Dmitry Baryshkov
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=20241027-sar2130p-nvmem-v2-1-743c1271bf2d@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_namajain@quicinc.com \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).