On Mon, Feb 08, 2016 at 10:08:28PM +0530, Laxman Dewangan wrote:

On Monday 08 February 2016 08:25 PM, Mark Brown wrote:

quoted

On Sat, Feb 06, 2016 at 08:07:22PM +0530, Laxman Dewangan wrote:

quoted

quoted

Before removing irq domains, it is require to unmap all
mapped interrupt from that domain. Currently there is API
to map the interrupt on chip as regmap_irq_get_virq() for
creating mapping. Add equivalent API to dispose the mapped
irq in irq domains.

quoted

This makes no sense to me.  Why would you ever want to unmap the
interrupts separately to destroying the domain

This is the requirement from irq_domain_remove(). This is what we have in
irq_domain_remove():
kernel/irq/irqdomain.c

I am adding the API equivalent to regmap_irq_get_virq() to unmap virtual irq
here.

This does not explain why anyone would ever want to use this interface
(which was my question), why would anyone ever want to do this as a
separate step?

quoted

and why would you ever
want to destroy the domain without unmapping the interrupts?

That's exactlly we are trying to do, unmap interrupt in client level before
destroying domain.

Again, why would any client ever want to skip this step? 

-- 
-- 
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
--- 
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.