From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-staging@lists.linux.dev, linux-renesas-soc@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: i2c: maxim,max96712: Add compatible for MAX96724
Date: Tue, 27 Aug 2024 20:03:34 +0200 [thread overview]
Message-ID: <20240827180334.GI2636928@fsdn.se> (raw)
In-Reply-To: <7dadf8dd-ad54-4e4f-a336-adc3444df4b0@kernel.org>
Hi Krzysztof,
Thanks for your feedback.
On 2024-08-27 16:53:20 +0200, Krzysztof Kozlowski wrote:
> On 27/08/2024 15:18, Niklas Söderlund wrote:
> > The MAX96712 and MAX96724 are almost identical and can be supported by
> > the same driver, add a compatible for MAX96724.
>
> The driver statement in this context is meaningless. You did not make
> them compatible so what does it matter?
Agreed, this commit message can be improved.
>
> >
> > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > ---
> > * Changes since v1
> > - Group in series together with driver change.
> > ---
> > .../devicetree/bindings/media/i2c/maxim,max96712.yaml | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml b/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml
> > index 6c72e77b927c..26f85151afbd 100644
> > --- a/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml
> > +++ b/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml
> > @@ -25,7 +25,10 @@ description: |
> >
> > properties:
> > compatible:
> > - const: maxim,max96712
> > + items:
> > + - enum:
> > + - maxim,max96712
> > + - maxim,max96724
>
> Driver change tells these are compatible and version is detectable.
> Express it in the binding with fallback or explain in commit msg why
> they are not compatible.
It is, and as you point out the commit message can be improved. It
should have made it clear that what is supported by the staging driver
(test pattern generator) is similar for the two devices, the full device
have larger differences.
Before this driver can move out of staging the full GMSL side of things
needs to be added and there they differ more and will need different
bindings as one device have more PHYs then the other for example. Run
time detecting is not enough to be able to verify that in DTS files.
I will fix this for the next version.
>
>
> Best regards,
> Krzysztof
>
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2024-08-27 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 13:18 [PATCH v2 0/2] media: staging: max96712: Add support for MAX96724 Niklas Söderlund
2024-08-27 13:18 ` [PATCH v2 1/2] dt-bindings: i2c: maxim,max96712: Add compatible " Niklas Söderlund
2024-08-27 14:53 ` Krzysztof Kozlowski
2024-08-27 18:03 ` Niklas Söderlund [this message]
2024-08-28 5:45 ` Krzysztof Kozlowski
2024-08-27 13:18 ` [PATCH v2 2/2] media: staging: max96712: Add support " Niklas Söderlund
2024-08-27 13:32 ` Sakari Ailus
2024-08-27 17:57 ` Niklas Söderlund
2024-08-27 21:00 ` Sakari Ailus
2024-08-27 13:55 ` Tommaso Merciai
2024-08-28 10:02 ` Julien Massot
2024-09-04 12:45 ` Tommaso Merciai
2024-08-27 18:21 ` Dan Carpenter
2024-08-28 5:51 ` Biju Das
2024-08-28 9:41 ` Julien Massot
2024-08-28 10:00 ` Niklas Söderlund
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=20240827180334.GI2636928@fsdn.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).