From: Arun Kumar K <arun.kk@samsung.com>
To: linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, linux-media@vger.kernel.org
Cc: kgene.kim@samsung.com, k.debski@samsung.com,
jtp.park@samsung.com, ch.naveen@samsung.com, arun.kk@samsung.com,
thomas.abraham@linaro.org, kmpark@infradead.org,
joshi@samsung.com
Subject: [PATCH v1 0/2] Add MFC device tree support
Date: Mon, 03 Sep 2012 22:22:56 +0530 [thread overview]
Message-ID: <1346691178-29580-1-git-send-email-arun.kk@samsung.com> (raw)
This patchset adds device tree support for s5p-mfc driver.
The first patch adds DT support for both Exynos4 and 5 SoCs
which has different versions of MFC. The second patch which
adds DT support for the driver has to be applied over the
patchset [1] which adds the MFCv6 support.
Changelog:
- Moved board specific DT information to different dtsi file
- Changed compatible name for the device
- Addressed other review comments
[1] http://www.mail-archive.com/linux-media@vger.kernel.org/msg51284.html
Arun Kumar K (1):
[media] s5p-mfc: Add device tree support
Naveen Krishna Chatradhi (1):
ARM: EXYNOS: Add MFC device tree support
.../devicetree/bindings/media/s5p-mfc.txt | 27 +++++
arch/arm/boot/dts/exynos4210-origen.dts | 7 ++
arch/arm/boot/dts/exynos4210.dtsi | 6 +
arch/arm/boot/dts/exynos5250-smdk5250.dts | 7 ++
arch/arm/boot/dts/exynos5250.dtsi | 6 +
arch/arm/mach-exynos/Kconfig | 2 +
arch/arm/mach-exynos/clock-exynos5.c | 2 +-
arch/arm/mach-exynos/mach-exynos4-dt.c | 9 ++
arch/arm/mach-exynos/mach-exynos5-dt.c | 9 ++
drivers/media/platform/s5p-mfc/s5p_mfc.c | 104 +++++++++++++++++---
10 files changed, 162 insertions(+), 17 deletions(-)
create mode 100644 Documentation/devicetree/bindings/media/s5p-mfc.txt
next reply other threads:[~2012-09-03 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 16:52 Arun Kumar K [this message]
2012-09-03 16:52 ` [PATCH v1 1/2] ARM: EXYNOS: Add MFC device tree support Arun Kumar K
2012-09-03 16:52 ` [PATCH v1 2/2] [media] s5p-mfc: Add " Arun Kumar K
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=1346691178-29580-1-git-send-email-arun.kk@samsung.com \
--to=arun.kk@samsung.com \
--cc=ch.naveen@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=joshi@samsung.com \
--cc=jtp.park@samsung.com \
--cc=k.debski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=thomas.abraham@linaro.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).