| Message ID | 1464096690-23605-7-git-send-email-m.szyprowski@samsung.com (mailing list archive) |
|---|---|
| State | Accepted |
| Headers | show |
On 05/24/2016 03:31 PM, Marek Szyprowski wrote: > This patch replaces custom properties for defining reserved memory > regions with generic reserved memory bindings for MFC video codec > device. > > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> > --- > arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi | 27 ++++++++++++++++++++++ > arch/arm/boot/dts/exynos4210-origen.dts | 4 ++-- > arch/arm/boot/dts/exynos4210-smdkv310.dts | 4 ++-- > arch/arm/boot/dts/exynos4412-origen.dts | 4 ++-- > arch/arm/boot/dts/exynos4412-smdk4412.dts | 4 ++-- > arch/arm/boot/dts/exynos5250-arndale.dts | 4 ++-- > arch/arm/boot/dts/exynos5250-smdk5250.dts | 4 ++-- > arch/arm/boot/dts/exynos5250-spring.dts | 4 ++-- > arch/arm/boot/dts/exynos5420-arndale-octa.dts | 4 ++-- > arch/arm/boot/dts/exynos5420-peach-pit.dts | 4 ++-- > arch/arm/boot/dts/exynos5420-smdk5420.dts | 4 ++-- > arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi | 4 ++-- > arch/arm/boot/dts/exynos5800-peach-pi.dts | 4 ++-- > 13 files changed, 51 insertions(+), 24 deletions(-) > create mode 100644 arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi > > diff --git a/arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi b/arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi > new file mode 100644 > index 0000000..e7445c9 > --- /dev/null > +++ b/arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi > @@ -0,0 +1,27 @@ > +/* > + * Samsung's Exynos SoC MFC (Video Codec) reserved memory common definition. Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com> One nit - our copyright would be welcomed: Copyright (c) 2016 Samsung Electronics Co., Ltd However if there are no objections I will add it when applying. Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hello Marek, On 05/24/2016 09:31 AM, Marek Szyprowski wrote: > This patch replaces custom properties for defining reserved memory > regions with generic reserved memory bindings for MFC video codec > device. > > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> > --- [snip] > + > +/ { > + reserved-memory { > + #address-cells = <1>; > + #size-cells = <1>; > + ranges; > + > + mfc_left: region@51000000 { > + compatible = "shared-dma-pool"; > + no-map; > + reg = <0x51000000 0x800000>; > + }; > + > + mfc_right: region@43000000 { > + compatible = "shared-dma-pool"; > + no-map; > + reg = <0x43000000 0x800000>; > + }; > + }; I've a question probably for a follow up patch, but do you know what's a sane default size for these? I needed to bump the mfc_left size from 8 MiB to 16 MiB in order to decode a 480p H264 video using GStramer. So clearly the default sizes are not that useful. > +}; > diff --git a/arch/arm/boot/dts/exynos4210-origen.dts b/arch/arm/boot/dts/exynos4210-origen.dts > index ad7394c..f5e4eb2 100644 > --- a/arch/arm/boot/dts/exynos4210-origen.dts > +++ b/arch/arm/boot/dts/exynos4210-origen.dts > @@ -18,6 +18,7 @@ > #include "exynos4210.dtsi" > #include <dt-bindings/gpio/gpio.h> > #include <dt-bindings/input/input.h> > +#include "exynos-mfc-reserved-memory.dtsi" > > / { > model = "Insignal Origen evaluation board based on Exynos4210"; > @@ -288,8 +289,7 @@ > }; > > &mfc { > - samsung,mfc-r = <0x43000000 0x800000>; > - samsung,mfc-l = <0x51000000 0x800000>; > + memory-region = <&mfc_left>, <&mfc_right>; > status = "okay"; I wonder if shouldn't be better to include the exynos-mfc-reserved-memory.dtsi on each SoC dtsi and set the memory-regions in the MFC node instead of doing it on each DTS, and let DTS to just replace with its own memory regions if the default sizes are not suitable for them. Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com> Tested-by: Javier Martinez Canillas <javier@osg.samsung.com> Best regards,
Hello, On 2016-05-25 19:11, Javier Martinez Canillas wrote: > Hello Marek, > > On 05/24/2016 09:31 AM, Marek Szyprowski wrote: >> This patch replaces custom properties for defining reserved memory >> regions with generic reserved memory bindings for MFC video codec >> device. >> >> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> >> --- > [snip] > >> + >> +/ { >> + reserved-memory { >> + #address-cells = <1>; >> + #size-cells = <1>; >> + ranges; >> + >> + mfc_left: region@51000000 { >> + compatible = "shared-dma-pool"; >> + no-map; >> + reg = <0x51000000 0x800000>; >> + }; >> + >> + mfc_right: region@43000000 { >> + compatible = "shared-dma-pool"; >> + no-map; >> + reg = <0x43000000 0x800000>; >> + }; >> + }; > I've a question probably for a follow up patch, but do you know what's a > sane default size for these? I needed to bump the mfc_left size from 8 MiB > to 16 MiB in order to decode a 480p H264 video using GStramer. So clearly > the default sizes are not that useful. Right, the default size for the 'left' region can be increased. Frankly, those values (8MiB/0x43000000+ 8MiB/0x51000000) comes from my initial patches prepared for some demo and don't have much with any real requirements. They were copied (blindly...) by various developers without any deeper understanding. Probably the most sane would be to use something like this: mfc_left: region_mfc_left { compatible = "shared-dma-pool"; no-map; size = <0x1000000>; alignment = <0x100000>; }; mfc_right: region_mfc_right { compatible = "shared-dma-pool"; no-map; size = <0x800000>; alignment = <0x100000>; }; So the region will be allocated automatically from the available memory. This way another nice feature of the generic reserved memory regions can be used. The only platform which really requires MFC regions to be placed at certain memory offsets is Samsung S5PV210/S5PC110 (sometimes called exynos3), where there is no memory address interleaving and MFC device has limited memory interface, which cannot do 2 transactions to the same physical memory bank. However S5PV210/S5PC110 machine code lost support for MFC during conversion to device tree, so it is not a problem here. All newer platforms (Exynos4, Exynos3250, Exynos5+) use memory interleaving, so the actual offset of memory bank has no influence on the physical memory bank. >> +}; >> diff --git a/arch/arm/boot/dts/exynos4210-origen.dts b/arch/arm/boot/dts/exynos4210-origen.dts >> index ad7394c..f5e4eb2 100644 >> --- a/arch/arm/boot/dts/exynos4210-origen.dts >> +++ b/arch/arm/boot/dts/exynos4210-origen.dts >> @@ -18,6 +18,7 @@ >> #include "exynos4210.dtsi" >> #include <dt-bindings/gpio/gpio.h> >> #include <dt-bindings/input/input.h> >> +#include "exynos-mfc-reserved-memory.dtsi" >> >> / { >> model = "Insignal Origen evaluation board based on Exynos4210"; >> @@ -288,8 +289,7 @@ >> }; >> >> &mfc { >> - samsung,mfc-r = <0x43000000 0x800000>; >> - samsung,mfc-l = <0x51000000 0x800000>; >> + memory-region = <&mfc_left>, <&mfc_right>; >> status = "okay"; > I wonder if shouldn't be better to include the exynos-mfc-reserved-memory.dtsi > on each SoC dtsi and set the memory-regions in the MFC node instead of doing > it on each DTS, and let DTS to just replace with its own memory regions if the > default sizes are not suitable for them. I don't have strong opinion on this. Maybe it would make more sense to move the following entry: &mfc { memory-region = <&mfc_left>, <&mfc_right>; }; also to the exynos-mfc-reserved-memory.dtsi ? So board will just include it if it want to use MFC device with reserved memory regions. > Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com> > Tested-by: Javier Martinez Canillas <javier@osg.samsung.com> Best regards
Hello Marek, On 05/27/2016 07:32 AM, Marek Szyprowski wrote: > Hello, > > > On 2016-05-25 19:11, Javier Martinez Canillas wrote: >> Hello Marek, >> >> On 05/24/2016 09:31 AM, Marek Szyprowski wrote: >>> This patch replaces custom properties for defining reserved memory >>> regions with generic reserved memory bindings for MFC video codec >>> device. >>> >>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> >>> --- >> [snip] >> >>> + >>> +/ { >>> + reserved-memory { >>> + #address-cells = <1>; >>> + #size-cells = <1>; >>> + ranges; >>> + >>> + mfc_left: region@51000000 { >>> + compatible = "shared-dma-pool"; >>> + no-map; >>> + reg = <0x51000000 0x800000>; >>> + }; >>> + >>> + mfc_right: region@43000000 { >>> + compatible = "shared-dma-pool"; >>> + no-map; >>> + reg = <0x43000000 0x800000>; >>> + }; >>> + }; >> I've a question probably for a follow up patch, but do you know what's a >> sane default size for these? I needed to bump the mfc_left size from 8 MiB >> to 16 MiB in order to decode a 480p H264 video using GStramer. So clearly >> the default sizes are not that useful. > > Right, the default size for the 'left' region can be increased. Frankly, those > values (8MiB/0x43000000+ 8MiB/0x51000000) comes from my initial patches > prepared for some demo and don't have much with any real requirements. They > were copied (blindly...) by various developers without any deeper understanding. Yes, I've to admit that I was one of those when added the MFC regions to the Peach Chromebooks but worked because I tested with small videos. When trying to decode bigger videos, then had to increase the 'left' region as mentioned. > Probably the most sane would be to use something like this: > > mfc_left: region_mfc_left { > compatible = "shared-dma-pool"; > no-map; > size = <0x1000000>; > alignment = <0x100000>; > }; > > mfc_right: region_mfc_right { > compatible = "shared-dma-pool"; > no-map; > size = <0x800000>; > alignment = <0x100000>; > }; > > So the region will be allocated automatically from the available memory. This way > another nice feature of the generic reserved memory regions can be used. > That sounds better indeed. Not requiring a certain memory offset will also have the nice side effect to prevent conflicts like the one Pankaj had with his initramfs [0]. > The only platform which really requires MFC regions to be placed at certain memory > offsets is Samsung S5PV210/S5PC110 (sometimes called exynos3), where there is no > memory address interleaving and MFC device has limited memory interface, which cannot > do 2 transactions to the same physical memory bank. However S5PV210/S5PC110 machine > code lost support for MFC during conversion to device tree, so it is not a problem > here. > > All newer platforms (Exynos4, Exynos3250, Exynos5+) use memory interleaving, so the > actual offset of memory bank has no influence on the physical memory bank. > I see, thanks a lot for the explanation. >>> +}; >>> diff --git a/arch/arm/boot/dts/exynos4210-origen.dts b/arch/arm/boot/dts/exynos4210-origen.dts >>> index ad7394c..f5e4eb2 100644 >>> --- a/arch/arm/boot/dts/exynos4210-origen.dts >>> +++ b/arch/arm/boot/dts/exynos4210-origen.dts >>> @@ -18,6 +18,7 @@ >>> #include "exynos4210.dtsi" >>> #include <dt-bindings/gpio/gpio.h> >>> #include <dt-bindings/input/input.h> >>> +#include "exynos-mfc-reserved-memory.dtsi" >>> / { >>> model = "Insignal Origen evaluation board based on Exynos4210"; >>> @@ -288,8 +289,7 @@ >>> }; >>> &mfc { >>> - samsung,mfc-r = <0x43000000 0x800000>; >>> - samsung,mfc-l = <0x51000000 0x800000>; >>> + memory-region = <&mfc_left>, <&mfc_right>; >>> status = "okay"; >> I wonder if shouldn't be better to include the exynos-mfc-reserved-memory.dtsi >> on each SoC dtsi and set the memory-regions in the MFC node instead of doing >> it on each DTS, and let DTS to just replace with its own memory regions if the >> default sizes are not suitable for them. > > I don't have strong opinion on this. Maybe it would make more sense to move the > following entry: > > &mfc { > memory-region = <&mfc_left>, <&mfc_right>; > }; > > also to the exynos-mfc-reserved-memory.dtsi ? So board will just include it if > it want to use MFC device with reserved memory regions. > Ok, that also sounds like a good option for me. >> Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com> >> Tested-by: Javier Martinez Canillas <javier@osg.samsung.com> > > Best regards [0]: https://lkml.org/lkml/2016/5/26/98 Best regards,
diff --git a/arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi b/arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi new file mode 100644 index 0000000..e7445c9 --- /dev/null +++ b/arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi @@ -0,0 +1,27 @@ +/* + * Samsung's Exynos SoC MFC (Video Codec) reserved memory common definition. + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ + +/ { + reserved-memory { + #address-cells = <1>; + #size-cells = <1>; + ranges; + + mfc_left: region@51000000 { + compatible = "shared-dma-pool"; + no-map; + reg = <0x51000000 0x800000>; + }; + + mfc_right: region@43000000 { + compatible = "shared-dma-pool"; + no-map; + reg = <0x43000000 0x800000>; + }; + }; +}; diff --git a/arch/arm/boot/dts/exynos4210-origen.dts b/arch/arm/boot/dts/exynos4210-origen.dts index ad7394c..f5e4eb2 100644 --- a/arch/arm/boot/dts/exynos4210-origen.dts +++ b/arch/arm/boot/dts/exynos4210-origen.dts @@ -18,6 +18,7 @@ #include "exynos4210.dtsi" #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Insignal Origen evaluation board based on Exynos4210"; @@ -288,8 +289,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; status = "okay"; }; diff --git a/arch/arm/boot/dts/exynos4210-smdkv310.dts b/arch/arm/boot/dts/exynos4210-smdkv310.dts index 94ca7d3..de917f0 100644 --- a/arch/arm/boot/dts/exynos4210-smdkv310.dts +++ b/arch/arm/boot/dts/exynos4210-smdkv310.dts @@ -17,6 +17,7 @@ /dts-v1/; #include "exynos4210.dtsi" #include <dt-bindings/gpio/gpio.h> +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Samsung smdkv310 evaluation board based on Exynos4210"; @@ -133,8 +134,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; status = "okay"; }; diff --git a/arch/arm/boot/dts/exynos4412-origen.dts b/arch/arm/boot/dts/exynos4412-origen.dts index 8bca699..cd363d7 100644 --- a/arch/arm/boot/dts/exynos4412-origen.dts +++ b/arch/arm/boot/dts/exynos4412-origen.dts @@ -16,6 +16,7 @@ #include "exynos4412.dtsi" #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Insignal Origen evaluation board based on Exynos4412"; @@ -466,8 +467,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; status = "okay"; }; diff --git a/arch/arm/boot/dts/exynos4412-smdk4412.dts b/arch/arm/boot/dts/exynos4412-smdk4412.dts index a51069f..9b6d561 100644 --- a/arch/arm/boot/dts/exynos4412-smdk4412.dts +++ b/arch/arm/boot/dts/exynos4412-smdk4412.dts @@ -14,6 +14,7 @@ /dts-v1/; #include "exynos4412.dtsi" +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Samsung SMDK evaluation board based on Exynos4412"; @@ -112,8 +113,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; status = "okay"; }; diff --git a/arch/arm/boot/dts/exynos5250-arndale.dts b/arch/arm/boot/dts/exynos5250-arndale.dts index 85dad29..39940f4 100644 --- a/arch/arm/boot/dts/exynos5250-arndale.dts +++ b/arch/arm/boot/dts/exynos5250-arndale.dts @@ -14,6 +14,7 @@ #include <dt-bindings/interrupt-controller/irq.h> #include <dt-bindings/input/input.h> #include "exynos5250.dtsi" +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Insignal Arndale evaluation board based on EXYNOS5250"; @@ -516,8 +517,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; }; &mmc_0 { diff --git a/arch/arm/boot/dts/exynos5250-smdk5250.dts b/arch/arm/boot/dts/exynos5250-smdk5250.dts index b7992b1..9fac874 100644 --- a/arch/arm/boot/dts/exynos5250-smdk5250.dts +++ b/arch/arm/boot/dts/exynos5250-smdk5250.dts @@ -13,6 +13,7 @@ #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/interrupt-controller/irq.h> #include "exynos5250.dtsi" +#include "exynos-mfc-reserved-memory.dtsi" / { model = "SAMSUNG SMDK5250 board based on EXYNOS5250"; @@ -344,8 +345,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; }; &mmc_0 { diff --git a/arch/arm/boot/dts/exynos5250-spring.dts b/arch/arm/boot/dts/exynos5250-spring.dts index ac291f5..784130b 100644 --- a/arch/arm/boot/dts/exynos5250-spring.dts +++ b/arch/arm/boot/dts/exynos5250-spring.dts @@ -14,6 +14,7 @@ #include <dt-bindings/interrupt-controller/irq.h> #include <dt-bindings/input/input.h> #include "exynos5250.dtsi" +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Google Spring"; @@ -425,8 +426,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; }; &mmc_0 { diff --git a/arch/arm/boot/dts/exynos5420-arndale-octa.dts b/arch/arm/boot/dts/exynos5420-arndale-octa.dts index 60bc861..b8b5f3a 100644 --- a/arch/arm/boot/dts/exynos5420-arndale-octa.dts +++ b/arch/arm/boot/dts/exynos5420-arndale-octa.dts @@ -16,6 +16,7 @@ #include <dt-bindings/interrupt-controller/irq.h> #include <dt-bindings/input/input.h> #include <dt-bindings/clock/samsung,s2mps11.h> +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Insignal Arndale Octa evaluation board based on EXYNOS5420"; @@ -347,8 +348,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; }; &mmc_0 { diff --git a/arch/arm/boot/dts/exynos5420-peach-pit.dts b/arch/arm/boot/dts/exynos5420-peach-pit.dts index f9d2e4f..d530b4f 100644 --- a/arch/arm/boot/dts/exynos5420-peach-pit.dts +++ b/arch/arm/boot/dts/exynos5420-peach-pit.dts @@ -16,6 +16,7 @@ #include <dt-bindings/regulator/maxim,max77802.h> #include "exynos5420.dtsi" #include "exynos5420-cpus.dtsi" +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Google Peach Pit Rev 6+"; @@ -695,8 +696,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; }; &mmc_0 { diff --git a/arch/arm/boot/dts/exynos5420-smdk5420.dts b/arch/arm/boot/dts/exynos5420-smdk5420.dts index 2e748d1..5206f41 100644 --- a/arch/arm/boot/dts/exynos5420-smdk5420.dts +++ b/arch/arm/boot/dts/exynos5420-smdk5420.dts @@ -13,6 +13,7 @@ #include "exynos5420.dtsi" #include "exynos5420-cpus.dtsi" #include <dt-bindings/gpio/gpio.h> +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Samsung SMDK5420 board based on EXYNOS5420"; @@ -355,8 +356,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; }; &mmc_0 { diff --git a/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi b/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi index 2a4e10b..7c2335f 100644 --- a/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi +++ b/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi @@ -17,6 +17,7 @@ #include "exynos5800.dtsi" #include "exynos5422-cpus.dtsi" #include "exynos5422-cpu-thermal.dtsi" +#include "exynos-mfc-reserved-memory.dtsi" / { memory { @@ -406,8 +407,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; }; &mmc_0 { diff --git a/arch/arm/boot/dts/exynos5800-peach-pi.dts b/arch/arm/boot/dts/exynos5800-peach-pi.dts index 62ceb89..1f73596 100644 --- a/arch/arm/boot/dts/exynos5800-peach-pi.dts +++ b/arch/arm/boot/dts/exynos5800-peach-pi.dts @@ -16,6 +16,7 @@ #include <dt-bindings/regulator/maxim,max77802.h> #include "exynos5800.dtsi" #include "exynos5420-cpus.dtsi" +#include "exynos-mfc-reserved-memory.dtsi" / { model = "Google Peach Pi Rev 10+"; @@ -670,8 +671,7 @@ }; &mfc { - samsung,mfc-r = <0x43000000 0x800000>; - samsung,mfc-l = <0x51000000 0x800000>; + memory-region = <&mfc_left>, <&mfc_right>; }; &mmc_0 {
This patch replaces custom properties for defining reserved memory regions with generic reserved memory bindings for MFC video codec device. Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> --- arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi | 27 ++++++++++++++++++++++ arch/arm/boot/dts/exynos4210-origen.dts | 4 ++-- arch/arm/boot/dts/exynos4210-smdkv310.dts | 4 ++-- arch/arm/boot/dts/exynos4412-origen.dts | 4 ++-- arch/arm/boot/dts/exynos4412-smdk4412.dts | 4 ++-- arch/arm/boot/dts/exynos5250-arndale.dts | 4 ++-- arch/arm/boot/dts/exynos5250-smdk5250.dts | 4 ++-- arch/arm/boot/dts/exynos5250-spring.dts | 4 ++-- arch/arm/boot/dts/exynos5420-arndale-octa.dts | 4 ++-- arch/arm/boot/dts/exynos5420-peach-pit.dts | 4 ++-- arch/arm/boot/dts/exynos5420-smdk5420.dts | 4 ++-- arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi | 4 ++-- arch/arm/boot/dts/exynos5800-peach-pi.dts | 4 ++-- 13 files changed, 51 insertions(+), 24 deletions(-) create mode 100644 arch/arm/boot/dts/exynos-mfc-reserved-memory.dtsi