From: Mingxuan Guo <gmx472@qq.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, Mingxuan Guo <gmx472@qq.com>
Subject: [PATCH v2] dt-bindings: media: i2c: dongwoon,dw9768: add Giantec GT9764
Date: Tue, 13 Oct 2026 12:37:01 +0800 [thread overview]
Message-ID: <tencent_FA6A841DD9155FEEBFDEA7FE7310568E4606@qq.com> (raw)
The GT9764 is one of Giantec's VCM driver parts and shares the register
model of the GT9769 already covered by this binding: the vendor's VCM
driver application note (AN971) covers GT9764, GT9767, GT9768, GT9769,
GT9772 and GT9778, all built around the same 10-bit DAC with the AAC
actuator-control extensions.
Document it as a specific compatible that requires the GT9769 as its
fallback, so the existing driver binds through the GT9769 entry and no
driver change is needed.
Signed-off-by: Mingxuan Guo <gmx472@qq.com>
---
Changes in v2:
- Use the GT9769 as a fallback compatible instead of a standalone driver
entry (Conor Dooley), and drop the driver patch accordingly; this also
clears the Media CI warning about the compatible being undocumented.
Documentation/devicetree/bindings/media/i2c/dongwoon,dw9768.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/media/i2c/dongwoon,dw9768.yaml b/Documentation/devicetree/bindings/media/i2c/dongwoon,dw9768.yaml
--- a/Documentation/devicetree/bindings/media/i2c/dongwoon,dw9768.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/dongwoon,dw9768.yaml
@@ -20,9 +20,13 @@ description: |-
properties:
compatible:
- enum:
- - dongwoon,dw9768 # for DW9768 VCM
- - giantec,gt9769 # for GT9769 VCM
+ oneOf:
+ - enum:
+ - dongwoon,dw9768 # for DW9768 VCM
+ - giantec,gt9769 # for GT9769 VCM
+ - items:
+ - const: giantec,gt9764 # for GT9764 VCM
+ - const: giantec,gt9769 # fallback, same register model
reg:
maxItems: 1
next reply other threads:[~2026-10-13 4:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 4:37 Mingxuan Guo [this message]
2026-10-13 9:40 ` Krzysztof Kozlowski
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=tencent_FA6A841DD9155FEEBFDEA7FE7310568E4606@qq.com \
--to=gmx472@qq.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 \
/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
all inboxes | Powered by JetHome®