Re: [RFC v2 PATCH] mipi-dsi-bus: add MIPI DSI bus support

[Tomi Valkeinen <tomi.valkeinen@ti.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]

On 2013-12-13 13:22, Andrzej Hajda wrote:
> 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>;
>         };
> };

I don't think range is good, as then you can't have, say, VC IDs 0 and
2. But giving the VC IDs individually as I did in my recent reply,
should do the same thing as above, without ranges.

It's still open to me if that method is good or not.

 Tomi



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel