From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Borislav Petkov <bp@alien8.de>
Cc: bjorn.andersson@linaro.org, mchehab@kernel.org,
james.morse@arm.com, rric@kernel.org,
linux-arm-msm@vger.kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_saipraka@quicinc.com
Subject: Re: [PATCH v4 1/2] EDAC/qcom: Get rid of hardcoded register offsets
Date: Mon, 28 Nov 2022 23:47:05 +0530 [thread overview]
Message-ID: <20221128181705.GP62721@thinkpad> (raw)
In-Reply-To: <Y4SmtfSzLbYea+f0@zn.tnic>
On Mon, Nov 28, 2022 at 01:16:53PM +0100, Borislav Petkov wrote:
> On Wed, Nov 16, 2022 at 08:03:51PM +0530, Manivannan Sadhasivam wrote:
> > The LLCC EDAC register offsets varies between each SoC. Hardcoding the
> > register offsets won't work and will often result in crash due to
> > accessing the wrong locations.
> >
> > Hence, get the register offsets from the LLCC driver matching the
> > individual SoCs.
> >
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > ---
> > drivers/edac/qcom_edac.c | 116 ++++++++++++++---------------
> > include/linux/soc/qcom/llcc-qcom.h | 6 --
> > 2 files changed, 58 insertions(+), 64 deletions(-)
>
> It looks to me like this patch needs to go to stable?
>
Well, yes but that would imply both LLCC and EDAC patches going together.
Splitting them will break the build, which is worse.
So I delibrately avoided CCing stable list. I'll ping them once both patches
are in mainline.
> Also, the Fixes tag should probably be:
>
> Fixes: 27450653f1db ("drivers: edac: Add EDAC driver support for QCOM SoCs")
>
> Yes, no?
>
No. The actual breakage happened with, a6e9d7ef252c ("soc: qcom: llcc: Add
configuration data for SM8450 SoC"). I didn't add the fixes tag because, the
stable team might backport this patch automatically. And since the tag is not
present in the LLCC patch, it will break the build.
> Also, please explain to me how you've tested this patch if it doesn't
> even build?!
>
> ERROR: modpost: "__devm_regmap_init_mmio_clk" [drivers/soc/qcom/llcc-qcom.ko] undefined!
> make[1]: *** [scripts/Makefile.modpost:126: Module.symvers] Error 1
> make: *** [Makefile:1944: modpost] Error 2
>
> I guess because CONFIG_QCOM_LLCC is =y in your config while I have
> CONFIG_QCOM_LLCC=m.
>
> And I reported the same build error to you the last time. Did you not
> see it?
>
> For the next version, you'd need to fix all possible Kconfig build
> errors before sending.
>
Sorry, it is because I only tried building for ARM64 architecture. The error
you are seeing is for x86-64 and I could now reproduce it as well.
Will submit the next iteration including a fix for that.
Thanks,
Mani
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2022-11-28 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 14:33 [PATCH v4 0/2] Fix crash when using Qcom LLCC/EDAC drivers Manivannan Sadhasivam
2022-11-16 14:33 ` [PATCH v4 1/2] EDAC/qcom: Get rid of hardcoded register offsets Manivannan Sadhasivam
2022-11-28 12:16 ` Borislav Petkov
2022-11-28 18:17 ` Manivannan Sadhasivam [this message]
2022-11-28 18:35 ` Borislav Petkov
2022-11-29 5:53 ` Manivannan Sadhasivam
2022-11-16 14:33 ` [PATCH v4 2/2] EDAC/qcom: Remove extra error no assignment in qcom_llcc_core_setup() 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=20221128181705.GP62721@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_saipraka@quicinc.com \
--cc=rric@kernel.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