[PATCH 06/15] irqdomain: Ensure type settings match for an existing mapping

2016-03-19 Thread Jon Hunter
When mapping an IRQ, if a mapping already exists, then we simply return the virtual IRQ number. However, we do not check that the type settings for the existing mapping match those for the mapping that is about to be created. It may be unlikely that the type settings would not match, but check for

Re: [PATCH 06/15] irqdomain: Ensure type settings match for an existing mapping

2016-03-19 Thread Jon Hunter
On 18/03/16 10:03, Grygorii Strashko wrote: > On 03/17/2016 08:18 PM, Jon Hunter wrote: >> >> On 17/03/16 14:19, Jon Hunter wrote: >>> When mapping an IRQ, if a mapping already exists, then we simply return >>> the virtual IRQ number. However, we do not check that the type settings >>> for the exi

Re: [PATCH 06/15] irqdomain: Ensure type settings match for an existing mapping

2016-03-19 Thread Grygorii Strashko
On 03/17/2016 08:18 PM, Jon Hunter wrote: On 17/03/16 14:19, Jon Hunter wrote: When mapping an IRQ, if a mapping already exists, then we simply return the virtual IRQ number. However, we do not check that the type settings for the existing mapping match those for the mapping that is about to be

Re: [PATCH 06/15] irqdomain: Ensure type settings match for an existing mapping

2016-03-19 Thread Jon Hunter
On 17/03/16 14:19, Jon Hunter wrote: > When mapping an IRQ, if a mapping already exists, then we simply return > the virtual IRQ number. However, we do not check that the type settings > for the existing mapping match those for the mapping that is about to be > created. It may be unlikely that the