From: Faiyaz Mohammed <faiyaz.mohammed@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Conor Dooley <conor@kernel.org>,
Jonathan Cameron <jic23@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: Wed, 21 Oct 2026 17:24:44 +0530 [thread overview]
Message-ID: <67404f33-9452-4a53-8ed6-8fee4eea2611@oss.qualcomm.com> (raw)
In-Reply-To: <20261017-spiffy-shapeless-caiman-d658a6@quoll>
On 17-10-2026 22:04, Krzysztof Kozlowski wrote:
> On Wed, Oct 14, 2026 at 09:26:17PM +0530, Faiyaz Mohammed 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>
>> ---
>> drivers/soc/qcom/llcc-qcom.c | 45 ++++++++++++++++++++++++++++++++++++--
>> include/linux/soc/qcom/llcc-qcom.h | 13 +++++++++++
>> 2 files changed, 56 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/soc/qcom/llcc-qcom.c b/drivers/soc/qcom/llcc-qcom.c
>> index d7a42a8040a1..39e0da14b36d 100644
>> --- a/drivers/soc/qcom/llcc-qcom.c
>> +++ b/drivers/soc/qcom/llcc-qcom.c
>> @@ -4509,6 +4509,41 @@ static const struct llcc_edac_reg_offset llcc_v2_1_edac_reg_offset = {
>> .drp_ecc_db_err_syn0 = 0x52120,
>> };
>>
>> +static const struct llcc_edac_reg_offset llcc_lcp_srp_edac_reg_offset = {
>> + .trp_ecc_error_status0 = 0x20344,
>> + .trp_ecc_error_status1 = 0x20348,
>> + .trp_ecc_sb_err_syn0 = 0x2034c,
>> + .trp_ecc_db_err_syn0 = 0x20370,
>> + .trp_ecc_error_cntr_clear = 0x20440,
>> + .trp_interrupt_0_status = 0x20480,
>> + .trp_interrupt_0_clear = 0x20484,
>> + .trp_interrupt_0_enable = 0x20488,
>> +
>> + /* LLCC Common registers */
>> + .cmn_status0 = 0x3400c,
>> + .cmn_interrupt_0_enable = 0x3401c,
>> + .cmn_interrupt_1_enable = 0x3402c,
>> + .cmn_interrupt_2_enable = 0x3403c,
>> +
>> + /* LLCC DRP registers */
>> + .drp_ecc_error_cfg = 0x50000,
>> + .drp_ecc_error_cntr_clear = 0x50004,
>> + .drp_interrupt_status = 0x50020,
>> + .drp_interrupt_clear = 0x50028,
>> + .drp_interrupt_enable = 0x5002c,
>> + .drp_ecc_error_status0 = 0x520f4,
>> + .drp_ecc_error_status1 = 0x520f8,
>> + .drp_ecc_sb_err_syn0 = 0x520fc,
>> + .drp_ecc_db_err_syn0 = 0x52120,
>> +
>> + /* LCP/SRP DDR DRAM ECC registers */
>> + .lcp_srp_ecc_error_cntr_clear = 0x59004,
>> + .lcp_srp_ecc_error_status1 = 0x59010,
>> + .lcp_srp_interrupt_status = 0x59070,
>> + .lcp_srp_interrupt_clear = 0x59074,
>> + .lcp_srp_interrupt_enable = 0x59078,
>> +};
>> +
>> 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");
>> -
>> + if (cfg->edac_reg_offset && cfg->edac_reg_offset->lcp_srp_interrupt_enable) {
>> + drv_data->lcp_irq = platform_get_irq_optional(pdev, 1);
>
> Why do you exactly require interrupt-names?
>
Good question. The driver was using platform_get_irq_optional(pdev, 1)
by index, which made interrupt-names a documentation-only annotation
with no driver enforcement — not a good reason to require it.
Switched lcp_irq retrieval to platform_get_irq_byname_optional(pdev,
"lcp"). Platforms without interrupt-names naturally return -ENODATA,
which the driver treats as absent — no explicit register-offset guard
needed. The ecc_irq stays index-based (platform_get_irq_optional(pdev,
0)) for backward compatibility with all legacy platforms that have no
interrupt-names property.
Will repost as v2.
> Best regards,
> Krzysztof
Thanks & regards,
Mohammed Faiyaz
next prev parent reply other threads:[~2026-10-21 11:54 UTC|newest]
Thread overview: 13+ 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-17 16:34 ` Krzysztof Kozlowski
2026-10-21 11:47 ` Faiyaz Mohammed
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
2026-10-21 11:49 ` Faiyaz Mohammed
2026-10-17 16:34 ` Krzysztof Kozlowski
2026-10-21 11:54 ` Faiyaz Mohammed [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-16 17:26 ` Jonathan Cameron
2026-10-21 12:01 ` Faiyaz Mohammed
2026-10-14 15:56 ` [PATCH 4/4] arm64: dts: qcom: shikra: add LCP/SRP ECC interrupt to LLCC node Faiyaz Mohammed
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=67404f33-9452-4a53-8ed6-8fee4eea2611@oss.qualcomm.com \
--to=faiyaz.mohammed@oss.qualcomm.com \
--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=jic23@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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
all inboxes | Powered by JetHome®