All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Hans Verkuil <hverkuil+cisco@kernel.org>,
	Quentin Freimanis <quentin@q-lab.dev>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>
Subject: Re: [PATCH v3 1/2] dt-bindings: media: i2c: Add onsemi AR0234 image sensor binding
Date: Tue, 1 Sep 2026 15:53:52 +0200	[thread overview]
Message-ID: <58c0d082-b527-4fd1-9f7a-74b58b4db54d@kernel.org> (raw)
In-Reply-To: <CAP1tNvT2+uNvcHf9=c_ysaM=gKrnz+5ZMTOq-8n_V+Ryx=yxLA@mail.gmail.com>

On 01/09/2026 12:32, Alexander Shiyan wrote:
> Hello.
> 
>>>> On Thu, Aug 20, 2026 at 10:55:23AM +0300, Alexander Shiyan wrote:
>>>>> Add devicetree binding for the onsemi AR0234 CMOS image sensor.
>>>>> Signed-off-by: Alexander Shiyan <eagle.alexander923@gmail.com>
> ...
>>>>> diff --git a/Documentation/devicetree/bindings/media/i2c/onnn,ar0234.yaml b/Documentation/devicetree/bindings/media/i2c/onnn,ar0234.yaml
>>> ...
>>>>> +properties:
>>>>> +  compatible:
>>>>> +    enum:
>>>>> +      - onnn,ar0234cssc
>>>>> +      - onnn,ar0234cssm
>>>>> +      - onnn,ar0234cs
>>>>> +    description:
>>>>> +      The AR0234 sensor exists in two different models, a colour variant
>>>>> +      (AR0234CSSC) and a monochrome variant (AR0234CSSM). The device exposes
>>>>> +      the model through registers, allowing for auto-detection with a common
>>>>> +      "onnn,ar0234cs" compatible string.
>>>>
>>>> So all devices are compatible? Then why compatibility is not expressed?
>>>> What are the actual programming differences between sc, sm and "none"
>>>> variants?
>>>
>>> Perhaps I need to revert to the compatibility strings that were used
>>> in version 2
>>> (https://patchwork.kernel.org/project/linux-media/patch/20260807102847.1813059-2-eagle.alexander923@gmail.com/).
>>>
>>> From a programming standpoint, it makes almost no difference which
>>> sensor is used
>>> - the only differences are in the output format and the format count.
>>> Either way, the driver always uses the sensor model determined via
>>> register reads.
>>> If the specified type does not match the detected one, only a warning
>>> will be printed.
>>
>> Devices should be made compatible with the fallback or even the color
>> and mono variants could be dropped. That depends on the difference
>> between color/mono.
> 
> Removing the separation would result in a regression.

What regression? You just proposed these compatibles, they are not
accepted, so how and what possible could ever regress?


Best regards,
Krzysztof

  reply	other threads:[~2026-09-01 13:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  7:55 [PATCH v3 0/2] media: i2c: Add onsemi AR0234 camera sensor driver Alexander Shiyan
2026-08-20  7:55 ` [PATCH v3 1/2] dt-bindings: media: i2c: Add onsemi AR0234 image sensor binding Alexander Shiyan
2026-08-20  8:01   ` sashiko-bot
2026-08-27  9:56   ` Krzysztof Kozlowski
2026-08-28  5:51     ` Alexander Shiyan
2026-08-28  6:36       ` Krzysztof Kozlowski
2026-09-01 10:32         ` Alexander Shiyan
2026-09-01 13:53           ` Krzysztof Kozlowski [this message]
2026-08-27  9:58   ` Krzysztof Kozlowski
2026-08-28  5:34     ` Alexander Shiyan
2026-08-28  6:32       ` Krzysztof Kozlowski
2026-08-20  7:55 ` [PATCH v3 2/2] media: i2c: Add onsemi AR0234 image sensor driver Alexander Shiyan
2026-08-20  8:11   ` sashiko-bot

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=58c0d082-b527-4fd1-9f7a-74b58b4db54d@kernel.org \
    --to=krzk@kernel.org \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eagle.alexander923@gmail.com \
    --cc=hverkuil+cisco@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=quentin@q-lab.dev \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.