Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

[...] >>> To solve this problem, I was thinking we could convert to use the asynchronous pm_runtime_get() API, when trying to runtime resume the device from atomic contexts. >>> >>> I'm not sure if this will work for DMA engine devices. If I understand >>> correctly some client's

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

[...] >>> To solve this problem, I was thinking we could convert to use the asynchronous pm_runtime_get() API, when trying to runtime resume the device from atomic contexts. >>> >>> I'm not sure if this will work for DMA engine devices. If I understand >>> correctly some client's

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

Hi Ulf, On 2016-09-14 12:28, Ulf Hansson wrote: [...] There are some similarities between IOMMU and DMA engine devices (serial drivers are imho completely different case). Both hw blocks do their work on behalf of some other hardware block, which I will call master device. DMA engine

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

Hi Ulf, On 2016-09-14 12:28, Ulf Hansson wrote: [...] There are some similarities between IOMMU and DMA engine devices (serial drivers are imho completely different case). Both hw blocks do their work on behalf of some other hardware block, which I will call master device. DMA engine

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

[...] > > > There are some similarities between IOMMU and DMA engine devices (serial > drivers are imho completely different case). Both hw blocks do their work > on behalf of some other hardware block, which I will call master device. > DMA engine performs some DMA transaction on master's device

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

[...] > > > There are some similarities between IOMMU and DMA engine devices (serial > drivers are imho completely different case). Both hw blocks do their work > on behalf of some other hardware block, which I will call master device. > DMA engine performs some DMA transaction on master's device

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

Hi Ulf, On 2016-09-13 16:20, Ulf Hansson wrote: On 13 September 2016 at 14:49, Marek Szyprowski wrote: This patch uses recently introduced device links to track the runtime pm state of the master's device. This way each SYSMMU controller is runtime activated when its

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

Hi Ulf, On 2016-09-13 16:20, Ulf Hansson wrote: On 13 September 2016 at 14:49, Marek Szyprowski wrote: This patch uses recently introduced device links to track the runtime pm state of the master's device. This way each SYSMMU controller is runtime activated when its master's device is active

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

Hi Marek, [auto build test ERROR on iommu/next] [also build test ERROR on v4.8-rc6 next-20160913] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record what

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

Hi Marek, [auto build test ERROR on iommu/next] [also build test ERROR on v4.8-rc6 next-20160913] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for convenience) to record what

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

On 13 September 2016 at 14:49, Marek Szyprowski wrote: > This patch uses recently introduced device links to track the runtime pm > state of the master's device. This way each SYSMMU controller is runtime > activated when its master's device is active and can

Re: [PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

On 13 September 2016 at 14:49, Marek Szyprowski wrote: > This patch uses recently introduced device links to track the runtime pm > state of the master's device. This way each SYSMMU controller is runtime > activated when its master's device is active and can save/restore its state > instead of

[PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

This patch uses recently introduced device links to track the runtime pm state of the master's device. This way each SYSMMU controller is runtime activated when its master's device is active and can save/restore its state instead of being enabled all the time. This way SYSMMU controllers no longer

[PATCH v3 2/2] iommu/exynos: Add proper runtime pm support

This patch uses recently introduced device links to track the runtime pm state of the master's device. This way each SYSMMU controller is runtime activated when its master's device is active and can save/restore its state instead of being enabled all the time. This way SYSMMU controllers no longer