[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181123163742.GC53235@atomide.com>
Date: Fri, 23 Nov 2018 08:37:42 -0800
From: Tony Lindgren <tony@...mide.com>
To: Roger Quadros <rogerq@...com>
Cc: robh+dt@...nel.org, bcousson@...libre.com, ssantosh@...nel.org,
ohad@...ery.com, bjorn.andersson@...aro.org, s-anna@...com,
nsekhar@...com, t-kristo@...com, nsaulnier@...com, jreeder@...com,
m-karicheri2@...com, woods.technical@...il.com,
linux-omap@...r.kernel.org, linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 08/17] soc: ti: pruss: Add a PRUSS irqchip driver for
PRUSS interrupts
* Roger Quadros <rogerq@...com> [181122 11:39]:
> The PRUSS INTC module is reference counted during the interrupt
> setup phase through the irqchip's irq_request_resources() and
> irq_release_resources() ops. This restricts the module from being
> removed as long as there are active interrupt users.
So are there any reasons why this could not be just a regular
drivers/irqchip driver nowadays?
Regards,
Tony
Powered by blists - more mailing lists