ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	ksummit-discuss@lists.linuxfoundation.org,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Tomasz Figa <t.figa@samsung.com>,
	Andrzej Hajda <a.hajda@samsung.com>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Tomasz Stanislawski <t.stanislaws@samsung.com>,
	Shuah Khan <shuahkhan@gmail.com>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] PM dependencies
Date: Mon, 12 May 2014 20:09:29 +0200	[thread overview]
Message-ID: <53710E59.5030601@gmail.com> (raw)
In-Reply-To: <1872038.43ncqEMWSx@avalon>

Hi,

On 12.05.2014 19:43, Laurent Pinchart wrote:
> Hello,
> 
> On modern systems many PM dependencies don't follow the Linux kernel device 
> model based on parent-child relationships from a control bus point of view. 
> For instance a GPU will need the IOMMU that services its memory requests to be 
> powered on to perform DMA operations.
> 
> Ad-hoc solutions with subsystem-specific or even driver-specific APIs have 
> been implemented (see omap_iommu_save_ctx and omap_iommu_restore_ctx in 
> include/linux/omap-iommu.h for instance, that push the burden of saving and 
> restoring the IOMMU registers to bus master drivers), but they make automatic 
> handling of hardware resources difficult. In the IOMMU case again, the goal is 
> to hide IOMMU handling inside the DMA mapping API and make its usage 
> completely transparent to bus master drivers in most of the cases. An IOMMU-
> specific API to explicitly control IOMMU power from the bus master driver 
> would make that goal impossible to reach.
> 
> The problem is not limited to IOMMUs. We have similar dependencies at 
> suspend/resume time with camera interfaces for instance, where two completely 
> unrelated device in the Linux device hierarchy (a camera interface platform 
> device in the SoC and an I2C camera sensor) need to be suspended and resumed 
> in a controlled order. I'm sure many more use cases exist.
> 
> Whether we can (partly) reuse existing infrastructure for this is not clear. 
> I'd like to gather use cases, to first find out exactly how widespread the 
> need is, and whether we can come up with a common solution or we are really 
> faced with different classes of similarly looking but distinct issues.
> 
> Tomasz Figa (CC'ed) has recently expressed interest for this topic, if he's 
> still interested I'd like to nominate him.

Yes, I'm still interested.

IOMMUs are the use case I've been wondering about recently, but I'd like
to take some time to analyze other use cases useful for Samsung
platforms. I will post them in another reply to this thread as soon as I
get to some interesting conclusions.

Best regards,
Tomasz

  parent reply	other threads:[~2014-05-12 18:09 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 17:43 Laurent Pinchart
2014-05-12 17:51 ` Shuah Khan
2014-05-18 15:42   ` Mauro Carvalho Chehab
2014-05-12 18:09 ` Tomasz Figa [this message]
2014-05-12 20:14 ` Mark Brown
2014-05-12 20:27   ` Laurent Pinchart
2014-05-12 20:31     ` Mark Brown
2014-05-12 21:16       ` Tomasz Figa
2014-05-12 22:07         ` Mark Brown
2014-05-13  7:43           ` Daniel Vetter
2014-05-13 10:31             ` Laurent Pinchart
2014-05-13 14:26               ` Shuah Khan
2014-05-15 23:43                 ` Laurent Pinchart
2014-05-19  1:00                   ` Shuah Khan
2014-05-19  7:30                     ` Geert Uytterhoeven
2014-05-13 22:27           ` Rafael J. Wysocki
2014-05-13 22:34             ` Rafael J. Wysocki
2014-05-14 12:59               ` Rafael J. Wysocki
2014-05-15 23:34               ` Laurent Pinchart
2014-05-20 16:57                 ` Kevin Hilman
2014-05-20 18:51                   ` Mark Brown
2014-05-21  9:26                   ` Ulf Hansson
2014-05-21 11:16                   ` Geert Uytterhoeven
2014-05-22  0:19                   ` Rafael J. Wysocki
2014-05-22 10:14                     ` Mark Brown
2014-05-23 23:15                       ` Rafael J. Wysocki
2014-05-24 10:53                         ` Mark Brown
2014-05-25 12:56                           ` Rafael J. Wysocki
2014-05-22 17:35                     ` Kevin Hilman
2014-05-23 23:26                       ` Rafael J. Wysocki
2014-05-23  0:18                   ` Laurent Pinchart
2014-05-23  0:39                     ` Kevin Hilman
2014-05-23  8:32                       ` Linus Walleij
2014-05-23 15:26                         ` Kevin Hilman
2014-05-24  0:13                           ` Rafael J. Wysocki
2014-05-24  0:08                         ` Rafael J. Wysocki
2014-05-26 14:30                         ` Peter De Schrijver
2014-05-23  8:25                     ` Linus Walleij
2014-05-23  9:10                       ` Ulf Hansson
2014-05-24  0:00                       ` Rafael J. Wysocki
2014-05-15 22:45             ` Laurent Pinchart
2014-05-14 21:08           ` Kevin Hilman
2014-05-14 12:11       ` Rafael J. Wysocki
2014-05-14 11:57         ` Mark Brown
2014-05-14 12:32           ` Rafael J. Wysocki
2014-05-14 15:14             ` Mark Brown
2014-05-14 15:26           ` Laurent Pinchart
2014-05-14 15:40             ` Mark Brown

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=53710E59.5030601@gmail.com \
    --to=tomasz.figa@gmail.com \
    --cc=a.hajda@samsung.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=m.szyprowski@samsung.com \
    --cc=s.nawrocki@samsung.com \
    --cc=shuahkhan@gmail.com \
    --cc=t.figa@samsung.com \
    --cc=t.stanislaws@samsung.com \
    /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