mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nirujogi, Pratap" <pnirujog@amd.com>
To: Mehdi Djait <mehdi.djait@linux.intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
	Pratap Nirujogi <pratap.nirujogi@amd.com>,
	mchehab@kernel.org, hverkuil@xs4all.nl,
	bryan.odonoghue@linaro.org, krzk@kernel.org,
	dave.stevenson@raspberrypi.com, hdegoede@redhat.com,
	jai.luthra@ideasonboard.com, tomi.valkeinen@ideasonboard.com,
	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, vengutta@amd.com,
	Svetoslav.Stoilov@amd.com, Yana.Zheleva@amd.com
Subject: Re: [PATCH v3 RESEND] media: i2c: Add OV05C10 camera sensor driver
Date: Tue, 24 Jun 2025 16:01:51 -0400	[thread overview]
Message-ID: <db804aaf-3842-471b-874a-08d5374a76bf@amd.com> (raw)
In-Reply-To: <892063b4-165a-4d6e-a6bd-94ef58c0ee73@amd.com>



On 6/24/2025 2:26 PM, Nirujogi, Pratap wrote:
> Hi Mehdi, Sakari, Laurent,
> 
> On 6/24/2025 7:27 AM, Mehdi Djait wrote:
>> Caution: This message originated from an External Source. Use proper 
>> caution when opening attachments, clicking links, or responding.
>>
>>
>> Hi Laurent, Hi Sakari,
>>
>> On Tue, Jun 24, 2025 at 01:27:45PM +0300, Laurent Pinchart wrote:
>>> On Tue, Jun 24, 2025 at 10:20:34AM +0000, Sakari Ailus wrote:
>>>> On Tue, Jun 24, 2025 at 10:19:35AM +0000, Sakari Ailus wrote:
>>>>> On Tue, Jun 24, 2025 at 10:35:18AM +0200, Mehdi Djait wrote:
>>>>>> On Tue, Jun 24, 2025 at 01:05:03AM +0300, Laurent Pinchart wrote:
>>>>>>> On Mon, Jun 23, 2025 at 05:51:48PM -0400, Nirujogi, Pratap wrote:
>>>>>>>> On 6/16/2025 6:49 PM, Nirujogi, Pratap wrote:
>>>>>>>>>>> +static int ov05c10_probe(struct i2c_client *client)
>>>>>>>>>>> +{
>>>>>>>>>>> +     struct ov05c10 *ov05c10;
>>>>>>>>>>> +     u32 clkfreq;
>>>>>>>>>>> +     int ret;
>>>>>>>>>>> +
>>>>>>>>>>> +     ov05c10 = devm_kzalloc(&client->dev, sizeof(*ov05c10),
>>>>>>>>>>> GFP_KERNEL);
>>>>>>>>>>> +     if (!ov05c10)
>>>>>>>>>>> +             return -ENOMEM;
>>>>>>>>>>> +
>>>>>>>>>>> +     struct fwnode_handle *fwnode = dev_fwnode(&client->dev);
>>>>>>>>>>> +
>>>>>>>>>>> +     ret = fwnode_property_read_u32(fwnode, "clock-frequency",
>>>>>>>>>>> &clkfreq);
>>>>>>>>>>> +     if (ret)
>>>>>>>>>>> +             return  dev_err_probe(&client->dev, -EINVAL,
>>>>>>>>>>> +                                   "fail to get clock freq\n");
>>>>>>>>>>
>>>>>>>>>> Let's try to land
>>>>>>>>>> https://lore.kernel.org/linux-media/20250521104115.176950-1-
>>>>>>>>>> mehdi.djait@linux.intel.com/
>>>>>>>>>> and replace the code above with devm_v4l2_sensor_clk_get().
>>>>>>>>>>
>>>>>>>>> Ok, we will verify on our side.
>>>>>>>>
>>>>>>>> We tried using devm_v4l2_sensor_clk_get() and found its required 
>>>>>>>> to add
>>>>>>>> support for software_node to make it work with this driver.
>>>>>>>
>>>>>>> Why is that ?
>>>>>>>
>>>>>>>> Please refer
>>>>>>>> the changes below and let us know if these should be submitted as a
>>>>>>>> separate patch.
>>>>>>
>>>>>> The helper is still not merged, so no patch is required.
>>>>>>
>>>>>> I will see if a change is needed from the helper side or the 
>>>>>> OV05C10 side.
>>>>>
>>>>> I wonder if there's a better way to figure out if you're running on 
>>>>> a DT or
>>>>> ACPI based system than getting the device's parents and checking 
>>>>> which one
>>>>> you find first, DT or ACPI. I think that should work for now at least.
>>>>
>>>> Or, rather, checking for non-OF node here would probably work the 
>>>> best. I
>>>> wouldn't expect these to be software node based on DT systems ever.
>>>
>>> Until it happens :-) And we'll handle it then.
>>
>> So we have the following:
>>
>> - The problem with this driver is due to lack of proper ACPI
>>    description. HW is already shipping and AMD will work on better ACPI
>>    description for future models. See [1]
>>
> Thanks Mehdi for clarifying and providing the reference from the 
> associated x86/platform driver patch.
> 
> yes, thats true we have to add software_nodes to mitigate the issue 
> caused by incomplete description of camera device in ACPI tables.
> 
> For future models we are working on a plan to address this issue 
> following the MIPI DisCo Imaging Spec suggested by Sakari to properly 
> describe the camera device in ACPI. Please see [A]
> 
> Once again thanks everyone for the support!
> 
> [A] https://lore.kernel.org/ 
> lkml/2a9ba94e-7985-4ba9-88c6-45b8cf4d001f@amd.com/
> 
>> - software_node can also be used on DT systems
>>
>> [1] https://lore.kernel.org/lkml/0d801367- 
>> da24-4596-83d9-08ccd89ca670@redhat.com/
>>
>> Now going back to the helper. If we want to support this case:
>>
>> Approach 1: software_node || acpi
>>
>> --- a/drivers/media/v4l2-core/v4l2-common.c
>> +++ b/drivers/media/v4l2-core/v4l2-common.c
>> @@ -682,16 +682,17 @@ struct clk *devm_v4l2_sensor_clk_get(struct 
>> device *dev, const char *id)
>>          const char *clk_id __free(kfree) = NULL;
>>          struct clk_hw *clk_hw;
>>          struct clk *clk;
>> -       bool acpi_node;
>> +       bool acpi_sw_node;
>>          u32 rate;
>>          int ret;
>>
>>          clk = devm_clk_get_optional(dev, id);
>>          ret = device_property_read_u32(dev, "clock-frequency", &rate);
>> -       acpi_node = is_acpi_node(dev_fwnode(dev));
>> +       acpi_sw_node = is_acpi_node(dev_fwnode(dev)) ||
>> +                      is_software_node(dev_fwnode(dev));
>>
>>          if (clk) {
>> -               if (!ret && acpi_node) {
>> +               if (!ret && acpi_sw_node) {
>>                          ret = clk_set_rate(clk, rate);
>>                          if (ret) {
>>                                  dev_err(dev, "Failed to set clock 
>> rate: %u\n",
>> @@ -705,7 +706,7 @@ struct clk *devm_v4l2_sensor_clk_get(struct device 
>> *dev, const char *id)
>>          if (ret)
>>                  return ERR_PTR(ret);
>>
>> -       if (!IS_ENABLED(CONFIG_COMMON_CLK) || !acpi_node)
>> +       if (!IS_ENABLED(CONFIG_COMMON_CLK) || !acpi_sw_node)
>>                  return ERR_PTR(-ENOENT);
>>
>>          if (!id) {
>>
>>
>> Approach 2: of_node
>>
>> --- a/drivers/media/v4l2-core/v4l2-common.c
>> +++ b/drivers/media/v4l2-core/v4l2-common.c
>> @@ -682,16 +682,16 @@ struct clk *devm_v4l2_sensor_clk_get(struct 
>> device *dev, const char *id)
>>          const char *clk_id __free(kfree) = NULL;
>>          struct clk_hw *clk_hw;
>>          struct clk *clk;
>> -       bool acpi_node;
>> +       bool of_node;
>>          u32 rate;
>>          int ret;
>>
>>          clk = devm_clk_get_optional(dev, id);
>>          ret = device_property_read_u32(dev, "clock-frequency", &rate);
>> -       acpi_node = is_acpi_node(dev_fwnode(dev));
>> +       of_node = is_of_node(dev_fwnode(dev));
>>
>>          if (clk) {
>> -               if (!ret && acpi_node) {
>> +               if (!ret && !of_node) {
>>                          ret = clk_set_rate(clk, rate);
>>                          if (ret) {
>>                                  dev_err(dev, "Failed to set clock 
>> rate: %u\n",
>> @@ -705,7 +705,7 @@ struct clk *devm_v4l2_sensor_clk_get(struct device 
>> *dev, const char *id)
>>          if (ret)
>>                  return ERR_PTR(ret);
>>
>> -       if (!IS_ENABLED(CONFIG_COMMON_CLK) || !acpi_node)
>> +       if (!IS_ENABLED(CONFIG_COMMON_CLK) || of_node)
>>                  return ERR_PTR(-ENOENT);
>>
>>          if (!id) {
>>
> Thanks for proposing "approach 2 using !swnode", I verified and confirm 
> it works at my end.
> 
sorry,  fixing the typo - I meant "approach 2 using !of_node".

Thanks,
Pratap


> Thanks,
> Pratap
>>
>> -- 
>> Kind Regards
>> Mehdi Djait
> 


  reply	other threads:[~2025-06-24 20:02 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09 19:42 Pratap Nirujogi
2025-06-13  4:55 ` Hao Yao
2025-06-13 11:02   ` Kieran Bingham
2025-06-13 12:05     ` Bryan O'Donoghue
2025-06-16 23:15       ` Nirujogi, Pratap
2025-06-16 23:46     ` Nirujogi, Pratap
2025-06-28 19:23       ` Sakari Ailus
2025-06-13 22:02   ` Sakari Ailus
2025-06-14 22:52     ` Laurent Pinchart
2025-06-16 22:33       ` Nirujogi, Pratap
2025-06-29  7:40         ` Sakari Ailus
2025-06-30 22:31           ` Nirujogi, Pratap
2025-07-02  6:08             ` Yan, Dongcheng
2025-07-02  6:12               ` Sakari Ailus
2025-07-02 16:47                 ` Nirujogi, Pratap
2025-07-03  6:24                   ` Yan, Dongcheng
2025-07-05 11:45                     ` Nirujogi, Pratap
2025-07-06  9:11                   ` Sakari Ailus
2025-07-08 15:31                     ` Nirujogi, Pratap
2025-06-23 11:27       ` Sakari Ailus
2025-06-23 12:06         ` Laurent Pinchart
2025-06-23 21:53           ` Nirujogi, Pratap
2025-06-23 22:11             ` Laurent Pinchart
2025-06-16 23:12     ` Nirujogi, Pratap
2025-06-23 12:09       ` Laurent Pinchart
2025-06-23 13:22         ` Sakari Ailus
2025-06-23 13:42           ` Laurent Pinchart
2025-06-23 21:55             ` Nirujogi, Pratap
2025-06-23 22:06               ` Laurent Pinchart
2025-06-23 23:21                 ` Nirujogi, Pratap
2025-06-25 22:06               ` Nirujogi, Pratap
2025-06-26 11:11                 ` Kieran Bingham
2025-06-26 12:23                   ` Laurent Pinchart
2025-06-26 18:22                     ` Nirujogi, Pratap
2025-06-26 18:56                       ` Laurent Pinchart
2025-06-26 19:21                         ` Nirujogi, Pratap
2025-06-26 18:14                   ` Nirujogi, Pratap
2025-06-17  0:19   ` Nirujogi, Pratap
2025-06-15  0:09 ` Laurent Pinchart
2025-06-16 22:49   ` Nirujogi, Pratap
2025-06-23 21:51     ` Nirujogi, Pratap
2025-06-23 22:05       ` Laurent Pinchart
2025-06-23 23:28         ` Nirujogi, Pratap
2025-06-24  0:19           ` Laurent Pinchart
2025-06-24 18:49             ` Nirujogi, Pratap
2025-06-24 19:00               ` Laurent Pinchart
2025-06-24 19:49                 ` Nirujogi, Pratap
2025-06-24  8:35         ` Mehdi Djait
2025-06-24 10:19           ` Sakari Ailus
2025-06-24 10:20             ` Sakari Ailus
2025-06-24 10:27               ` Laurent Pinchart
2025-06-24 11:27                 ` Mehdi Djait
2025-06-24 11:33                   ` Laurent Pinchart
2025-06-24 11:46                   ` Sakari Ailus
2025-06-24 16:34                     ` Mehdi Djait
2025-06-24 20:24                       ` Nirujogi, Pratap
2025-06-25  6:11                       ` Sakari Ailus
2025-06-24 18:26                   ` Nirujogi, Pratap
2025-06-24 20:01                     ` Nirujogi, Pratap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-15 22:41 Pratap Nirujogi

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=db804aaf-3842-471b-874a-08d5374a76bf@amd.com \
    --to=pnirujog@amd.com \
    --cc=Svetoslav.Stoilov@amd.com \
    --cc=Yana.Zheleva@amd.com \
    --cc=benjamin.chan@amd.com \
    --cc=bin.du@amd.com \
    --cc=bryan.odonoghue@linaro.org \
    --cc=dantony@amd.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=grosikop@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jai.luthra@ideasonboard.com \
    --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=mehdi.djait@linux.intel.com \
    --cc=pratap.nirujogi@amd.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tomi.valkeinen@ideasonboard.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

all inboxes | Powered by JetHome®