public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Nirujogi, Pratap" <pnirujog@amd.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Pratap Nirujogi <pratap.nirujogi@amd.com>,
	mchehab@kernel.org, hverkuil@xs4all.nl,
	dave.stevenson@raspberrypi.com, krzk@kernel.org,
	dan.carpenter@linaro.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, benjamin.chan@amd.com,
	bin.du@amd.com, grosikop@amd.com, king.li@amd.com,
	dantony@amd.com, Venkata Narendra Kumar Gutta <vengutta@amd.com>
Subject: Re: [PATCH v2] media: i2c: Add OV05C10 camera sensor driver
Date: Tue, 6 May 2025 07:45:24 +0000	[thread overview]
Message-ID: <aBm-FEdHqERKj9Am@kekkonen.localdomain> (raw)
In-Reply-To: <20250402012052.GG4845@pendragon.ideasonboard.com>

Hi Laurent,

On Wed, Apr 02, 2025 at 04:20:52AM +0300, Laurent Pinchart wrote:
> On Mon, Mar 31, 2025 at 03:17:22PM -0400, Nirujogi, Pratap wrote:
> > On 3/28/2025 9:18 PM, Bryan O'Donoghue wrote:
> > > On 28/03/2025 21:42, Pratap Nirujogi wrote:
> > >> From: Bin Du <Bin.Du@amd.com>
> > > 
> > >> +static const struct i2c_device_id ov05c10_id[] = {
> > >> +     {"ov05c10", 0 },
> > >> +     { }
> > >> +};
> > > 
> > > There's an IPU6/IPU7 version of this driver.
> > > 
> > > https://github.com/intel/ipu6-drivers/blob/master/drivers/media/i2c/ 
> > > ov05c10.c
> > > 
> > > Perhaps you could import the Intel ACPI name contained in there too.
> > > 
> > sure, will add Intel ACPI names too in V3. To be specific, I'm going to 
> > add the below table in addition to the existing "struct i2c_device_id 
> > ov05c10_id[]" table:
> > 
> > static const struct acpi_device_id ov05c10_acpi_ids[] = {
> > 	{ "OVTI05C1" },
> > 	{}
> > };
> 
> You could drop the i2c_device_id table if you added an OF device ID
> table, but you'll need DT bindings for that. Sakari, any best practice
> rule in this area ?

I don't think there should be a need for an I²C ID in any case, having just
ACPI _HID is fine.

DT bindings would of course be a plus.

> 
> > >> +
> > >> +MODULE_DEVICE_TABLE(i2c, ov05c10_id);
> > >> +
> > >> +static struct i2c_driver ov05c10_i2c_driver = {
> > >> +     .driver = {
> > >> +             .name = DRV_NAME,
> > >> +             .pm = pm_ptr(&ov05c10_pm_ops),
> > >> +     },
> > >> +     .id_table = ov05c10_id,
> > >> +     .probe = ov05c10_probe,
> > >> +     .remove = ov05c10_remove,
> > >> +};
> > >> +
> > >> +module_i2c_driver(ov05c10_i2c_driver);
> > >> +
> > >> +MODULE_AUTHOR("Pratap Nirujogi <pratap.nirujogi@amd.com>");
> > >> +MODULE_AUTHOR("Venkata Narendra Kumar Gutta <vengutta@amd.com>");
> > >> +MODULE_AUTHOR("Bin Du <bin.du@amd.com>");
> > >> +MODULE_DESCRIPTION("OmniVision OV05C1010 sensor driver");
> > >> +MODULE_LICENSE("GPL v2");
> > > 
> > > Why v2 ? Checkpatch will complain about v2 and BTW the IPU6 driver above
> > > is GPL not GPL v2.
> > 
> > sure, will replace "GPL v2" with "GPL" in V3.
> 

-- 
Regards,

Sakari Ailus

  parent reply	other threads:[~2025-05-06  8:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MhUYQD7uWnfZQAPq7VslFWPHOmx2B2UfAIpbMhLq1-7GC_i5bI2hhns_-ov_AAVpEH_VmDDFYkS5aOKBwnY61g==@protonmail.internalid>
2025-03-28 21:42 ` [PATCH v2] media: i2c: Add OV05C10 camera sensor driver Pratap Nirujogi
2025-03-29  1:18   ` Bryan O'Donoghue
2025-03-31 19:17     ` Nirujogi, Pratap
2025-04-02  1:20       ` Laurent Pinchart
2025-04-02 22:04         ` Nirujogi, Pratap
2025-05-06  7:45         ` Sakari Ailus [this message]
2025-05-06 11:29           ` Hans de Goede
2025-05-07 20:25             ` Nirujogi, Pratap
2025-04-08 21:09       ` Nirujogi, Pratap
2025-03-29  4:30   ` Krzysztof Kozlowski
2025-03-31 19:19     ` Nirujogi, Pratap

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=aBm-FEdHqERKj9Am@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=benjamin.chan@amd.com \
    --cc=bin.du@amd.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=dan.carpenter@linaro.org \
    --cc=dantony@amd.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=grosikop@amd.com \
    --cc=hverkuil@xs4all.nl \
    --cc=king.li@amd.com \
    --cc=krzk@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=pnirujog@amd.com \
    --cc=pratap.nirujogi@amd.com \
    --cc=vengutta@amd.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