Re: [RFC PATCH 01/13] misc: atmel_ssc: add device tree DMA support

2013-07-04 Thread Bo Shen
t to test this issue? Ok, I nailed it ! To be sure we are on the same base, here is what I have done: onto next-20130704: - your 5 patches: ASoC: atmel_ssc_dai: move set dma data to startup callback ASoC: atmel_ssc_dai: add error mask define ASoC: atmel-pcm-dma: move prepare for dma to dai pr

Re: Appended DTB files for multi-machine kernels

2013-07-04 Thread Daniel Mack
Hi Arnd, On 04.07.2013 23:34, Arnd Bergmann wrote: > On Thursday 04 July 2013, Mark Brown wrote: >> Another way of skinning this would be for either the kernel to contain >> a set of machine ID to compatible string mappings or for the device >> trees for the boards to have an additional propertie

[GIT PULL] devicetree for v3.11

2013-07-04 Thread Grant Likely
Hi Linus, Please pull the following branch. Description in the signed tag. g. The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10: Linux 3.10-rc5 (2013-06-08 17:41:04 -0700) are available in the git repository at: git://git.secretlab.ca/git/linux tags/devicetree-fo

Re: [PATCH] of: Fix address decoding on Bimini and js2x machines

2013-07-04 Thread Benjamin Herrenschmidt
On Thu, 2013-07-04 at 17:18 +0100, Grant Likely wrote: > > I'll include this in my 3.11 pull request for Linus > > Oops. Ben, I misread what you wrote. It would have been just fine to > include it in your powerpc -next branch. Sorry for the confusion. > > Anyway, I saw your powerpc pull req and t

Re: Appended DTB files for multi-machine kernels

2013-07-04 Thread Arnd Bergmann
On Thursday 04 July 2013, Mark Brown wrote: > On Thu, Jul 04, 2013 at 06:56:24PM +0200, Daniel Mack wrote: > > > Unless I missed some recent discussion, this case is not easy to handle. > > Yes, I know that these kind of things should be handled by a > > next-generation bootloader, but in our case

Re: [PATCH v2 0/3] extend stmmac DT support

2013-07-04 Thread David Miller
From: Srinivas KANDAGATLA Date: Thu, 4 Jul 2013 10:34:56 +0100 > Thankyou for the comments on v1 patches. > > This patch series adds support to new gmac versions 3.6.10 and 3.710, these > versions of IP are integrated into ST STiH415/STiH416 SOCs. > This patchset also adds phy reset capablity t

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Dave Airlie
> ... >>> Sorry but I'd like to say that this cannot be used commonly. Shouldn't you >>> really consider Linux framebuffer or other subsystems? The above dtsi file >>> is specific to DRM subsystem. And I think the dtsi file has no any >>> dependency on certain subsystem so board dtsi f

Re: Appended DTB files for multi-machine kernels

2013-07-04 Thread Nicolas Pitre
On Thu, 4 Jul 2013, Daniel Mack wrote: > Hi Nicolas, > > On 04.07.2013 19:28, Nicolas Pitre wrote: > > On Thu, 4 Jul 2013, Daniel Mack wrote: > >> I'm open to opinion and sugesstions :) > > > > What you describe above more or less fits the definition of what I > > called the "impedance matcher"

Re: Appended DTB files for multi-machine kernels

2013-07-04 Thread Daniel Mack
Hi Nicolas, On 04.07.2013 19:28, Nicolas Pitre wrote: > On Thu, 4 Jul 2013, Daniel Mack wrote: >> I'm open to opinion and sugesstions :) > > What you describe above more or less fits the definition of what I > called the "impedance matcher". However it doesn't need to be part of > the kernel a

Re: Appended DTB files for multi-machine kernels

2013-07-04 Thread Nicolas Pitre
On Thu, 4 Jul 2013, Daniel Mack wrote: > Hi, > > I'm facing a problem with a transition from legacy board-file driven ARM > machines to DTB, and I'm under the impression that a solution for it > could be of broader interest. > > In short, devices that have been deployed in quantities come in thr

[PATCH] gpio-rcar: Add interrupt controller support to the DT bindings

2013-07-04 Thread Laurent Pinchart
Update the DT bindings documentation with the interrupt-controller and #interrupt-cells properties. Signed-off-by: Laurent Pinchart --- Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt | 8 1 file changed, 8 insertions(+) diff --git a/Documentation/devicetree/bindings/gpio/

Re: Appended DTB files for multi-machine kernels

2013-07-04 Thread Mark Brown
On Thu, Jul 04, 2013 at 06:56:24PM +0200, Daniel Mack wrote: > Unless I missed some recent discussion, this case is not easy to handle. > Yes, I know that these kind of things should be handled by a > next-generation bootloader, but in our case, we want to avoid a loader > update of already shippe

Re: [PATCH v4 0/4] mtd:nand:omap2: clean-up of supported ECC schemes

2013-07-04 Thread Mugunthan V N
On 7/3/2013 11:34 PM, Gupta, Pekon wrote: On Wednesday 03 July 2013, Artem Bityutskiy wrote: On Wed, 2013-07-03 at 13:16 +, Gupta, Pekon wrote: [Pekon]: Yes, I'm not seeing these build issues, as I'm cleanly returning from probe with pr_err(), if the required libraries (/lib/bch.c) are not

Appended DTB files for multi-machine kernels

2013-07-04 Thread Daniel Mack
Hi, I'm facing a problem with a transition from legacy board-file driven ARM machines to DTB, and I'm under the impression that a solution for it could be of broader interest. In short, devices that have been deployed in quantities come in three hardware variants, which all boot with a unique mac

Re: [PATCH] of: Fix address decoding on Bimini and js2x machines

2013-07-04 Thread Grant Likely
On Wed, 3 Jul 2013 15:37:56 +0100, Grant Likely wrote: > On Wed, Jul 3, 2013 at 3:10 PM, Rob Herring wrote: > > On 07/03/2013 01:01 AM, Benjamin Herrenschmidt wrote: > >> Commit: > >> > >> e38c0a1fbc5803cbacdaac0557c70ac8ca5152e7 > >> of/address: Handle #address-cells > 2 specially > >> > >>

Re: [PATCH v2 1/6] misc: sram: fix error path in sram_probe

2013-07-04 Thread Philipp Zabel
Hi Heiko, Am Donnerstag, den 04.07.2013, 16:34 +0200 schrieb Heiko Stübner: > Hi Philipp, > > Am Dienstag, 25. Juni 2013, 11:04:34 schrieb Philipp Zabel: > > Hi Heiko, > > > > Am Dienstag, den 25.06.2013, 10:46 +0200 schrieb Heiko Stübner: > > > The pool is created thru devm_gen_pool_create, so

Re: [RFC PATCH V2 1/8] regulator: Introduce OMAP regulator to control PMIC over VC/VP

2013-07-04 Thread Mark Brown
On Fri, Jun 21, 2013 at 04:25:42PM -0500, Nishanth Menon wrote: > +static const struct omap_pmic_info omap_twl4030_vdd1 = { > + .slave_addr = 0x12, > + .voltage_reg_addr = 0x00, > + .cmd_reg_addr = 0x00, > + .i2c_timeout_us = 200, > + .slew_rate_uV = 4000, > + .step_size_uV

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Rob Clark
On Wed, Jul 3, 2013 at 5:02 AM, Sascha Hauer wrote: > On Wed, Jul 03, 2013 at 05:57:18PM +0900, Inki Dae wrote: >> > video { >> > /* Single video card w/ multiple lcd controllers */ >> > card0 { >> > compatible = "marvell,armada-510-display"; >> > reg = <0 0x3f0

[PATCH v3 2/4] ARM: mach-moxart: add MOXA ART device tree files

2013-07-04 Thread Jonas Jensen
Add generic SoC include and UC-7112-LX platform device tree files and documentation. Signed-off-by: Jonas Jensen --- Notes: Applies to next-20130703 Changes since v2: 1. add and update documentation, new drivers: mmc, mac, rtc, watchdog, gpio, core-clock, apb-clock

[PATCH v3 4/4] ARM: reinsert ARCH_MULTI_V4 Kconfig option

2013-07-04 Thread Jonas Jensen
CPU_FA526 is thumbless and adding under e.g. ARCH_MULTI_V4T instead means inclusion of CPU_ARM920T which in turn selects CPU_ABRT_EV4T, CPU_CACHE_V4WT, CPU_COPY_V4WB, CPU_TLB_V4WBI, which in turn can mean trouble when the kernel eventually tries to exec init: [2.58] Kernel panic - not sy

[PATCH v3 3/4] ARM: mach-moxart: add MOXA ART UART debug files

2013-07-04 Thread Jonas Jensen
Add MOXA ART kernel low-level debugging port support. Signed-off-by: Jonas Jensen --- Notes: Applies to next-20130703 Changes since v2: 1. use alphabetic ordering in Kconfig arch/arm/Kconfig.debug | 8 arch/arm/include/debug/moxart.S | 20 ++

[PATCH v3 1/4] ARM: mach-moxart: add MOXA ART SoC files

2013-07-04 Thread Jonas Jensen
Add MOXA ART SoC support. The MOXA ART SoC is based on a Faraday FA526 ARMv4 32-bit 192 MHz CPU with MMU and 16KB/8KB D/I-cache (UC-7112-LX). Signed-off-by: Jonas Jensen --- Notes: Applies to next-20130703 Changes since v2: 1. add CLKSRC_MMIO and GENERIC_CLOCKEVENTS to ARC

Re: [PATCH v2 1/6] misc: sram: fix error path in sram_probe

2013-07-04 Thread Heiko Stübner
Hi Philipp, Am Dienstag, 25. Juni 2013, 11:04:34 schrieb Philipp Zabel: > Hi Heiko, > > Am Dienstag, den 25.06.2013, 10:46 +0200 schrieb Heiko Stübner: > > The pool is created thru devm_gen_pool_create, so the call to > > gen_pool_destroy is not necessary. > > Instead the sram-clock must be turne

Re: [PATCH v3 2/8] wlcore: set irq_flags in the board files instead of hiding behind a quirk

2013-07-04 Thread Luciano Coelho
On Wed, 2013-07-03 at 17:12 +0200, Javier Martinez Canillas wrote: > On Wed, Jul 3, 2013 at 4:15 PM, Luciano Coelho wrote: > > On Wed, 2013-07-03 at 17:03 +0300, Luciano Coelho wrote: > >> The platform_quirk element in the platform data was used to change the > >> way the IRQ is triggered. When s

[PATCH] ARM: u300: fix return value check in __u300_init_boardpower()

2013-07-04 Thread Wei Yongjun
From: Wei Yongjun In case of error, the function syscon_node_to_regmap() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Signed-off-by: Wei Yongjun --- arch/arm/mach-u300/regulator.c | 4 ++-- 1 file changed, 2 insertions(+),

Re: [RFC PATCH 01/13] misc: atmel_ssc: add device tree DMA support

2013-07-04 Thread Richard Genoud
e codec to the SSC and then is >> handled by the DMA. >> there must be something nasty on the DMA bus to hang everything like >> that... > > > Will you try i2c without DMA support to test this issue? Ok, I nailed it ! To be sure we are on the same base, here is what I h

Re: [PATCH v2 1/2] ARM: configs: Enable TI_EDMA in omap2plus_defconfig

2013-07-04 Thread Tony Lindgren
* Joel Fernandes [130626 20:48]: > Build EDMA in by default to avoid fewer people stepping on their toes > with broken DMA on drivers needing EDMA. Thanks applying this one into omap-for-v3.11/fixes. Tony ___ devicetree-discuss mailing list devicetree-

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sebastian Hesselbarth
On 07/04/13 12:09, Sascha Hauer wrote: On Thu, Jul 04, 2013 at 11:44:41AM +0200, Sebastian Hesselbarth wrote: On 07/04/13 11:30, Sascha Hauer wrote: On Thu, Jul 04, 2013 at 10:11:31AM +0100, Russell King wrote: On Thu, Jul 04, 2013 at 10:58:17AM +0200, Sascha Hauer wrote: On Thu, Jul 04, 2013

Re: [PATCH v9 0/8] Generic PHY Framework

2013-07-04 Thread Felipe Balbi
On Thu, Jul 04, 2013 at 03:25:32PM +0530, Kishon Vijay Abraham I wrote: > On Thursday 04 July 2013 02:51 PM, Patel, Satish wrote: > >Hi, > > > >>-Original Message- > >>From: Balbi, Felipe > >>Sent: Wednesday, July 03, 2013 6:51 PM > >>To: ABRAHAM, KISHON VIJAY > >>Cc: Patel, Satish; grant.l

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sascha Hauer
On Thu, Jul 04, 2013 at 11:44:41AM +0200, Sebastian Hesselbarth wrote: > On 07/04/13 11:30, Sascha Hauer wrote: > >On Thu, Jul 04, 2013 at 10:11:31AM +0100, Russell King wrote: > >>On Thu, Jul 04, 2013 at 10:58:17AM +0200, Sascha Hauer wrote: > >>>On Thu, Jul 04, 2013 at 09:40:52AM +0100, Russell K

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sascha Hauer
On Thu, Jul 04, 2013 at 11:40:17AM +0200, Sebastian Hesselbarth wrote: > On 07/04/13 11:23, Sascha Hauer wrote: > > > >With this you can describe the whole graph of devices you have in the > >devicetree. The examples in this file have a path from a camera sensor > >via a MIPI converter to a capture

Re: [PATCH v9 0/8] Generic PHY Framework

2013-07-04 Thread Kishon Vijay Abraham I
On Thursday 04 July 2013 02:51 PM, Patel, Satish wrote: Hi, -Original Message- From: Balbi, Felipe Sent: Wednesday, July 03, 2013 6:51 PM To: ABRAHAM, KISHON VIJAY Cc: Patel, Satish; grant.lik...@linaro.org; t...@atomide.com; Balbi, Felipe; a...@arndb.de; swar...@nvidia.com; sylvester.n

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sascha Hauer
On Thu, Jul 04, 2013 at 10:08:29AM +0100, Russell King wrote: > On Thu, Jul 04, 2013 at 10:33:07AM +0200, Sascha Hauer wrote: > > A componentized device never completes and it doesn't have to. A > > componentized device can start once there is a path from an input > > (crtc, i2s unit) to an output

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sebastian Hesselbarth
On 07/04/13 11:30, Sascha Hauer wrote: On Thu, Jul 04, 2013 at 10:11:31AM +0100, Russell King wrote: On Thu, Jul 04, 2013 at 10:58:17AM +0200, Sascha Hauer wrote: On Thu, Jul 04, 2013 at 09:40:52AM +0100, Russell King wrote: Wrong. Please read the example with the diagrams I gave. Consider w

[PATCH v2 3/3] dt:net:stmmac: Add dt specific phy reset callback support.

2013-07-04 Thread Srinivas KANDAGATLA
From: Srinivas Kandagatla This patch adds phy reset callback support for stmmac driver via device trees. It adds three new properties to gmac device tree bindings to define the reset signal via gpio. With this patch users can conveniently pass reset gpio number with pre, pulse and post delay in

[PATCH v2 0/3] extend stmmac DT support

2013-07-04 Thread Srinivas KANDAGATLA
From: Srinivas Kandagatla Hi Peppe/Dave, Thankyou for the comments on v1 patches. This patch series adds support to new gmac versions 3.6.10 and 3.710, these versions of IP are integrated into ST STiH415/STiH416 SOCs. This patchset also adds phy reset capablity to stmmac-mdio driver via DT. Ch

[PATCH v2 2/3] dt:net:stmmac: Add support to dwmac version 3.610 and 3.710

2013-07-04 Thread Srinivas KANDAGATLA
From: Srinivas Kandagatla This patch adds dt support to dwmac version 3.610 and 3.710 these versions are integrated in STiH415 and STiH416 ARM A9 SOCs. To support these IP version, some of the device tree properties are extended. Signed-off-by: Srinivas Kandagatla --- Documentation/devicetree/

[PATCH v2 1/3] dt:net:stmmac: Allocate platform data only if its NULL.

2013-07-04 Thread Srinivas KANDAGATLA
From: Srinivas Kandagatla In some DT use-cases platform data might be already allocated and passed via AUXDATA. These are the cases where machine level code populates few callbacks in the platform data. This patch adds check and reuses platform_data if its valid, before allocating a new one. Si

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sebastian Hesselbarth
On 07/04/13 11:23, Sascha Hauer wrote: On Thu, Jul 04, 2013 at 11:10:35AM +0200, Sebastian Hesselbarth wrote: On 07/04/13 10:53, Sascha Hauer wrote: On Thu, Jul 04, 2013 at 10:45:40AM +0200, Sebastian Hesselbarth wrote: On 07/04/13 10:33, Sascha Hauer wrote: A componentized device never comp

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sascha Hauer
On Thu, Jul 04, 2013 at 10:11:31AM +0100, Russell King wrote: > On Thu, Jul 04, 2013 at 10:58:17AM +0200, Sascha Hauer wrote: > > On Thu, Jul 04, 2013 at 09:40:52AM +0100, Russell King wrote: > > > Wrong. Please read the example with the diagrams I gave. Consider > > > what happens if you have tw

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sascha Hauer
On Thu, Jul 04, 2013 at 11:10:35AM +0200, Sebastian Hesselbarth wrote: > On 07/04/13 10:53, Sascha Hauer wrote: > >On Thu, Jul 04, 2013 at 10:45:40AM +0200, Sebastian Hesselbarth wrote: > >>On 07/04/13 10:33, Sascha Hauer wrote: > >>> > >>>A componentized device never completes and it doesn't have

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Russell King
On Thu, Jul 04, 2013 at 10:58:17AM +0200, Sascha Hauer wrote: > On Thu, Jul 04, 2013 at 09:40:52AM +0100, Russell King wrote: > > Wrong. Please read the example with the diagrams I gave. Consider > > what happens if you have two display devices connected to a single > > output, one which fixes th

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sebastian Hesselbarth
On 07/04/13 10:53, Sascha Hauer wrote: On Thu, Jul 04, 2013 at 10:45:40AM +0200, Sebastian Hesselbarth wrote: On 07/04/13 10:33, Sascha Hauer wrote: A componentized device never completes and it doesn't have to. A componentized device can start once there is a path from an input (crtc, i2s uni

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Russell King
On Thu, Jul 04, 2013 at 10:33:07AM +0200, Sascha Hauer wrote: > A componentized device never completes and it doesn't have to. A > componentized device can start once there is a path from an input > (crtc, i2s unit) to an output (connector, speaker). Sorry for the incomplete reply. If you read al

Re: [PATCHv3 1/3] iio: Add Nuvoton NAU7802 ADC driver

2013-07-04 Thread Lars-Peter Clausen
On 06/24/2013 07:24 PM, Alexandre Belloni wrote: > The Nuvoton NAU7802 ADC is a 24-bit 2-channels I2C ADC, with adjustable > gain and sampling rates. > > Signed-off-by: Alexandre Belloni > Signed-off-by: Maxime Ripard Reviewed-by: Lars-Peter Clausen One remark though. Multiline comments shoul

Re: [PATCH 1/1] Added Capella CM3218 Ambient Light Sensor IIO Driver.

2013-07-04 Thread Lars-Peter Clausen
On 07/04/2013 01:31 AM, Kevin Tsai wrote: Maybe write at least a short commit message which states the features of the chip. > Signed-off-by: Kevin Tsai > --- > drivers/staging/iio/light/Kconfig | 10 + > drivers/staging/iio/light/Makefile |1 + > drivers/staging/iio/light/cm3218.c | 58

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sascha Hauer
On Thu, Jul 04, 2013 at 09:40:52AM +0100, Russell King wrote: > On Thu, Jul 04, 2013 at 10:33:07AM +0200, Sascha Hauer wrote: > > On Wed, Jul 03, 2013 at 10:52:49AM +0100, Russell King wrote: > > > > > Sorry but I'd like to say that this cannot be used commonly. > > > > > Shouldn't you > > > > > r

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sascha Hauer
On Thu, Jul 04, 2013 at 10:45:40AM +0200, Sebastian Hesselbarth wrote: > On 07/04/13 10:33, Sascha Hauer wrote: > > > >A componentized device never completes and it doesn't have to. A > >componentized device can start once there is a path from an input > >(crtc, i2s unit) to an output (connector, s

Re: [PATCH v1 0/3] extend stmmac DT support.

2013-07-04 Thread Srinivas KANDAGATLA
On 04/07/13 00:04, David Miller wrote: > You are going to have to fix up the following build warnings and resubmit: > > CC [M] drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.o > drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c: In function > ‘stmmac_mdio_reset’: > drivers/net/ethernet/stmic

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sebastian Hesselbarth
On 07/04/13 10:33, Sascha Hauer wrote: On Wed, Jul 03, 2013 at 10:52:49AM +0100, Russell King wrote: Sorry but I'd like to say that this cannot be used commonly. Shouldn't you really consider Linux framebuffer or other subsystems? The above dtsi file is specific to DRM subsystem. And I think the

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Russell King
On Thu, Jul 04, 2013 at 10:33:07AM +0200, Sascha Hauer wrote: > On Wed, Jul 03, 2013 at 10:52:49AM +0100, Russell King wrote: > > > > Sorry but I'd like to say that this cannot be used commonly. Shouldn't > > > > you > > > > really consider Linux framebuffer or other subsystems? The above dtsi >

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sascha Hauer
On Wed, Jul 03, 2013 at 10:52:49AM +0100, Russell King wrote: > > > Sorry but I'd like to say that this cannot be used commonly. Shouldn't you > > > really consider Linux framebuffer or other subsystems? The above dtsi file > > > is specific to DRM subsystem. And I think the dtsi file has no any >

Re: [PATCH dtc] Makefile: provide separate install targets

2013-07-04 Thread David Gibson
On Thu, Jul 04, 2013 at 09:58:23AM +0800, Jeremy Kerr wrote: > Currently `make install` will install the binaries, libraries and > includes. > > This change separates the install target into install-bin, install-lib > and install-includes, so we have more flexibility, particularly when > we're jus

RE: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Inki Dae
> -Original Message- > From: Sebastian Hesselbarth [mailto:sebastian.hesselba...@gmail.com] > Sent: Thursday, July 04, 2013 4:25 PM > To: Inki Dae > Cc: 'Jean-Francois Moine'; 'Daniel Drake'; devicetree- > disc...@lists.ozlabs.org; dri-de...@lists.freedesktop.org; 'Sascha Hauer'; > 'Russe

Re: [RFC PATCH] pwm: atmel-pwm: add pwm controller driver

2013-07-04 Thread Bo Shen
Hi All, On 6/21/2013 16:45, Bo Shen wrote: add atmel pwm controller driver based on PWM framework this is basic function implementation of pwm controller it can work with pwm based led and backlight Signed-off-by: Bo Shen --- .../devicetree/bindings/pwm/atmel-pwm.txt | 19 ++ dr

Re: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Sebastian Hesselbarth
On 07/04/13 09:05, Inki Dae wrote: -Original Message- From: Sebastian Hesselbarth [mailto:sebastian.hesselba...@gmail.com] Sent: Wednesday, July 03, 2013 8:52 PM To: Inki Dae Cc: 'Russell King'; devicetree-discuss@lists.ozlabs.org; 'Jean-Francois Moine'; 'Sascha Hauer'; 'Daniel Drake'; dr

RE: Best practice device tree design for display subsystems/DRM

2013-07-04 Thread Inki Dae
> -Original Message- > From: Sebastian Hesselbarth [mailto:sebastian.hesselba...@gmail.com] > Sent: Wednesday, July 03, 2013 8:52 PM > To: Inki Dae > Cc: 'Russell King'; devicetree-discuss@lists.ozlabs.org; 'Jean-Francois > Moine'; 'Sascha Hauer'; 'Daniel Drake'; dri-de...@lists.freedeskt