public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Julien Massot <julien.massot@collabora.com>
Cc: linux-media@vger.kernel.org, kernel@collabora.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	mchehab@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	sakari.ailus@iki.fi
Subject: Re: [PATCH v4 2/4] dt-bindings: media: add Maxim MAX96714 GMSL2 Deserializer
Date: Fri, 8 Mar 2024 16:50:16 +0000	[thread overview]
Message-ID: <20240308-blank-issue-857c16294c17@spud> (raw)
In-Reply-To: <7d0197b9-9008-4260-86e9-4b7f7017b3b6@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]

On Fri, Mar 08, 2024 at 04:48:16PM +0100, Julien Massot wrote:
> 
> 
> On 3/8/24 16:07, Conor Dooley wrote:
> > On Fri, Mar 08, 2024 at 03:08:12PM +0100, Julien Massot wrote:
> > > On 3/7/24 20:21, Conor Dooley wrote:
> > > > On Tue, Mar 05, 2024 at 04:26:06PM +0100, Julien Massot wrote:
> > > > > Add DT bindings for Maxim MAX96714 GMSL2 Deserializer.
> > > > > 
> > > > > Signed-off-by: Julien Massot <julien.massot@collabora.com>
> > > > > ---
> > > > > Change since v3:
> > > > >    - Renamed file to maxim,max96714.yaml dropped the 'f' suffix
> > > > 
> > > > Why? The filename should match the compatible, which /does/ have an f.
> > > All the work has been done on MAX96714F variant of this Maxim GMSL2
> > > deserializer.
> > > The driver and the binding remain suitable for all variants of this chipset,
> > > since they share the same
> > > register mapping, similar features etc..
> > > 
> > > MAX96714 exists in different variant: MAX96714 / MAX96714F / MAX96714K that
> > > will be easy
> > > to add support for this binding and driver later.
> > 
> > Either document the non-f version if it really is that similar, using
> > all of the same properties, or name the file after the version you've
> > actually documented. I don't see why this particular case should be
> > given an exception to how bindings are named.
> > 
> > What is the actual difference between the f and non f versions? Is it
> > visible to software?
> 
> Yes there are a few differences visible to the software, for example the
> GMSL
> link rate since MAX96714 support 6 and 3 Gbps, while MAX96714F only supports
> 3Gbps.
> the registers map is the same, but a few values are not possible with the
> 'f' version.
> 
> I will add a compatible for the non 'f' version, and will do the same for
> the max96717 binding.

It's not immediately clear if that means that the f version should be a
fallback for the non-f version, but sounds like it could be if the
difference is purely that there's a reduced set of link rates or
similar.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-03-08 16:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 15:26 [PATCH v4 0/4] Add support for MAX96714F and MAX96717F GMSL2 ser/des Julien Massot
2024-03-05 15:26 ` [PATCH v4 1/4] dt-bindings: media: add Maxim MAX96717 GMSL2 Serializer Julien Massot
2024-03-07 19:22   ` Conor Dooley
2024-03-05 15:26 ` [PATCH v4 2/4] dt-bindings: media: add Maxim MAX96714 GMSL2 Deserializer Julien Massot
2024-03-07 19:21   ` Conor Dooley
2024-03-08 14:08     ` Julien Massot
2024-03-08 15:07       ` Conor Dooley
2024-03-08 15:48         ` Julien Massot
2024-03-08 16:50           ` Conor Dooley [this message]
2024-03-05 15:26 ` [PATCH v4 3/4] media: i2c: add MAX96717 driver Julien Massot
2024-03-05 15:26 ` [PATCH v4 4/4] media: i2c: add MAX96714 driver Julien Massot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240308-blank-issue-857c16294c17@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=julien.massot@collabora.com \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox