From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: florian.vaussard@epfl.ch
Cc: Enrico <ebutera@users.berlios.de>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Sebastian Reichel <sre@debian.org>
Subject: Re: omap3isp device tree support
Date: Thu, 09 Jan 2014 21:49:09 +0100 [thread overview]
Message-ID: <4572159.CqBuj6p70x@avalon> (raw)
In-Reply-To: <52CF0612.2020303@epfl.ch>
Hi Florian,
On Thursday 09 January 2014 21:26:58 Florian Vaussard wrote:
> On 01/07/2014 05:59 PM, Laurent Pinchart wrote:
> > On Friday 03 January 2014 12:30:33 Enrico wrote:
> >> On Wed, Dec 18, 2013 at 11:09 AM, Enrico wrote:
> >>> On Tue, Dec 17, 2013 at 2:11 PM, Florian Vaussard wrote:
> >>>> So I converted the iommu to DT (patches just sent),
> >
> > Florian, I've used your patches as a base for OMAP3 ISP DT work and they
> > seem pretty good (although patch 1/7 will need to be reworked, but that's
> > not a blocker). I've just had to fix a problem with the OMAP3 IOMMU,
> > please see
> >
> > http://git.linuxtv.org/pinchartl/media.git/commit/d3abafde0277f168df0b2912
> > b5d84550590d80b2
>
> According to the comments on the IOMMU/DT patches [1], some work is still
> needed to merge these patches, mainly to support other IOMMUs (OMAP4,
> OMAP5).
Sure, the code need to be reworked, but I believe it's going in the right
direction and shouldn't be too complex to fix.
> So the current base is probably ok. I will resume my work on this soon.
Great, thanks.
> What are your comments on patch 1?
I just agree with Suman that there can be multiple IOMMUs and that the
bus_set_iommu() call should thus be kept in the init function. The current
infrastructure allows multiple IOMMUs to coexist as long as they're of the
same type (I'm pretty sure we'll have to fix that at some point). I believe
the problem that patch 1/7 tries to fix is actually the right behaviour.
> I briefly looked at your fix, seems ok to me. I do not figure out how it
> worked for me.
I was puzzled by that as well :-)
> I will look at it closer next week.
>
> > I'd appreciate your comments on that. I can post the patch already if you
> > think that would be helpful.
>
> It is probably better to wait for the v2 of the iommu series. I can include
> your patch in it.
Please feel free to do so.
> > You can find my work-in-progress branch at
> >
> > http://git.linuxtv.org/pinchartl/media.git/shortlog/refs/heads/omap3isp/dt
> >
> > (the last three patches are definitely not complete yet).
>
> Great news! A while ago, Sebastian Reichel (in CC) posted an RFC for the
> binding [2]. Are you working with him on this?
No, I've replied to Sebastian's patch but haven't received any answer. My main
concern is that the proposal didn't use the V4L2 DT bindings to describe the
pipeline.
> [1] https://lkml.org/lkml/2013/12/17/197
> [2] http://thread.gmane.org/gmane.linux.drivers.devicetree/50580
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-01-09 20:48 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
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 [this message]
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=4572159.CqBuj6p70x@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ebutera@users.berlios.de \
--cc=florian.vaussard@epfl.ch \
--cc=linux-media@vger.kernel.org \
--cc=sre@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox