From: YinFengwei <fengwei_yin@linux.alibaba.com>
To: robin.murphy@arm.com, will@kernel.org, mark.rutland@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: jie.li.linux@linux.alibaba.com
Subject: Re: [PATCH] perf/arm-cmn: don't claim resource during ioremap() for CMN700 with ACPI
Date: Tue, 18 Feb 2025 09:43:02 +0800 [thread overview]
Message-ID: <Z7Plpr3e3hdQJieG@U-V2QX163P-2032.local> (raw)
In-Reply-To: <20250218012111.30068-1-fengwei_yin@linux.alibaba.com>
On Tue, Feb 18, 2025 at 09:21:11AM +0800, Yin Fengwei wrote:
> Currently, arm-cmn PMU driver assumes ACPI claim resource
> for CMN600 + ACPI. But with CMN700 + ACPI, the device probe
> failed because of resource claim failes when ioremap() is
> called:
> [ 10.837300] arm-cmn ARMHC700:00: error -EBUSY: can't request region for resource [mem 0x40000000-0x4fffffff]
> [ 10.847310] arm-cmn ARMHC700:00: probe with driver arm-cmn failed with error -16
> [ 10.854726] arm-cmn ARMHC700:02: error -EBUSY: can't request region for resource [mem 0x40040000000-0x4004fffffff]
> [ 10.865085] arm-cmn ARMHC700:02: probe with driver arm-cmn failed with error -16
>
> Let CMN700 + ACPI do same as CMN600 + ACPI to allow CMN700
> work in ACPI env.
>
> Signed-off-by: Yin Fengwei <fengwei_yin@linux.alibaba.com>
> ---
> I am also wondering whether we could just drop the CMN600 part id
> check here if ACPI companion device claimed the resource?
>
Sorry. Just saw the link
https://lore.kernel.org/all/1676535470-120560-1-git-send-email-renyu.zj@linux.alibaba.com/
after I hit send button. May continue the discussion there. Thanks.
Regards
Yin, Fengwei
next prev parent reply other threads:[~2025-02-18 1:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 1:21 [PATCH] perf/arm-cmn: don't claim resource during ioremap() for CMN700 with ACPI Yin Fengwei
2025-02-18 1:43 ` YinFengwei [this message]
[not found] <20250218012111.30068-1-fengwei_yin@linux.alibaba.com_quarantine>
2025-02-18 10:31 ` Robin Murphy
2025-02-18 10:35 ` YinFengwei
2025-02-18 10:58 ` YinFengwei
2025-02-18 12:31 ` Robin Murphy
2025-02-19 1:50 ` YinFengwei
2025-02-19 13:16 ` Robin Murphy
2025-02-20 1:22 ` YinFengwei
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=Z7Plpr3e3hdQJieG@U-V2QX163P-2032.local \
--to=fengwei_yin@linux.alibaba.com \
--cc=jie.li.linux@linux.alibaba.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=will@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