From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
hvaibhav@ti.com, linux-media@vger.kernel.org,
linux-omap@vger.kernel.org, Archit Taneja <archit@ti.com>,
mchehab@redhat.com
Subject: Re: [PATCH 0/2] omap_vout: remove cpu_is_* uses
Date: Thu, 29 Nov 2012 17:39:45 +0100 [thread overview]
Message-ID: <2148719.6v36XORg4e@avalon> (raw)
In-Reply-To: <20121129162927.GF5312@atomide.com>
Hi Tony,
On Thursday 29 November 2012 08:29:27 Tony Lindgren wrote:
> * Laurent Pinchart <laurent.pinchart@ideasonboard.com> [121129 01:37]:
> > On Thursday 29 November 2012 11:30:28 Tomi Valkeinen wrote:
> > > On 2012-11-28 17:13, Laurent Pinchart wrote:
> > > > On Monday 12 November 2012 15:33:38 Tomi Valkeinen wrote:
> > > >> Hi,
> > > >>
> > > >> This patch removes use of cpu_is_* funcs from omap_vout, and uses
> > > >> omapdss's version instead. The other patch removes an unneeded
> > > >> plat/dma.h include.
> > > >>
> > > >> These are based on current omapdss master branch, which has the
> > > >> omapdss version code. The omapdss version code is queued for v3.8.
> > > >> I'm not sure which is the best way to handle these patches due to the
> > > >> dependency to omapdss. The easiest option is to merge these for 3.9.
> > > >>
> > > >> There's still the OMAP DMA use in omap_vout_vrfb.c, which is the last
> > > >> OMAP dependency in the omap_vout driver. I'm not going to touch that,
> > > >> as it doesn't look as trivial as this cpu_is_* removal, and I don't
> > > >> have much knowledge of the omap_vout driver.
> > > >>
> > > >> Compiled, but not tested.
> > > >
> > > > Tested on a Beagleboard-xM.
> > > >
> > > > Tested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > > > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > >
> > > Thanks.
> > >
> > > > The patches depend on unmerged OMAP DSS patches. Would you like to
> > > > push this series through linuxtv or through your DSS tree ? The later
> > > > might be easier, depending on when the required DSS patches will hit
> > > > mainline.
> > >
> > > The DSS patches will be merged for 3.8. I can take this via the omapdss
> > > tree, as there probably won't be any conflicts with other v4l2 stuff.
> > >
> > > Or, we can just delay these until 3.9. These patches remove omap
> > > platform dependencies, helping the effort to get common ARM kernel.
> > > However, as there's still the VRFB code in the omap_vout driver, the
> > > dependency remains. Thus, in way, these patches alone don't help
> > > anything, and we could delay these for 3.9 and hope that
> > > omap_vout_vrfb.c gets converted also for that merge window.
> >
> > OK, I'll queue them for v3.9 then.
>
> Please rather queue the cpu_is_omap removal to v3.8 so I can
> remove plat/cpu.h for omap2+.
In that case the patches should go through the DSS tree. Mauro, are you fine
with that ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-11-29 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 13:33 [PATCH 0/2] omap_vout: remove cpu_is_* uses Tomi Valkeinen
2012-11-12 13:33 ` [PATCH 1/2] [media] omap_vout: use omapdss's version instead of cpu_is_* Tomi Valkeinen
2012-11-12 13:33 ` [PATCH 2/2] [media] omap_vout: remove extra include Tomi Valkeinen
2012-11-12 17:37 ` [PATCH 0/2] omap_vout: remove cpu_is_* uses Tony Lindgren
2012-11-28 15:13 ` Laurent Pinchart
2012-11-29 9:30 ` Tomi Valkeinen
2012-11-29 9:36 ` Laurent Pinchart
2012-11-29 16:29 ` Tony Lindgren
2012-11-29 16:39 ` Laurent Pinchart [this message]
2012-11-29 17:05 ` Mauro Carvalho Chehab
2012-11-29 17:08 ` Tomi Valkeinen
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=2148719.6v36XORg4e@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=archit@ti.com \
--cc=hvaibhav@ti.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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).