From: Yicong Yang <yangyicong@huawei.com>
To: Youwan Wang <youwan@nfschina.com>
Cc: <jonathan.cameron@huawei.com>, <yangyicong@hisilicon.com>,
<will@kernel.org>, <mark.rutland@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/perf: hisi: Fix readl DDRC_VERSION stuck
Date: Thu, 17 Oct 2024 14:39:53 +0800 [thread overview]
Message-ID: <4c0097dd-6dd3-e4e6-14d1-d94a6d98bf5a@huawei.com> (raw)
In-Reply-To: <20241010084217.37540-1-youwan@nfschina.com>
On 2024/10/10 16:42, Youwan Wang wrote:
> The CPU of the device I am using is kunpeng 920,
> which can start normally with version 5.4 kernel.
> However, when installing version 6.6 kernel, the
> kernel gets stuck when loading the "hisi_dddrc_pmu"
> driver. I went to debug and found that it gets stuck
> when "readl (ddrc_pmu ->base+DDRC_VERSION)". I suspect
what does "stuck" mean here? do you see some hardware errors
or similiar? If so this should be an unexpected device and
your patch still doesn't address the issue, since you only make
the probe work but the device's still inaccessible so it
shouldn't be appeared in the system.
as Will mentions, this is probably a firmware issue. please
try to update to the latest firmware.
Thanks.
> that the hardware does not support it. My modification is:
> for the "HISI0233" device, according to the implementation
> of version 5.4 kernel, the identity is not obtained from
> the register. For "identifier" sysfs, identifier: 0
>
> Signed-off-by: Youwan Wang <youwan@nfschina.com>
> ---
> drivers/perf/hisilicon/hisi_uncore_ddrc_pmu.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/perf/hisilicon/hisi_uncore_ddrc_pmu.c b/drivers/perf/hisilicon/hisi_uncore_ddrc_pmu.c
> index b804e3738113..3cecad46b01f 100644
> --- a/drivers/perf/hisilicon/hisi_uncore_ddrc_pmu.c
> +++ b/drivers/perf/hisilicon/hisi_uncore_ddrc_pmu.c
> @@ -321,6 +321,9 @@ static int hisi_ddrc_pmu_init_data(struct platform_device *pdev,
> return PTR_ERR(ddrc_pmu->base);
> }
>
> + if (strstr(pdev->name, "HISI0233"))
> + return 0;
> +
> ddrc_pmu->identifier = readl(ddrc_pmu->base + DDRC_VERSION);
> if (ddrc_pmu->identifier >= HISI_PMU_V2) {
> if (device_property_read_u32(&pdev->dev, "hisilicon,sub-id",
>
prev parent reply other threads:[~2024-10-17 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 8:42 Youwan Wang
2024-10-14 13:56 ` Will Deacon
2024-10-17 6:39 ` Yicong Yang [this message]
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=4c0097dd-6dd3-e4e6-14d1-d94a6d98bf5a@huawei.com \
--to=yangyicong@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=youwan@nfschina.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®