From: Tomasz Figa <tomasz.figa@gmail.com>
To: Arun Kumar K <arun.kk@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, 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, joshi@samsung.com
Subject: Re: [PATCH v4] ARM: EXYNOS: Add MFC device tree support
Date: Wed, 26 Sep 2012 08:54:59 +0200 [thread overview]
Message-ID: <1504455.8j02SeYi2o@flatron> (raw)
In-Reply-To: <1348337237-15426-2-git-send-email-arun.kk@samsung.com>
Hi Arun,
A little nitpick inline.
On Saturday 22 of September 2012 23:37:17 Arun Kumar K wrote:
> This patch adds device tree entry for MFC v6 in the Exynos5
> SoC. Makes the required changes in the clock files and adds
> MFC to the DT device list.
>
> Signed-off-by: Naveen Krishna Chatradhi <ch.naveen@samsung.com>
> Signed-off-by: Arun Kumar K <arun.kk@samsung.com>
> ---
> .../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
>
> diff --git a/Documentation/devicetree/bindings/media/s5p-mfc.txt
> b/Documentation/devicetree/bindings/media/s5p-mfc.txt new file mode
> 100644
> index 0000000..f95e775
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/s5p-mfc.txt
> @@ -0,0 +1,27 @@
> +* Samsung Multi Format Codec (MFC)
> +
> +Multi Format Codec (MFC) is the IP present in Samsung SoCs which
> +supports high resolution decoding and encoding functionalities.
> +The MFC device driver is a v4l2 driver which can encode/decode
> +video raw/elementary streams and has support for all popular
> +video codecs.
> +
> +Required properties:
> + - compatible : value should be either one among the following
> + (a) "samsung,mfc-v5" for MFC v5 present in Exynos4 SoCs
> + (b) "samsung,mfc-v6" for MFC v6 present in Exynos5 SoCs
> +
> + - reg : Physical base address of the IP registers and length of memory
> + mapped region.
> +
> + - interrupts : MFC interrupt number to the CPU.
> +
> + - samsung,mfc-r : Base address of the first memory bank used by MFC
> + for DMA contiguous memory allocation.
> +
> + - samsung,mfc-r-size : Size of the first memory bank.
> +
> + - samsung,mfc-l : Base address of the second memory bank used by MFC
> + for DMA contiguous memory allocation.
> +
> + - samsung,mfc-l-size : Size of the second memory bank.
Maybe the base address and size could be merged into one property with two
values, as it is done with the reg property? What do you think?
> diff --git a/arch/arm/boot/dts/exynos5250-smdk5250.dts
> b/arch/arm/boot/dts/exynos5250-smdk5250.dts index 8a5e348..99890ec
> 100644
> --- a/arch/arm/boot/dts/exynos5250-smdk5250.dts
> +++ b/arch/arm/boot/dts/exynos5250-smdk5250.dts
> @@ -109,4 +109,11 @@
> spi_2: spi@12d40000 {
> status = "disabled";
> };
> +
> + codec@11000000 {
> + samsung,mfc-r = <0x43000000>;
> + samsung,mfc-r-size = <8388608>;
> + samsung,mfc-l = <0x51000000>;
> + samsung,mfc-l-size = <8388608>;
It would look like this:
samsung-mfc-r = <0x43000000 0x800000>;
samsung-mfc-l = <0x51000000 0x800000>;
Best regards,
Tomasz Figa
next prev parent reply other threads:[~2012-09-26 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 18:07 [PATCH v4] Add MFC device tree support Arun Kumar K
2012-09-22 18:07 ` [PATCH v4] ARM: EXYNOS: " Arun Kumar K
2012-09-24 8:22 ` Karol Lewandowski
2012-09-26 2:12 ` Kukjin Kim
2012-09-26 6:54 ` Tomasz Figa [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-26 11:00 Arun Kumar K
2012-09-26 12:57 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=1504455.8j02SeYi2o@flatron \
--to=tomasz.figa@gmail.com \
--cc=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).