[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3o8aoavrv.fsf@t19.piap.pl>
Date: Tue, 27 Jul 2021 12:36:20 +0200
From: Krzysztof Hałasa <khalasa@...p.pl>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: devicetree@...r.kernel.org,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh+dt@...nel.org>, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, Sakari Ailus <sakari.ailus@....fi>
Subject: Re: [RFC v3] dt-binding: media: document ON Semi AR0521 sensor
bindings
Hi Laurent,
Laurent Pinchart <laurent.pinchart@...asonboard.com> writes:
>> + properties:
>> + data-lanes:
>> + anyOf:
>> + - items:
>> + - const: 1
>> + - items:
>> + - const: 1
>> + - const: 2
>> + - items:
>> + - const: 1
>> + - const: 2
>> + - const: 3
>> + - const: 4
>
> As the sensor also supports an HiSPi output, I would add the bus-type
> property:
>
> data-lanes:
> const: 4
Is there any example of this? I'm not sure how should it it look like.
Something like the following?
properties:
data-lanes:
anyOf:
- items:
- const: 1
- items:
- const: 1
- const: 2
- items:
- const: 1
- const: 2
- const: 3
- const: 4
bus-type:
data-lanes:
const: 4
And... HiSPi would need additional code in the driver. And preferably
some testing. I think I'd prefer to have DT and the driver staying in
some sort of sync. Also, I'm uncertain about the syntax and the meaning
of such, apparently redundant, construct. Nor about its relation to
HiSPi. An example would be welcome.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
Powered by blists - more mailing lists