From: Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
Magnus Damm <magnus.damm@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [RFC] media DT bindings
Date: Mon, 30 Jul 2012 23:02:26 +0200 [thread overview]
Message-ID: <5016F662.8030807@gmail.com> (raw)
In-Reply-To: <20120723121420.GC8302@sirena.org.uk>
On 07/23/2012 02:14 PM, Mark Brown wrote:
> On Wed, Jul 18, 2012 at 07:00:15PM +0200, Sylwester Nawrocki wrote:
>
>> One possible solution would be to have host/bridge drivers to register
>> a clkdev entry for I2C client device, so it can acquire the clock through
>> just clk_get(). We would have to ensure the clock is not tried to be
>> accessed before it is registered by a bridge. This would require to add
>> clock handling code to all sensor/encoder subdev drivers though..
>
> If this is done well it could just be a simple callback, and we could
> probably arrange for the framework to just implement the default
> behaviour if the driver doesn't do anything explicit.
I agree, if a clock is bound to a sub-device beforehand it could
probably be done with just a callback as well. Implementing default
behaviour at the framework makes a lot of sense too, it could ease
the conversion process significantly.
> Of couse this is one of those things where we really need the generic
> clock API to be generally available...
Indeed, I hope it won't take too much time before at least some of the
platforms get converted.
--
Thanks,
Sylwester
next prev parent reply other threads:[~2012-07-30 21:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.1207110854290.18999@axis700.grange>
2012-07-13 14:57 ` [RFC] media DT bindings Sylwester Nawrocki
2012-07-16 11:41 ` Guennadi Liakhovetski
2012-07-18 17:00 ` Sylwester Nawrocki
2012-07-23 12:14 ` Mark Brown
2012-07-30 21:02 ` Sylwester Nawrocki [this message]
2012-07-27 11:25 ` Laurent Pinchart
2012-07-31 9:26 ` Guennadi Liakhovetski
2012-07-31 12:08 ` Laurent Pinchart
2012-07-31 12:39 ` Guennadi Liakhovetski
2012-07-31 21:22 ` Laurent Pinchart
2012-07-31 23:29 ` Stephen Warren
2012-08-01 5:59 ` Laurent Pinchart
2012-08-01 15:57 ` Stephen Warren
2012-08-01 6:47 ` Guennadi Liakhovetski
2012-08-01 7:19 ` Laurent Pinchart
2012-08-04 9:27 ` 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=5016F662.8030807@gmail.com \
--to=sylvester.nawrocki@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski@gmx.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).