linux-kernel - Re: [PATCH v4 06/19] dt-bindings: media: i2c: max96717: add support for MAX96793

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f6847b24-aa57-4ce5-995f-03b3056f88a1@gmail.com>
Date: Tue, 24 Jun 2025 19:20:48 +0300
From: Cosmin Tanislav <demonsingur@...il.com>
To: Martin Hecht <mhecht73@...il.com>,
 Tomi Valkeinen <tomi.valkeinen+renesas@...asonboard.com>,
 Mauro Carvalho Chehab <mchehab@...nel.org>, Rob Herring <robh@...nel.org>,
 Niklas Söderlund <niklas.soderlund@...natech.se>,
 Julien Massot <julien.massot@...labora.com>,
 Sakari Ailus <sakari.ailus@...ux.intel.com>,
 Laurent Pinchart <laurent.pinchart@...asonboard.com>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Linus Walleij <linus.walleij@...aro.org>
Cc: "open list:MAXIM GMSL2 SERIALIZERS AND DESERIALIZERS"
 <linux-media@...r.kernel.org>,
 "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
 <devicetree@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>,
 "moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
 <linux-arm-kernel@...ts.infradead.org>,
 "open list:STAGING SUBSYSTEM" <linux-staging@...ts.linux.dev>,
 open "list:GPIO"
 "SUBSYSTEM:Keyword:(devm_)?gpio_(request|free|direction|get|set)"
 <linux-gpio@...r.kernel.org>, Cosmin Tanislav <cosmin.tanislav@...log.com>
Subject: Re: [PATCH v4 06/19] dt-bindings: media: i2c: max96717: add support
 for MAX96793



On 6/24/25 7:14 PM, Martin Hecht wrote:
> Hi Cosmin,
> 
> I'm preparing a test with Alvium + max96717 + max96716. I can't see away 
> to overwrite cfg settings to force pixel mode or tunnel mode. Any plans 
> to add this? Sometimes it is required to force the other mode than set 
> by pin-strapping.
> 
> BR Martin
> 

Hi Martin.

Pixel/tunnel mode is chosen automatically based on HW capabilities
routing, formats, etc.

I don't plan on adding a way to force it, since the presumption
is that the serdes framework will pick the best use case available, as
long as all the data can make its way to the PHY.

Forcing pixel/tunnel mode shouldn't be done via device-tree since it's
not related to the way hardware is wired up to the rest of the system.

> On 6/18/25 11:58, Cosmin Tanislav wrote:
>> MAX96793 is a newer variant of the MAX96717 which also supports GMSL3
>> links.
>>
>> Document this compatibility.
>>
>> Signed-off-by: Cosmin Tanislav <demonsingur@...il.com>
>> Acked-by: Rob Herring (Arm) <robh@...nel.org>
>> ---
>>   .../devicetree/bindings/media/i2c/maxim,max96717.yaml          | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/media/i2c/ 
>> maxim,max96717.yaml b/Documentation/devicetree/bindings/media/i2c/ 
>> maxim,max96717.yaml
>> index ab46a5f0bd7e..23f611177a87 100644
>> --- a/Documentation/devicetree/bindings/media/i2c/maxim,max96717.yaml
>> +++ b/Documentation/devicetree/bindings/media/i2c/maxim,max96717.yaml
>> @@ -30,6 +30,8 @@ description:
>>     MAX9295A only supports pixel mode.
>> +  MAX96793 also supports GMSL3 mode.
>> +
>>   properties:
>>     compatible:
>>       oneOf:
>> @@ -39,6 +41,7 @@ properties:
>>         - items:
>>             - enum:
>>                 - maxim,max96717
>> +              - maxim,max96793
>>             - const: maxim,max96717f
>>     '#gpio-cells':
>