From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: "Zhi Mao 毛智" <zhi.mao@mediatek.com>,
angelogioacchino.delregno@collabora.com, conor+dt@kernel.org,
krzk+dt@kernel.org, mchehab@kernel.org, robh@kernel.org,
dongchun.zhu@mediatek.com
Cc: heiko@sntech.de
Subject: Re: [PATCH v3 2/3] media: i2c: Add GT97xx VCM driver
Date: Thu, 13 Jun 2024 01:05:49 +0100 [thread overview]
Message-ID: <171823714905.1550852.13442340621133903705@ping.linuxembedded.co.uk> (raw)
In-Reply-To: <18d2c28fc8b47889689a1506957ea2a308c80fa2.camel@mediatek.com>
Hi Zhi,
Also - Cc: Dongchun Zhu <dongchun.zhu@mediatek.com> who is listed as the
DW9768 VCM driver author...
Quoting Zhi Mao (毛智) (2024-06-12 12:13:40)
> Hi Angelo,
>
> Thanks for your review.
>
> On Wed, 2024-06-12 at 09:07 +0200, AngeloGioacchino Del Regno wrote:
> > Il 12/06/24 03:20, Zhi Mao ha scritto:
> > > Add a V4L2 sub-device driver for Giantec GT97xx VCM.
> > >
> > > Signed-off-by: Zhi Mao <zhi.mao@mediatek.com>
> >
> > Hello Zhi,
> >
> > I fail to see why would you need to upstream this new driver instead
> > of
> > simply adding the IC_INFO_REG to the already existing (and more
> > featureful)
> > dw9768 driver, which also seems to support the Giantec GT9769 VCM.
Even more so especially as
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/media/i2c/dw9768.c
already directly supports the compatible strings added by this driver -
surely we don't want multiple (near identical) drivers matching the same
compatible string?
> >
>
> Our project uses Giantec VCM hardware.
> For detailed vendor information, please visit: (
> https://en.giantec-semi.com/yqmd/164).
> The VCM datasheet we are referencing is provided by Giantec.
> Currently, the relationship between Giantec VCM and Dongwoon VCM is
> unclear, but Dongwoon seems to be another manufacturer of VCM
> hardware.
>
> From the perspective of software driver development and maintenance, it
> makes sense for each vendor's hardware should have its own software
> driver.
Personally, I don't think so. If two vendors make identical parts, we
shouldn't have two identical drivers.
I still have plans to refactor VCM drivers if I get some spare-time(tm)
as almost each driver does the same identical task. They're all just
copies of the boilerplate. That seems like something we should reduce,
not increase.
--
Kieran
> So, I upstream a new VCM driver for Giantec.
>
> > Cheers,
> > Angelo
next prev parent reply other threads:[~2024-06-13 0:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 1:20 [PATCH v3 0/3] media: i2c: Add support for GT97xx VCM Zhi Mao
2024-06-12 1:20 ` [PATCH v3 1/3] media: dt-bindings: i2c: add Giantec " Zhi Mao
2024-06-12 7:08 ` AngeloGioacchino Del Regno
2024-06-12 1:20 ` [PATCH v3 2/3] media: i2c: Add GT97xx VCM driver Zhi Mao
2024-06-12 7:07 ` AngeloGioacchino Del Regno
2024-06-12 11:13 ` Zhi Mao (毛智)
2024-06-13 0:05 ` Kieran Bingham [this message]
2024-06-13 19:51 ` Andy Shevchenko
2024-06-21 17:36 ` sakari.ailus
2024-06-12 1:20 ` [PATCH v3 3/3] MAINTAINERS: Add entry for " Zhi Mao
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=171823714905.1550852.13442340621133903705@ping.linuxembedded.co.uk \
--to=kieran.bingham@ideasonboard.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=dongchun.zhu@mediatek.com \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=zhi.mao@mediatek.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