From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH, RFC] i.MX DRM support
Date: Fri, 6 Jul 2012 15:58:33 -0700 [thread overview]
Message-ID: <20120706225833.GA22265@kroah.com> (raw)
In-Reply-To: <20120702100506.GI24458@pengutronix.de>
On Mon, Jul 02, 2012 at 12:05:06PM +0200, Sascha Hauer wrote:
> On Thu, Jun 14, 2012 at 03:43:22PM +0200, Sascha Hauer wrote:
> > Hi All,
> >
> > The following is the state-of-the-art i.MX IPU (Image Processing Unit)
> > DRM support.
> >
> > This code is around for quite some time now and has been posted several
> > times with different APIs, first with plain old framebuffer support, now
> > DRM, first platform device binding, now devicetree. Unfortunately there's
> > quite much code needed to get something useful out of the IPU, so these
> > patches haven't received a lot of attention from people not involved in
> > i.MX. I think we have now come to a point where this code needs more public
> > exposure and where it's easier to talk in incremental changes instead of
> > blobs. Therefore I request this to go to staging for some cycles.
>
> Dave, Greg,
>
> Comments to this one? I addressed the comments I received so far and am
> about to respin this series. Is it ok to put this to staging? If yes,
> should I move the whole stuff into drivers/staging/ or should it stay
> in drivers/gpu/drm with just a Kconfig dependency on STAGING?
That's up to the DRM subsystem maintainer to choose.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: David Jander <david.jander@protonic.nl>,
Dave Airlie <airlied@linux.ie>, Matt Sealey <matt@genesi-usa.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
Ahmed Ammar <aammar@genesi-usa.com>
Subject: Re: [PATCH, RFC] i.MX DRM support
Date: Fri, 6 Jul 2012 15:58:33 -0700 [thread overview]
Message-ID: <20120706225833.GA22265@kroah.com> (raw)
In-Reply-To: <20120702100506.GI24458@pengutronix.de>
On Mon, Jul 02, 2012 at 12:05:06PM +0200, Sascha Hauer wrote:
> On Thu, Jun 14, 2012 at 03:43:22PM +0200, Sascha Hauer wrote:
> > Hi All,
> >
> > The following is the state-of-the-art i.MX IPU (Image Processing Unit)
> > DRM support.
> >
> > This code is around for quite some time now and has been posted several
> > times with different APIs, first with plain old framebuffer support, now
> > DRM, first platform device binding, now devicetree. Unfortunately there's
> > quite much code needed to get something useful out of the IPU, so these
> > patches haven't received a lot of attention from people not involved in
> > i.MX. I think we have now come to a point where this code needs more public
> > exposure and where it's easier to talk in incremental changes instead of
> > blobs. Therefore I request this to go to staging for some cycles.
>
> Dave, Greg,
>
> Comments to this one? I addressed the comments I received so far and am
> about to respin this series. Is it ok to put this to staging? If yes,
> should I move the whole stuff into drivers/staging/ or should it stay
> in drivers/gpu/drm with just a Kconfig dependency on STAGING?
That's up to the DRM subsystem maintainer to choose.
greg k-h
next prev parent reply other threads:[~2012-07-06 22:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 13:43 [PATCH, RFC] i.MX DRM support Sascha Hauer
2012-06-14 13:43 ` Sascha Hauer
2012-06-14 13:43 ` [PATCH 1/5] DRM: Add i.MX drm core support Sascha Hauer
2012-06-14 13:43 ` Sascha Hauer
2012-06-21 5:30 ` Shawn Guo
2012-06-21 5:30 ` Shawn Guo
2012-06-21 6:52 ` Sascha Hauer
2012-06-21 6:52 ` Sascha Hauer
2012-06-14 13:43 ` [PATCH 2/5] DRM i.MX: Add parallel display support Sascha Hauer
2012-06-14 13:43 ` Sascha Hauer
2012-06-21 5:35 ` Shawn Guo
2012-06-21 5:35 ` Shawn Guo
2012-06-21 6:07 ` Shawn Guo
2012-06-21 6:07 ` Shawn Guo
2012-06-21 7:06 ` Sascha Hauer
2012-06-21 7:06 ` Sascha Hauer
2012-06-22 5:29 ` Shawn Guo
2012-06-22 5:29 ` Shawn Guo
2012-06-14 13:43 ` [PATCH 3/5] DRM i.MX: Add LCDC support Sascha Hauer
2012-06-14 13:43 ` Sascha Hauer
2012-06-21 6:12 ` Shawn Guo
2012-06-21 6:12 ` Shawn Guo
2012-06-21 7:10 ` Sascha Hauer
2012-06-21 7:10 ` Sascha Hauer
2012-06-14 13:43 ` [PATCH 4/5] DRM: add i.MX IPUv3 base driver Sascha Hauer
2012-06-14 13:43 ` Sascha Hauer
2012-06-22 6:04 ` Shawn Guo
2012-06-22 6:04 ` Shawn Guo
2012-06-14 13:43 ` [PATCH 5/5] DRM: Add i.MX IPUv3 crtc support Sascha Hauer
2012-06-14 13:43 ` Sascha Hauer
2012-06-19 18:20 ` [PATCH, RFC] i.MX DRM support Fabio Estevam
2012-06-19 18:20 ` Fabio Estevam
2012-07-02 10:05 ` Sascha Hauer
2012-07-02 10:05 ` Sascha Hauer
2012-07-02 11:12 ` Dirk Behme
2012-07-02 11:12 ` Dirk Behme
2012-07-06 22:58 ` Greg Kroah-Hartman [this message]
2012-07-06 22:58 ` Greg Kroah-Hartman
2012-07-08 7:35 ` Dave Airlie
2012-07-08 7:35 ` Dave Airlie
2012-07-09 8:42 ` Sascha Hauer
2012-07-09 8:42 ` Sascha Hauer
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=20120706225833.GA22265@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.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.