mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Artur Rojek <contact@artur-rojek.eu>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Rich Felker <dalias@libc.org>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Uros Bizjak <ubizjak@gmail.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	"D . Jeff Dionne" <jeff@coresemi.io>,
	Rob Landley <rob@landley.net>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] irqchip: clocksource: fix jcore-pit irq request
Date: Wed, 19 Feb 2025 15:43:37 +0100	[thread overview]
Message-ID: <d7484ab2-6da0-4bb9-a2ae-9388dac15038@linaro.org> (raw)
In-Reply-To: <20250216175545.35079-3-contact@artur-rojek.eu>

On 16/02/2025 18:55, Artur Rojek wrote:
> The jcore-aic irqchip does not have separate interrupt numbers reserved
> for cpu-local vs global interrupts. Instead, the task of selecting this
> property is being delegated to the device drivers requesting the given
> irq.
> 
> This quirk has not been taken into account while migrating jcore-pit to
> request_percpu_irq(), resulting in a failure to register PIT interrupts.
> 
> Fix this behavior by making the following changes:
> 1) Explicitly register irq_set_percpu_devid() in jcore-pit.
> 2) Provide enable_percpu_irq()/disable_percpu_irq() calls in jcore-pit.
> 3) Make jcore-aic pass the correct per-cpu cookie to the irq handler by
>     using handle_percpu_devid_irq() instead of handle_percpu_irq().
> 
> Fixes: 69a9dcbd2d65 ("clocksource/drivers/jcore: Use request_percpu_irq()")
> 
> Signed-off-by: Artur Rojek <contact@artur-rojek.eu>
> ---

How this patch should be merged ?

It is touching irqchip and clocksource at the same time.

May I pick it in the clocksource tree ?


-- 
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  parent reply	other threads:[~2025-02-19 14:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-16 17:55 [PATCH 0/2] J2 Turtle Board fixes Artur Rojek
2025-02-16 17:55 ` [PATCH 1/2] sh: align .bss section padding to 8-byte boundary Artur Rojek
2025-02-18 12:41   ` Rob Landley
2025-03-11 17:28   ` John Paul Adrian Glaubitz
2025-03-11 23:40     ` Artur Rojek
2025-03-12  8:06       ` Geert Uytterhoeven
2025-03-13 10:36         ` John Paul Adrian Glaubitz
2025-03-12  8:21       ` John Paul Adrian Glaubitz
2025-03-12  8:32         ` Uros Bizjak
2025-03-12  8:44           ` John Paul Adrian Glaubitz
2025-03-12  9:47           ` Geert Uytterhoeven
2025-03-12  9:55             ` Uros Bizjak
2025-03-13  9:38             ` David Laight
2025-04-05 17:38   ` John Paul Adrian Glaubitz
2025-02-16 17:55 ` [PATCH 2/2] irqchip: clocksource: fix jcore-pit irq request Artur Rojek
2025-02-17  7:14   ` Uros Bizjak
2025-02-17 22:35   ` [tip: irq/urgent] irqchip/jcore-aic, clocksource/drivers/jcore: Fix jcore-pit interrupt request tip-bot2 for Artur Rojek
2025-02-18 12:43   ` [PATCH 2/2] irqchip: clocksource: fix jcore-pit irq request Rob Landley
2025-02-19 14:43   ` Daniel Lezcano [this message]
2025-02-19 14:50     ` Geert Uytterhoeven
2025-02-19 14:52       ` Daniel Lezcano
2025-02-27  7:52 ` [PATCH 0/2] J2 Turtle Board fixes John Paul Adrian Glaubitz
2025-02-28  3:03   ` Rob Landley
2025-02-28  8:34     ` John Paul Adrian Glaubitz
2025-02-28 22:19       ` Rob Landley
2025-02-28 22:34         ` John Paul Adrian Glaubitz
2025-03-01  3:20           ` Rob Landley
2025-04-08 15:23         ` John Paul Adrian Glaubitz
2025-04-11 11:25           ` Rob Landley
2025-06-09 10:01             ` John Paul Adrian Glaubitz
2025-06-10 20:22               ` Rob Landley

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=d7484ab2-6da0-4bb9-a2ae-9388dac15038@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=contact@artur-rojek.eu \
    --cc=dalias@libc.org \
    --cc=geert+renesas@glider.be \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jeff@coresemi.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=tglx@linutronix.de \
    --cc=ubizjak@gmail.com \
    --cc=ysato@users.sourceforge.jp \
    /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®