From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Enrico <ebutera@users.berlios.de>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: omap3isp device tree support
Date: Tue, 17 Dec 2013 14:11:12 +0100 [thread overview]
Message-ID: <52B04D70.8060201@epfl.ch> (raw)
In-Reply-To: <CA+2YH7vDjCuTPwO9hDv-sM6ALAS_q-ZW2V=uq4MKG=75KD3xKg@mail.gmail.com>
Hello Enrico,
On 12/06/2013 11:54 AM, Enrico wrote:
> On Fri, Dec 6, 2013 at 11:31 AM, Florian Vaussard
> <florian.vaussard@epfl.ch> wrote:
>> Hello,
>>
>> On 12/06/2013 11:13 AM, Enrico wrote:
>>> Hi,
>>>
>>> i know there is some work going on for omap3isp device tree support,
>>> but right now is it possible to enable it in some other way in a DT
>>> kernel?
>>>
>>
>> The DT support is not yet ready, but an RFC binding has been proposed.
>> It won't be ready for 3.14.
>>
>>> I've tried enabling it in board-generic.c (omap3_init_camera(...) with
>>> proper platform data) but it hangs early at boot, do someone know if
>>> it's possible and how to do it?
>>>
>>
>> I did the same a few days ago, and went through several problems
>> (panics, half DT support,...). Now I am able to probe the ISP, I still
>> have one kernel panic to fix. Hope to send the patches in 1 or 2 days.
>> We are still in a transition period, but things should calm down in the
>> coming releases.
>>
So I converted the iommu to DT (patches just sent), used pdata quirks
for the isp / mtv9032 data, added a few patches from other people
(mainly clk to fix a crash when deferring the omap3isp probe), and a few
small hacks. I get a 3.13-rc3 (+ board-removal part from Tony Lindgren)
to boot on DT with a working MT9V032 camera. The missing part is the DT
binding for the omap3isp, but I guess that we will have to wait a bit
more for this.
If you want to test, I have a development tree here [1]. Any feedback is
welcome.
Cheers,
Florian
[1] https://github.com/vaussard/linux/commits/overo-for-3.14/iommu/dt
next prev parent reply other threads:[~2013-12-17 13:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 10:13 omap3isp device tree support Enrico
2013-12-06 10:31 ` Florian Vaussard
2013-12-06 10:54 ` Enrico
2013-12-17 13:11 ` Florian Vaussard [this message]
2013-12-18 10:09 ` Enrico
2013-12-23 17:45 ` Enrico
2013-12-23 18:33 ` Enrico
2014-01-03 11:30 ` Enrico
2014-01-06 10:11 ` Julien BERAUD
2014-01-07 10:12 ` Enrico
2014-01-08 11:55 ` Julien BERAUD
2014-01-09 18:14 ` Enrico
2014-01-10 9:02 ` Julien BERAUD
2014-02-07 10:24 ` Enrico
2014-01-07 16:59 ` Laurent Pinchart
2014-01-09 20:26 ` Florian Vaussard
2014-01-09 20:49 ` Laurent Pinchart
2014-01-09 20:54 ` Florian Vaussard
2014-01-09 21:30 ` Sebastian Reichel
2014-01-09 23:14 ` Enrico
2014-01-10 0:00 ` Laurent Pinchart
2013-12-09 13:11 ` Laurent Pinchart
[not found] <CALFbYK1kEnB2_3VqpLFNtaJ7hj9UHuhrL0iO_rFHD2VFt8THFw@mail.gmail.com>
2014-08-05 22:19 ` Laurent Pinchart
[not found] ` <CALFbYK3YtrDPGxc3UpASk7MgPTBGcd899Crvm1csY8g+j-fehg@mail.gmail.com>
2014-08-05 22:41 ` Laurent Pinchart
2014-08-05 22:50 ` alaganraj sandhanam
[not found] ` <1407284947.78794.YahooMailNeo@web162403.mail.bf1.yahoo.com>
2014-08-06 18:40 ` Alaganraj Sandhanam
2014-08-07 0:18 ` Sakari Ailus
2014-08-07 14:39 ` Alaganraj Sandhanam
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=52B04D70.8060201@epfl.ch \
--to=florian.vaussard@epfl.ch \
--cc=ebutera@users.berlios.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.