Am Mittwoch, den 28.05.2014, 14:13 -0700 schrieb Greg Kroah-Hartman: > On Mon, May 26, 2014 at 04:19:39PM +0200, Philipp Zabel wrote: > > The i.MX Image Processing Unit (IPU) contains a number of image processing > > blocks that sit right in the middle between DRM and V4L2. Some of the > > modules, > > such as Display Controller, Processor, and Interface (DC, DP, DI) or CMOS > > Sensor Interface (CSI) and their FIFOs could be assigned to either > > framework, > > but others, such as the dma controller (IDMAC) and image converter (IC) can > > be used by both. > > The IPUv3 core driver provides an internal API to access the modules, to be > > used by both DRM and V4L2 IPUv3 drivers. > > > > Signed-off-by: Lucas Stach <l.st...@pengutronix.de> > > Signed-off-by: Philipp Zabel <p.za...@pengutronix.de> > > --- > > Changes since RFC: > > - Rebased onto current staging-next > > - Removed an unrelated change to ipu_pixelformat_to_colorspace > > - Avoided moving around the IPU_PIX_FMT_GBR24 #define > > Acked-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Thank you. My favourite next step would be to send a pull request and have this merged into drm-next. Dave, Greg would you be ok with this? regards Philipp _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
