Devicetree
 help / color / mirror / Atom feed
From: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: media: i2c: og0ve1b: Add OmniVision OG0VA1B camera sensor
Date: Mon, 6 Jul 2026 21:31:03 +0800	[thread overview]
Message-ID: <b702c745-1b5d-4b94-b2c6-46e79a427768@oss.qualcomm.com> (raw)
In-Reply-To: <df510ed0-815a-4d72-b7c5-05025d8dbfd6@linaro.org>

Hi Vladimir,

On 7/2/2026 8:24 PM, Vladimir Zapolskiy wrote:
> Hi Wenmeng,
> 
> thank you for the updates!
> 
> On 7/2/26 13:52, Wenmeng Liu wrote:
>> The OmniVision OG0VA1B is a monochrome image sensor closely related to
>> the already supported OG0VE1B. It shares the same SCCB control interface,
>> power supplies, clock and MIPI D-PHY description, but differs in its
>> chip ID, register programming and output format.
>>
>> Signed-off-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
>> ---
>>   Documentation/devicetree/bindings/media/i2c/ovti,og0ve1b.yaml | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/media/i2c/ 
>> ovti,og0ve1b.yaml b/Documentation/devicetree/bindings/media/i2c/ 
>> ovti,og0ve1b.yaml
>> index 
>> bd2f1ae23e6547032361924a6953000bab1129df..ae44ec2fa9035b4e19834888a41987ae9e25118f 100644
>> --- a/Documentation/devicetree/bindings/media/i2c/ovti,og0ve1b.yaml
>> +++ b/Documentation/devicetree/bindings/media/i2c/ovti,og0ve1b.yaml
>> @@ -21,7 +21,9 @@ allOf:
>>   properties:
>>     compatible:
>> -    const: ovti,og0ve1b
>> +    enum:
>> +      - ovti,og0va1b
>> +      - ovti,og0ve1b
>>     reg:
>>       maxItems: 1
>>
> 
> Since it becomes a shared dt documentation, it will be accepted to get
> a generalised description section also, in any case:
> 
> Reviewed-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> 

Thanks for your review, will change description in next version.

Best regards,
Wenmeng

  reply	other threads:[~2026-07-06 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 10:52 [PATCH v2 0/3] media: i2c: Add OmniVision OG0VA1B camera sensor driver Wenmeng Liu
2026-07-02 10:52 ` [PATCH v2 1/3] dt-bindings: media: i2c: og0ve1b: Add OmniVision OG0VA1B camera sensor Wenmeng Liu
2026-07-02 12:24   ` Vladimir Zapolskiy
2026-07-06 13:31     ` Wenmeng Liu [this message]
2026-07-02 19:21   ` Conor Dooley
2026-07-02 10:52 ` [PATCH v2 2/3] media: i2c: og0ve1b: Introduce per-sensor data structure Wenmeng Liu
2026-07-02 11:04   ` sashiko-bot
2026-07-02 13:10   ` Vladimir Zapolskiy
2026-07-06 13:34     ` Wenmeng Liu
2026-07-02 16:31   ` Bryan O'Donoghue
2026-07-06 13:36     ` Wenmeng Liu
2026-07-06 13:47       ` Bryan O'Donoghue
2026-07-02 10:52 ` [PATCH v2 3/3] media: i2c: og0ve1b: Add support for OmniVision OG0VA1B Wenmeng Liu
2026-07-02 13:16   ` Vladimir Zapolskiy
2026-07-06 13:35     ` Wenmeng Liu

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=b702c745-1b5d-4b94-b2c6-46e79a427768@oss.qualcomm.com \
    --to=wenmeng.liu@oss.qualcomm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=vladimir.zapolskiy@linaro.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