[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lfhfl3yv.wl-maz@kernel.org>
Date: Sat, 12 Sep 2020 10:49:28 +0100
From: Marc Zyngier <maz@...nel.org>
To: Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>
Cc: tglx@...utronix.de, jason@...edaemon.net, s-anna@...com,
robh+dt@...nel.org, lee.jones@...aro.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
david@...hnology.com, praneeth@...com
Subject: Re: [RESEND PATCH v5 4/5] irqchip/irq-pruss-intc: Implement irq_{get,set}_irqchip_state ops
On Mon, 31 Aug 2020 16:09:17 +0100,
Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org> wrote:
>
> From: David Lechner <david@...hnology.com>
>
> This implements the irq_get_irqchip_state and irq_set_irqchip_state
> callbacks for the TI PRUSS INTC driver. The set callback can be used
> by drivers to "kick" a PRU by injecting a PRU system event.
>
> Example:
> irq_set_irqchip_state(irq, IRQCHIP_STATE_PENDING, true);
>
Please drop this "example", it brings nothing without the full
context. This patch just implements a standard callback.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists