From: Jonathan Cameron <jic23@kernel.org>
To: Faiyaz Mohammed <faiyaz.mohammed@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Conor Dooley <conor@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Borislav Petkov <bp@alien8.de>, Tony Luck <tony.luck@intel.com>,
Conor Dooley <conor+dt@kernel.org>,
Abel Vesa <abelvesa@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org
Subject: Re: [PATCH 2/4] soc: qcom: llcc: add LCP/SRP DDR DRAM ECC register offsets
Date: Fri, 16 Oct 2026 18:20:14 +0100 [thread overview]
Message-ID: <20261016182014.7d2d8bbe@jic23-hlaptop> (raw)
In-Reply-To: <20261014-master-v1-2-aba3cfcfbac9@oss.qualcomm.com>
On Wed, 14 Oct 2026 21:26:17 +0530
Faiyaz Mohammed <faiyaz.mohammed@oss.qualcomm.com> wrote:
> Add LCP/SRP ECC register offsets to struct llcc_edac_reg_offset and
> create llcc_lcp_srp_edac_reg_offset for QCM2390, leaving the shared
> llcc_v2_1_edac_reg_offset table unchanged. Switch shikra_cfg to the
> new table so other platforms with the same block can reuse it.
>
> Add lcp_irq to struct llcc_drv_data and retrieve the optional second
> interrupt in qcom_llcc_probe(), propagating non-absence errors so the
> driver defers correctly.
>
> Signed-off-by: Faiyaz Mohammed <faiyaz.mohammed@oss.qualcomm.com>
Hi Faiyaz,
One comment on existing code + a suggestion to tidy the new stuff
up a little.
That global for drv_data is less than ideal, but given you are touching
the driver please tidy up initial assignment to use INIT_ERR_PTR()
> static const struct llcc_edac_reg_offset llcc_v6_edac_reg_offset = {
> .trp_ecc_error_status0 = 0x47448,
> .trp_ecc_error_status1 = 0x47450,
> @@ -4767,7 +4802,7 @@ static const struct qcom_llcc_config shikra_cfg[] = {
> .sct_data = shikra_data,
> .size = ARRAY_SIZE(shikra_data),
> .reg_offset = llcc_v2_1_reg_offset,
> - .edac_reg_offset = &llcc_v2_1_edac_reg_offset,
> + .edac_reg_offset = &llcc_lcp_srp_edac_reg_offset,
> .irq_configured = true,
> },
> };
> @@ -5798,7 +5833,13 @@ static int qcom_llcc_probe(struct platform_device *pdev)
> if (drv_data->ecc_irq < 0 && drv_data->ecc_irq != -ENXIO)
> return dev_err_probe(&pdev->dev, drv_data->ecc_irq,
> "failed to get IRQ resource\n");
Unrelated to your patch, but why don't we need that tiny bit of error cleanup under
goto err for this path? That use of a global is not the best anyway, but none
the less I'd expect either some consistency or a comment on why not in the above
path.
> -
> + if (cfg->edac_reg_offset && cfg->edac_reg_offset->lcp_srp_interrupt_enable) {
> + drv_data->lcp_irq = platform_get_irq_optional(pdev, 1);
> + if (drv_data->lcp_irq < 0 && drv_data->lcp_irq != -ENXIO) {
> + ret = drv_data->lcp_irq;
> + goto err;
> + }
Maybe it's local style, but generally I'd put the value in ret until you've checked validty
then copy it to the good location.
ret = platform_get_irq_optional(pdev, 1);
if (ret < 0 && ret != -ENXIO)
goto err;
drv_data->lcp_irq = ret;
Both more compact and obvious when we trust the value to be good.
> + }
> drv_data->edac_reg_offset = cfg->edac_reg_offset;
> drv_data->ecc_irq_configured = cfg->irq_configured;
> drv_data->dev = dev;
next prev parent reply other threads:[~2026-10-16 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 15:56 [PATCH 0/4] edac: qcom: add DDR DRAM ECC reporting for Shikra (QCM2390) Faiyaz Mohammed
2026-10-14 15:56 ` [PATCH 1/4] dt-bindings: cache: qcom,llcc: allow optional second interrupt for LCP/SRP ECC Faiyaz Mohammed
2026-10-14 16:05 ` sashiko-bot
2026-10-14 15:56 ` [PATCH 2/4] soc: qcom: llcc: add LCP/SRP DDR DRAM ECC register offsets Faiyaz Mohammed
2026-10-16 17:20 ` Jonathan Cameron [this message]
2026-10-14 15:56 ` [PATCH 3/4] edac: qcom: add LCP/SRP DDR DRAM ECC support for Shikra Faiyaz Mohammed
2026-10-14 16:09 ` sashiko-bot
2026-10-14 15:56 ` [PATCH 4/4] arm64: dts: qcom: shikra: add LCP/SRP ECC interrupt to LLCC node Faiyaz Mohammed
2026-10-14 16:08 ` sashiko-bot
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=20261016182014.7d2d8bbe@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=faiyaz.mohammed@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=tony.luck@intel.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