mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	<alexandre.belloni@bootlin.com>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <jarkko.nikula@linux.intel.com>,
	<linux-i3c@lists.infradead.org>, <linux-arm-msm@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 2/3] i3c: master: Add Qualcomm I3C master controller driver
Date: Thu, 13 Feb 2025 00:59:56 +0530	[thread overview]
Message-ID: <b873c744-6b38-4ea0-a5de-2cc7dd0e4501@quicinc.com> (raw)
In-Reply-To: <20250211214128.GB1215572-robh@kernel.org>

Thanks a lot Rob ! sorry, i was late to respond on this while waiting 
for other comments agreements.

On 2/12/2025 3:11 AM, Rob Herring wrote:
> On Mon, Feb 10, 2025 at 09:41:28PM +0530, Mukesh Kumar Savaliya wrote:
>> Thanks Krzysztof !
>>
>> On 2/9/2025 5:10 PM, Krzysztof Kozlowski wrote:
>>> On 07/02/2025 13:03, Mukesh Kumar Savaliya wrote:
>>>>>> +	gi3c->se.clk = devm_clk_get(&pdev->dev, "se-clk");
>>>>>> +	if (IS_ERR(gi3c->se.clk)) {
>>>>>> +		ret = PTR_ERR(gi3c->se.clk);
>>>>>> +		dev_err(&pdev->dev, "Error getting SE Core clk %d\n", ret);
>>>>>> +		return ret;
>>>>>> +	}
>>>>>> +
>>>>>> +	ret = device_property_read_u32(&pdev->dev, "se-clock-frequency", &gi3c->clk_src_freq);
>>>>>
>>>>> You never tested your DTS or this code... Drop
>>>>>
>>>> I have tested on SM8550 MTP only. Below entry in my internal/local DTSI.
>>>
>>>
>>> And how is it supposed to work? Are you going to send us your local
>>> internal DTSI? Is it going to pass any checks?
>> was saying about code was testing with MTP. DTS was tested using dt-bindings
>> check.
> 
> make dtbs_check is how you test.
Sure, we are running "make dt_binding_check 
DT_SCHEMA_FILES=qcom,i3c-master.yaml"
> 
>> I should add "se-clock-frequency" and "dfs-index"
> 
> No. We already have standard clock properties and we don't put indexes
> into DT.
> 
Okay, sure Rob. I shall remove both of these and set internally within 
driver as they can be set to default.
> Rob


  reply	other threads:[~2025-02-12 19:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 14:31 [PATCH v1 0/3] Add Qualcomm i3c master controller driver support Mukesh Kumar Savaliya
2025-02-05 14:31 ` [PATCH v1 1/3] dt-bindings: i3c: Add Qualcomm I3C master controller bindings Mukesh Kumar Savaliya
2025-02-05 14:42   ` Krzysztof Kozlowski
2025-02-06 13:43     ` Mukesh Kumar Savaliya
2025-02-07 12:03       ` Mukesh Kumar Savaliya
2025-02-09 11:46         ` Krzysztof Kozlowski
2025-02-10 16:11           ` Mukesh Kumar Savaliya
2025-02-09 11:45       ` Krzysztof Kozlowski
2025-02-10 16:12         ` Mukesh Kumar Savaliya
2025-02-11 21:39           ` Rob Herring
2025-02-12  6:54             ` Krzysztof Kozlowski
2025-02-12 14:15             ` Mukesh Kumar Savaliya
2025-02-05 14:31 ` [PATCH v1 2/3] i3c: master: Add Qualcomm I3C master controller driver Mukesh Kumar Savaliya
2025-02-05 14:46   ` Krzysztof Kozlowski
2025-02-07 12:03     ` Mukesh Kumar Savaliya
2025-02-09 11:40       ` Krzysztof Kozlowski
2025-02-10 16:11         ` Mukesh Kumar Savaliya
2025-02-11 21:41           ` Rob Herring
2025-02-12 19:29             ` Mukesh Kumar Savaliya [this message]
2025-02-12 19:39               ` Krzysztof Kozlowski
2025-02-12 19:49                 ` Mukesh Kumar Savaliya
2025-02-06 16:48   ` Frank Li
2025-02-07 12:16     ` Mukesh Kumar Savaliya
2025-02-05 14:31 ` [PATCH v1 3/3] MAINTAINERS: Add maintainer for Qualcomm's I3C driver Mukesh Kumar Savaliya
2025-02-05 16:23 ` [PATCH v1 0/3] Add Qualcomm i3c master controller driver support Wolfram Sang
2025-02-07 12:05   ` Mukesh Kumar Savaliya

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=b873c744-6b38-4ea0-a5de-2cc7dd0e4501@quicinc.com \
    --to=quic_msavaliy@quicinc.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.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

all inboxes | Powered by JetHome®