public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/2] iommu: rockchip: Handle system-wide and runtime PM
Date: Sat, 20 Dec 2014 21:01:06 +0200	[thread overview]
Message-ID: <3922440.p7KFeqxHrO@avalon> (raw)
In-Reply-To: <8712967.RZO6JKCTcJ@vostro.rjw.lan>

Hi Kevin,

On Friday 19 December 2014 03:27:35 Rafael J. Wysocki wrote:
> On Thursday, December 18, 2014 11:28:58 PM Laurent Pinchart wrote:
> > Hi Kevin,
> 
> [cut]
> 
>>>>> It would be better to be able to reference count the DMA engine from
>>>>> the bus master IMO and arguably you can use the runtime PM framework
>>>>> for that. Namely, give bus masters someting like
>>>>> 
>>>>> 	pm_runtime_get_my_DMA_engine(bus_master_device)
>>>>> 	pm_runtime_put_my_DMA_engine(bus_master_device)
>>>>> 
>>>>> and let them call these as they see fit.
>>>> 
>>>> Please note that we're not talking about DMA engines here, but about
>>>> IOMMUs. DMA is involved through the DMA mapping API which hides the
>>>> IOMMU completely from the bus master drivers, not the DMA engine API.
>>>> 
>>>> Exposing the IOMMU is something we want to avoid, but DMA mapping
>>>> start/stop operations could certainly be implemented.
>>> 
>>> The problem with that is it only solves the IOMMU problem.  We have a
>>> more generic PM dependency problem of which this IOMMU example is only a
>>> subset, so I think we need a more generic solution.
>> 
>> I agree that a more generic solution is needed at least to support ACPI
>> _DEP, but that might not be optimal in the IOMMU use case as explained
>> above.
>
> Well, since we need it anyway, why don't we implement it and then figure out
> if anything more specific needs to be done for the IOMMU case?

Patches are welcome ;-)

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2014-12-20 19:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  8:26 [RFC PATCH 0/2] Fix rockchip IOMMU driver vs PM issues Tomasz Figa
2014-12-11  8:26 ` [RFC PATCH 1/2] pm: Add PM domain notifications Tomasz Figa
2014-12-11 10:36   ` Sylwester Nawrocki
2014-12-11 11:04     ` Tomasz Figa
2014-12-11 13:54       ` Sylwester Nawrocki
2014-12-11 15:30         ` Ulf Hansson
2014-12-11  8:26 ` [RFC PATCH 2/2] iommu: rockchip: Handle system-wide and runtime PM Tomasz Figa
2014-12-11 11:58   ` Ulf Hansson
2014-12-11 12:42     ` Tomasz Figa
2014-12-11 15:22       ` Ulf Hansson
2014-12-11 15:31       ` Kevin Hilman
2014-12-11 15:51         ` Ulf Hansson
2014-12-11 20:48           ` Rafael J. Wysocki
2014-12-12  4:15             ` Tomasz Figa
2014-12-12 20:04               ` Kevin Hilman
2014-12-15  2:32                 ` Tomasz Figa
2014-12-15  8:35                 ` Geert Uytterhoeven
2014-12-15 18:06                   ` Kevin Hilman
2014-12-12 20:47               ` Laurent Pinchart
2014-12-15  2:39                 ` Tomasz Figa
2014-12-15 19:53                   ` Laurent Pinchart
2014-12-16  2:18                     ` Tomasz Figa
2014-12-17  0:15                       ` Laurent Pinchart
2014-12-18  1:32                         ` Rafael J. Wysocki
2014-12-18 19:12                           ` Laurent Pinchart
2014-12-18 21:14                             ` Kevin Hilman
2014-12-18 21:28                               ` Laurent Pinchart
2014-12-19  2:27                                 ` Rafael J. Wysocki
2014-12-20 19:01                                   ` Laurent Pinchart [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3922440.p7KFeqxHrO@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox