Re: [PATCHv7 05/12] iommu/core: add ops->{bound,unbind}_driver()

2013-12-30 Thread Joerg Roedel
On Thu, Dec 12, 2013 at 09:57:06AM +0200, Hiroshi Doyu wrote: > ops->{bound,unbind}_driver() functions are called at > BUS_NOTIFY_{BOUND,UNBIND}_DRIVER respectively. > > This is necessary to control the device population order. IOMMU master > devices depend on an IOMMU device instanciation. IOMMU

Re: [PATCHv7 05/12] iommu/core: add ops-{bound,unbind}_driver()

2013-12-30 Thread Joerg Roedel
On Thu, Dec 12, 2013 at 09:57:06AM +0200, Hiroshi Doyu wrote: ops-{bound,unbind}_driver() functions are called at BUS_NOTIFY_{BOUND,UNBIND}_DRIVER respectively. This is necessary to control the device population order. IOMMU master devices depend on an IOMMU device instanciation. IOMMU

Re: [PATCHv7 05/12] iommu/core: add ops->{bound,unbind}_driver()

2013-12-16 Thread Stephen Warren
On 12/12/2013 12:57 AM, Hiroshi Doyu wrote: > ops->{bound,unbind}_driver() functions are called at > BUS_NOTIFY_{BOUND,UNBIND}_DRIVER respectively. Some explanation re: why the existing {add,remove}_device hooks aren't enough would be useful. I didn't really get that from the current commit

Re: [PATCHv7 05/12] iommu/core: add ops-{bound,unbind}_driver()

2013-12-16 Thread Stephen Warren
On 12/12/2013 12:57 AM, Hiroshi Doyu wrote: ops-{bound,unbind}_driver() functions are called at BUS_NOTIFY_{BOUND,UNBIND}_DRIVER respectively. Some explanation re: why the existing {add,remove}_device hooks aren't enough would be useful. I didn't really get that from the current commit

[PATCHv7 05/12] iommu/core: add ops->{bound,unbind}_driver()

2013-12-12 Thread Hiroshi Doyu
ops->{bound,unbind}_driver() functions are called at BUS_NOTIFY_{BOUND,UNBIND}_DRIVER respectively. This is necessary to control the device population order. IOMMU master devices depend on an IOMMU device instanciation. IOMMU master devices can be registered to an IOMMU only after it's

[PATCHv7 05/12] iommu/core: add ops-{bound,unbind}_driver()

2013-12-12 Thread Hiroshi Doyu
ops-{bound,unbind}_driver() functions are called at BUS_NOTIFY_{BOUND,UNBIND}_DRIVER respectively. This is necessary to control the device population order. IOMMU master devices depend on an IOMMU device instanciation. IOMMU master devices can be registered to an IOMMU only after it's