public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Tomasz Stanislawski <t.stanislaws@samsung.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	devicetree-discuss@lists.ozlabs.org,
	Sylwester Nawrocki <snjw23@gmail.com>,
	Tuukka Toivonen <tuukka.toivonen@intel.com>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [ANN] Meeting minutes of the Cambourne meeting
Date: Tue, 30 Aug 2011 14:41:48 +0100	[thread overview]
Message-ID: <20110830134148.GA14976@sirena.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1108300018490.5065@axis700.grange>

On Tue, Aug 30, 2011 at 12:20:09AM +0200, Guennadi Liakhovetski wrote:
> On Mon, 29 Aug 2011, Laurent Pinchart wrote:

> > My idea was to let the kernel register all devices based on the DT or board 
> > code. When the V4L2 host/bridge driver gets registered, it will then call a 
> > V4L2 core function with a list of subdevs it needs. The V4L2 core would store 
> > that information and react to bus notifier events to notify the V4L2 
> > host/bridge driver when all subdevs are present. At that point the host/bridge 
> > driver will get hold of all the subdevs and call (probably through the V4L2 
> > core) their .registered operation. That's where the subdevs will get access to 
> > their clock using clk_get().

> Correct me, if I'm wrong, but this seems to be the case of sensor (and 
> other i2c-client) drivers having to succeed their probe() methods without 
> being able to actually access the hardware?

The events should only be generated after the probe() has succeeded so
if the driver talks to the hardware then it can fail probe() if need be.

  parent reply	other threads:[~2011-08-30 13:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 14:47 [ANN] Agenda for the Cambourne meeting Laurent Pinchart
2011-07-26 14:59 ` Laurent Pinchart
2011-08-08 15:50 ` [ANN] Meeting minutes of " Laurent Pinchart
2011-08-09  9:52   ` Subash Patel
2011-08-09 15:52     ` Sakari Ailus
     [not found]     ` <CAF5T7d=h=BBhmFNs3EBPMGzKAJg_fciq=iB_GKQGDB+oiL+XAg@mail.gmail.com>
2011-08-09 15:59       ` Sakari Ailus
     [not found]         ` <CAF5T7dkXFBkD8CtKLR5UNOtmjMiOC3F6gfryMvM6=sfybQDDnA@mail.gmail.com>
2011-08-10 10:25           ` Sakari Ailus
2011-08-10  9:36       ` Tuukka Toivonen
2011-08-11  7:38   ` Sakari Ailus
2011-08-28 11:28   ` Sylwester Nawrocki
2011-08-29 13:08     ` Laurent Pinchart
2011-08-29 22:20       ` Guennadi Liakhovetski
2011-08-29 22:26         ` Laurent Pinchart
2011-08-29 22:38           ` Guennadi Liakhovetski
2011-08-30 13:41         ` Mark Brown [this message]
2011-08-30 13:56           ` Grant Likely
2011-08-30 14:00             ` Mark Brown
2011-08-30 14:03             ` Guennadi Liakhovetski
2011-08-30 15:18               ` Grant Likely
2011-08-30 15:42                 ` Laurent Pinchart
2011-08-30 15:46                   ` Mark Brown
2011-08-30 20:12                     ` Laurent Pinchart
2011-08-30 20:19                       ` Mark Brown
     [not found]                         ` <CACxGe6v0Tm8oz5+vcrdjzk3x0DdvBoyeqEv=aZv=XEA=Ev7WpQ@mail.gmail.com>
2011-08-30 20:37                           ` Laurent Pinchart
2011-08-30 20:39                             ` Mark Brown
2011-08-30 15:59                   ` Guennadi Liakhovetski

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=20110830134148.GA14976@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mchehab@redhat.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sakari.ailus@maxwell.research.nokia.com \
    --cc=snjw23@gmail.com \
    --cc=t.stanislaws@samsung.com \
    --cc=tuukka.toivonen@intel.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