Hi Inki Dae, Thanks for the review.
On Mon, Aug 19, 2013 at 5:56 PM, Inki Dae <inki....@samsung.com> wrote: > > >> -----Original Message----- >> From: linux-media-ow...@vger.kernel.org [mailto:linux-media- >> ow...@vger.kernel.org] On Behalf Of Shaik Ameer Basha >> Sent: Monday, August 19, 2013 7:59 PM >> To: linux-media@vger.kernel.org; linux-samsung-...@vger.kernel.org >> Cc: s.nawro...@samsung.com; posc...@google.com; arun...@samsung.com; >> shaik.am...@samsung.com >> Subject: [PATCH v2 0/5] Exynos5 M-Scaler Driver >> >> This patch adds support for M-Scaler (M2M Scaler) device which is a >> new device for scaling, blending, color fill and color space >> conversion on EXYNOS5 SoCs. > > All Exynos5 SoCs really have this IP? It seems that only Exynos5420 and > maybe Exynos5410 have this IP, NOT Exynos5250. Please check it again and > describe it surely over the all patch series. > > Thanks, > Inki Dae True, not all exynos5 series SoCs has this IP. Will change the description and the binding accordingly. Regards, Shaik Ameer Basha > >> >> This device supports the following as key features. >> input image format >> - YCbCr420 2P(UV/VU), 3P >> - YCbCr422 1P(YUYV/UYVY/YVYU), 2P(UV,VU), 3P >> - YCbCr444 2P(UV,VU), 3P >> - RGB565, ARGB1555, ARGB4444, ARGB8888, RGBA8888 >> - Pre-multiplexed ARGB8888, L8A8 and L8 >> output image format >> - YCbCr420 2P(UV/VU), 3P >> - YCbCr422 1P(YUYV/UYVY/YVYU), 2P(UV,VU), 3P >> - YCbCr444 2P(UV,VU), 3P >> - RGB565, ARGB1555, ARGB4444, ARGB8888, RGBA8888 >> - Pre-multiplexed ARGB8888 >> input rotation >> - 0/90/180/270 degree, X/Y/XY Flip >> scale ratio >> - 1/4 scale down to 16 scale up >> color space conversion >> - RGB to YUV / YUV to RGB >> Size >> - Input : 16x16 to 8192x8192 >> - Output: 4x4 to 8192x8192 >> alpha blending, color fill >> >> Rebased on: >> ----------- >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git:master >> >> Changes from v1: >> --------------- >> 1] Split the previous single patch into multiple patches. >> 2] Added DT binding documentation. >> 3] Removed the unnecessary header file inclusions. >> 4] Fix the condition check in mscl_prepare_address for swapping cb/cr >> addresses. >> >> Shaik Ameer Basha (5): >> [media] exynos-mscl: Add new driver for M-Scaler >> [media] exynos-mscl: Add core functionality for the M-Scaler driver >> [media] exynos-mscl: Add m2m functionality for the M-Scaler driver >> [media] exynos-mscl: Add DT bindings for M-Scaler driver >> [media] exynos-mscl: Add Makefile for M-Scaler driver >> >> .../devicetree/bindings/media/exynos5-mscl.txt | 34 + >> drivers/media/platform/Kconfig | 8 + >> drivers/media/platform/Makefile | 1 + >> drivers/media/platform/exynos-mscl/Makefile | 3 + >> drivers/media/platform/exynos-mscl/mscl-core.c | 1312 >> ++++++++++++++++++++ >> drivers/media/platform/exynos-mscl/mscl-core.h | 549 ++++++++ >> drivers/media/platform/exynos-mscl/mscl-m2m.c | 763 ++++++++++++ >> drivers/media/platform/exynos-mscl/mscl-regs.c | 318 +++++ >> drivers/media/platform/exynos-mscl/mscl-regs.h | 282 +++++ >> 9 files changed, 3270 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/media/exynos5- >> mscl.txt >> create mode 100644 drivers/media/platform/exynos-mscl/Makefile >> create mode 100644 drivers/media/platform/exynos-mscl/mscl-core.c >> create mode 100644 drivers/media/platform/exynos-mscl/mscl-core.h >> create mode 100644 drivers/media/platform/exynos-mscl/mscl-m2m.c >> create mode 100644 drivers/media/platform/exynos-mscl/mscl-regs.c >> create mode 100644 drivers/media/platform/exynos-mscl/mscl-regs.h >> >> -- >> 1.7.9.5 >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-media" in >> the body of a message to majord...@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
