public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Anssi Hannula <anssi.hannula@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Greg KH <greg@kroah.com>, Hans Verkuil <hverkuil@xs4all.nl>,
	Hans de Goede <j.w.r.degoede@hhs.nl>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-media@vger.kernel.org,
	Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
Subject: Re: How to handle devices sitting on multiple busses ?
Date: Tue, 25 Aug 2009 12:47:22 +0300	[thread overview]
Message-ID: <4A93B32A.5060102@gmail.com> (raw)
In-Reply-To: <200908241357.44562.laurent.pinchart@ideasonboard.com>

Laurent Pinchart wrote:
[...]
> As the bridge and I2C master live their own life in the Linux device tree, 
> they are initialized, suspended, resumed and destroyed independently. The 
> sensor being an I2C slave device, Linux initializes it after the I2C master 
> device is initialized, but doesn't ensure that the bridge is initialized first 
> as well. A similar problem occurs during suspend/resume, as the I2C slave 
> needs to be suspended before and resumed after the video bridge.
> 
> Have you ever encountered such a situation before ? Is there a clean way for a 
> device to have multiple parents, or do you have plans for such a possibility 
> in the future ? I would be willing to give an implementation a try if you can 
> provide me with some guidelines.
> 

It looks to me like this patch is related to your problem:
http://article.gmane.org/gmane.linux.power-management.general/15651

With a quick glance it doesn't seem to involve changes in device
initialization or destroying, though, but this is not really my area of
expertise.

-- 
Anssi Hannula

      parent reply	other threads:[~2009-08-25  9:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 11:57 How to handle devices sitting on multiple busses ? Laurent Pinchart
2009-08-24 16:16 ` Greg KH
2009-08-25  9:47 ` Anssi Hannula [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=4A93B32A.5060102@gmail.com \
    --to=anssi.hannula@gmail.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=greg@kroah.com \
    --cc=hverkuil@xs4all.nl \
    --cc=j.w.r.degoede@hhs.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@maxwell.research.nokia.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