Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hui Min Mina Chou <minachou@andestech.com>
To: <atish.patra@linux.dev>, <anup@brainfault.org>,
	<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Cc: <tim609@andestech.com>, <cynthia@andestech.com>,
	<ben717@andestech.com>, <az70021@gmail.com>,
	Charles Ci-Jyun Wu <dminus@andestech.com>
Subject: [PATCH] perf: andes: support ANDES_CUSTOM_PMU on ARCH_ANDES
Date: Wed, 4 Feb 2026 17:18:37 +0800	[thread overview]
Message-ID: <20260204091836.1713729-1-minachou@andestech.com> (raw)

From: Charles Ci-Jyun Wu <dminus@andestech.com>

Modify ANDES_CUSTOM_PMU Kconfig dependency to include both
ARCH_ANDES and ARCH_RENESAS platforms. Previously, it depended only
on ARCH_RENESAS, which prevented PMU IRQ from being enabled correctly
on Andes platforms

Signed-off-by: Cynthia Huang <cynthia@andestech.com>
Signed-off-by: Charles Ci-Jyun Wu <dminus@andestech.com>
---
 drivers/perf/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/perf/Kconfig b/drivers/perf/Kconfig
index 638321fc9800..39e174d36336 100644
--- a/drivers/perf/Kconfig
+++ b/drivers/perf/Kconfig
@@ -117,7 +117,7 @@ config STARFIVE_STARLINK_PMU
 
 config ANDES_CUSTOM_PMU
 	bool "Andes custom PMU support"
-	depends on ARCH_RENESAS && RISCV_ALTERNATIVE && RISCV_PMU_SBI
+	depends on (ARCH_ANDES || ARCH_RENESAS) && RISCV_ALTERNATIVE && RISCV_PMU_SBI
 	default y
 	help
 	  The Andes cores implement the PMU overflow extension very
-- 
2.34.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

                 reply	other threads:[~2026-02-04  9:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260204091836.1713729-1-minachou@andestech.com \
    --to=minachou@andestech.com \
    --cc=anup@brainfault.org \
    --cc=atish.patra@linux.dev \
    --cc=az70021@gmail.com \
    --cc=ben717@andestech.com \
    --cc=cynthia@andestech.com \
    --cc=dminus@andestech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=tim609@andestech.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