From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrzej Hajda <a.hajda@samsung.com>
Subject: Re: [RFC v2 PATCH] mipi-dsi-bus: add MIPI DSI bus support
Date: Fri, 13 Dec 2013 12:22:19 +0100
Message-ID: <52AAEDEB.5090102@samsung.com>
References: <20131122174127.GA30591@ulmo.nvidia.com>
	<52936745.1070209@samsung.com> <20131127105401.GB9639@ulmo.nvidia.com>
	<52A08FB3.5040800@ti.com> <20131206125424.GA30625@ulmo.nvidia.com>
	<52A5AAAE.5090601@ti.com> <20131209131015.GB17693@ulmo.nvidia.com>
	<52A5DC30.5030801@ti.com> <20131209161048.GA11742@ulmo.nvidia.com>
	<52A6DCBA.7060801@ti.com> <20131212121941.GF11524@ulmo.nvidia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
Received: from mailout3.w1.samsung.com (mailout3.w1.samsung.com
	[210.118.77.13])
	by gabe.freedesktop.org (Postfix) with ESMTP id 744A8FAEA4
	for <dri-devel@lists.freedesktop.org>;
	Fri, 13 Dec 2013 03:22:29 -0800 (PST)
Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244])
	by mailout3.w1.samsung.com
	(Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit
	(built Nov
	17 2011)) with ESMTP id <0MXQ00366SXE8T80@mailout3.w1.samsung.com> for
	dri-devel@lists.freedesktop.org; Fri, 13 Dec 2013 11:22:26 +0000 (GMT)
In-reply-to: <20131212121941.GF11524@ulmo.nvidia.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: Thierry Reding <thierry.reding@gmail.com>, Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Kyungmin Park <kyungmin.park@samsung.com>, Thierry Reding <treding@nvidia.com>, dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org

On 12/12/2013 01:19 PM, Thierry Reding wrote:
> On Tue, Dec 10, 2013 at 11:19:54AM +0200, Tomi Valkeinen wrote:
>> On 2013-12-09 18:10, Thierry Reding wrote:
>>
>> Btw, about single linux device handling multiple VC IDs: I noticed that
>> the DSI spec has an example, in which a DSI peripheral receives
>> interlaced video, and the video packets containing even field have VC ID
>> 0 and packets for odd field have VC ID 1. I'm not sure how relevant
>> interlaced video is, but I think there's an example where having
>> separate linux devices for each VC ID would be somewhat clumsy.
> Ugh... that's pretty bad.
I wonder if this scenario could not be solved just
by allowing range of VCs per device, for example:
dsi {
        #address-cells = <1>;
        #size-cells = <1>;
        panel_with_interleaved_vc@0 {
             reg = <0, 2>;
        };
};

Regards
Andrzej