From: Arun Kumar K <arun.kk@samsung.com>
To: linux-samsung-soc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org
Cc: kgene.kim@samsung.com, k.debski@samsung.com,
jtp.park@samsung.com, thomas.abraham@linaro.org,
k.lewandowsk@samsung.com, s.nawrocki@samsung.com,
ch.naveen@samsung.com, arun.kk@samsung.com, joshi@samsung.com
Subject: [PATCH v4] Add MFC device tree support
Date: Sat, 22 Sep 2012 23:37:16 +0530 [thread overview]
Message-ID: <1348337237-15426-1-git-send-email-arun.kk@samsung.com> (raw)
This patch adds the device tree entries for MFC on Exynos5.
This is rebased to the linux-samsung for-next branch.
Changelog v4
- Addressed review comments from Karol Lewandowski
http://permalink.gmane.org/gmane.linux.kernel.samsung-soc/12703
Changelog v3
- Addressed review comments given by Sylwester Nawrocki
http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg12340.html
Changelog v2
- Use fdt functions to parse dtsi file for mfc memory info
Changelog v1
- Moved board specific DT information to different dtsi file
- Changed compatible name for the device
- Addressed other review comments
Arun Kumar K (1):
ARM: EXYNOS: Add MFC device tree support
.../devicetree/bindings/media/s5p-mfc.txt | 27 ++++++++++++++
arch/arm/boot/dts/exynos5250-smdk5250.dts | 7 ++++
arch/arm/boot/dts/exynos5250.dtsi | 6 +++
arch/arm/mach-exynos/Kconfig | 1 +
arch/arm/mach-exynos/clock-exynos5.c | 2 +-
arch/arm/mach-exynos/common.c | 37 ++++++++++++++++++++
arch/arm/mach-exynos/common.h | 10 +++++
arch/arm/mach-exynos/mach-exynos5-dt.c | 16 ++++++++
8 files changed, 105 insertions(+), 1 deletions(-)
create mode 100644 Documentation/devicetree/bindings/media/s5p-mfc.txt
next reply other threads:[~2012-09-22 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 18:07 Arun Kumar K [this message]
2012-09-22 18:07 ` [PATCH v4] ARM: EXYNOS: Add MFC device tree support Arun Kumar K
2012-09-24 8:22 ` Karol Lewandowski
2012-09-26 2:12 ` Kukjin Kim
2012-09-26 6:54 ` Tomasz Figa
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=1348337237-15426-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=k.lewandowsk@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.com \
--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).