From: sashiko-bot@kernel.org
To: "Rosen Penev" <rosenp@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 3/4] irqchip/ath79-misc: convert to a platform driver
Date: Sat, 14 Nov 2026 23:47:32 +0000 [thread overview]
Message-ID: <sashiko-outbox-215126@kernel.org> (raw)
In-Reply-To: <20261114233718.86520-4-rosenp@gmail.com>
> The MISC interrupt controller is cascaded from a CPU interrupt, and its
> users are all platform devices, which defer their probe until it is
> available. The performance counter interrupt, the only one needed
> before the early initcalls, is now mapped on demand.
>
> Probe the controller as a platform driver, and use device-managed
> resources, which also fixes the leak of the register mapping when the
> irq domain cannot be created.
>
> The driver now probes after plat_time_init(), which on QCA956x and
> TP9343 enables the MIPS timer interrupt in the MISC controller, without
> which there are no jiffies. Keep that enable bit when disabling the
> other interrupts, which leaves the register as it was with the old init
> order.
>
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261114233718.86520-1-rosenp@gmail.com?part=3
next prev parent reply other threads:[~2026-11-14 23:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 23:37 [PATCH v2 0/4] irqchip/ath79-misc: probe as a platform driver Rosen Penev
2026-11-14 23:37 ` [PATCH v2 1/4] MIPS: perf: look up the PMU interrupt when it is requested Rosen Penev
2026-11-14 23:37 ` [PATCH v2 2/4] irqchip/ath79-misc: map the performance counter interrupt on demand Rosen Penev
2026-11-14 23:45 ` sashiko-bot
2026-11-14 23:37 ` [PATCH v2 3/4] irqchip/ath79-misc: convert to a platform driver Rosen Penev
2026-11-14 23:47 ` sashiko-bot [this message]
2026-11-14 23:37 ` [PATCH v2 4/4] irqchip/ath79-misc: allow COMPILE_TEST builds Rosen Penev
2026-11-14 23:44 ` sashiko-bot
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=sashiko-outbox-215126@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.