linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Move IPUv3 core out of staging, add CSI support
Date: Fri, 20 Dec 2013 19:12:29 +0000	[thread overview]
Message-ID: <20131220191229.GA27254@kroah.com> (raw)
In-Reply-To: <1387561966-31758-1-git-send-email-p.zabel@pengutronix.de>

On Fri, Dec 20, 2013 at 06:52:41PM +0100, Philipp Zabel wrote:
> Hi,
> 
> this is mostly about the first patch, which moves the IPUv3 core code
> (drivers/staging/imx-drm/ipu-v3) to drivers/gpu. host1x, which
> serves a similar purpose, already sits there.
> The other four patches add the necessary code for CSI and SMFC handling,
> which is used by the V4L2 CSI capture driver.
> 
> Currently this is based on Russell's patch
>     [PATCH 62/64] imx-drm: pass an IPU ID to crtc and core
> 
> I am aware that there are now quite a few other patches in the pipeline
> that touch drivers/staging/imx-drm/ipu-v3/*, so I am happy to rebase this
> (or them) as needed. I'd like to move the core code out of staging so that
> we can start submitting V4L2 code for video capture and scaling / colorspace
> conversion in parallel.

I'd recommend doing the move (if the gpu/drm maintainer agrees) after
3.14-rc1 as then all of my pending patches would be applied and we would
be synced up with everything.

Once this "core" is moved, what is keeping the rest in staging and why
isn't it moving out as well?

thanks,

greg k-h

  reply	other threads:[~2013-12-20 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 17:52 [RFC PATCH 0/5] Move IPUv3 core out of staging, add CSI support Philipp Zabel
2013-12-20 19:12 ` Greg Kroah-Hartman [this message]
2014-01-03 16:59 ` Philipp Zabel
2014-02-26  8:39 ` Dan Carpenter
2014-02-26 10:08 ` Russell King - ARM Linux

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=20131220191229.GA27254@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-fbdev@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 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).