From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-media@vger.kernel.org
Subject: Re: soc_camera and device-tree
Date: Sun, 15 Jun 2014 16:02:32 +0200 [thread overview]
Message-ID: <87ioo2tgnb.fsf@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.1406142256010.23099@axis700.grange> (Guennadi Liakhovetski's message of "Sat, 14 Jun 2014 22:58:27 +0200 (CEST)")
Guennadi Liakhovetski <g.liakhovetski@gmx.de> writes:
> Hi Robert,
>
> On Sat, 14 Jun 2014, Robert Jarzmik wrote:
>
>> Hi Guennadi,
>>
>> I'm slowly converting all of my drivers to device-tree.
>> In the process, I met ... soc_camera.
>>
>> I converted mt9m111.c and pxa_camera.c, but now I need the linking
>> soc_camera. And I don't have a clear idea on how it should be done.
>
> Have a look at this thread
>
> http://thread.gmane.org/gmane.linux.ports.sh.devel/34412/focus=36244
Ah excellent, job's done before working, just as I like it :)
Just a couple of remarks :
- in Ben's serie, there is/are call(s) to v4l2_of_get_next_endpoint().
This was recently replaced with of_graph_get_next_endpoint().
Same story for v4l2_of_get_remote_port() replaced by
of_graph_get_remote_port().
See commit "[media] of: move graph helpers from drivers/media/v4l2-core to
drivers/of", commit id fd9fdb7.
- the clock "mclk" topic
There will be cases where this SoC clock won't be available in the common
clock framework, ie. not in drivers/clk. For example the PXA architecture is
not yet ported to the commmon clk framework (it's in the staging).
So we should be carefull to not assume common clock framework is available.
- the testing coverage
For the next spin I'd like to be joined to the list of reviewers/testers. As
I'm testing it for another couple of host/icd, that will grow up the test
base.
Cheers.
--
Robert
next prev parent reply other threads:[~2014-06-15 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 20:30 soc_camera and device-tree Robert Jarzmik
2014-06-14 20:58 ` Guennadi Liakhovetski
2014-06-15 14:02 ` Robert Jarzmik [this message]
2014-06-15 19:20 ` Guennadi Liakhovetski
2014-06-15 19:59 ` Ben Dooks
2014-06-15 19:19 ` Ben Dooks
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=87ioo2tgnb.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=ben.dooks@codethink.co.uk \
--cc=g.liakhovetski@gmx.de \
--cc=linux-media@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.