Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1580370
| From | Marek Szyprowski <m.szyprowski@samsung.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM |
| Date | 2017-02-14 09:00 +0100 |
| Message-ID | <taGbL-7gH-3@gated-at.bofh.it> (permalink) |
| References | (6 earlier) <taefv-5FQ-5@gated-at.bofh.it> <tamPN-2Yu-39@gated-at.bofh.it> <tanVv-3DB-1@gated-at.bofh.it> <taqTo-5xK-29@gated-at.bofh.it> <tarcK-5Fx-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Vinod, On 2017-02-13 16:47, Vinod Koul wrote: > On Mon, Feb 13, 2017 at 04:32:32PM +0100, Ulf Hansson wrote: >> [...] >> >>>> Although, I don't know of other examples, besides the runtime PM use >>>> case, where non-atomic channel prepare/unprepare would make sense. Do >>>> you? >>> The primary ask for that has been to enable runtime_pm for drivers. It's not >>> a new ask, but we somehow haven't gotten around to do it. >> Okay, I see. >> >>>>> As I said earlier, if we want to solve that problem a better idea is to >>>>> actually split the prepare as we discussed in [1] >>>>> >>>>> This way we can get a non atomic descriptor allocate/prepare and release. >>>>> Yes we need to redesign the APIs to solve this, but if you guys are up for >>>>> it, I think we can do it and avoid any further round abouts :) >>>> Adding/re-designing dma APIs is a viable option to solve the runtime PM case. >>>> >>>> Changes would be needed for all related dma client drivers as well, >>>> although if that's what we need to do - let's do it. >>> Yes, but do bear in mind that some cases do need atomic prepare. The primary >>> cases for DMA had that in mind and also submitting next transaction from the >>> callback (tasklet) context, so that won't go away. >>> >>> It would help in other cases where clients know that they will not be in >>> atomic context so we provide additional non-atomic "allocation" followed by >>> prepare, so that drivers can split the work among these and people can do >>> runtime_pm and other things.. >> That for sharing the details. >> >> It seems like some dma expert really need to be heavily involved if we >> ever are going to complete this work. :-) > Sure, I will help out :) > > If anyone of you are in Portland next week, then we can discuss these f2f. I > will try taking a stab at the new API design next week. I'm not going to Portland, but I hope that you will have a fruitful discussion there. [...] Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Marek Szyprowski <m.szyprowski@samsung.com> - 2017-02-09 15:30 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Vinod Koul <vinod.koul@intel.com> - 2017-02-10 06:00 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Marek Szyprowski <m.szyprowski@samsung.com> - 2017-02-10 13:00 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Ulf Hansson <ulf.hansson@linaro.org> - 2017-02-10 15:00 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Vinod Koul <vinod.koul@intel.com> - 2017-02-13 03:10 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Ulf Hansson <ulf.hansson@linaro.org> - 2017-02-13 12:20 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Marek Szyprowski <m.szyprowski@samsung.com> - 2017-02-13 13:20 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Vinod Koul <vinod.koul@intel.com> - 2017-02-13 13:40 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Vinod Koul <vinod.koul@intel.com> - 2017-02-13 13:30 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Ulf Hansson <ulf.hansson@linaro.org> - 2017-02-13 16:40 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Vinod Koul <vinod.koul@intel.com> - 2017-02-13 17:00 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Marek Szyprowski <m.szyprowski@samsung.com> - 2017-02-14 09:00 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Ulf Hansson <ulf.hansson@linaro.org> - 2017-02-14 09:30 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Marek Szyprowski <m.szyprowski@samsung.com> - 2017-02-13 13:10 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Marek Szyprowski <m.szyprowski@samsung.com> - 2017-02-13 12:50 +0100
Re: [PATCH v8 3/3] dmaengine: pl330: Don't require irq-safe runtime PM Ulf Hansson <ulf.hansson@linaro.org> - 2017-02-13 16:20 +0100
csiph-web