Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Neeraj Soni <neeraj.soni@oss.qualcomm.com>
Cc: ulf.hansson@linaro.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, andersson@kernel.org,
	konradybcio@kernel.org, linux-mmc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: mmc: sdhci-msm: Add ICE phandle
Date: Mon, 19 Jan 2026 11:35:16 +0100	[thread overview]
Message-ID: <fce1d7e3-22e2-4a01-aea3-573900da8bd9@kernel.org> (raw)
In-Reply-To: <c6200c33-29b4-7bfc-1b07-6a04383f8dd1@oss.qualcomm.com>

On 19/01/2026 10:47, Neeraj Soni wrote:
> Hi,
> 
> On 1/16/2026 12:48 PM, Krzysztof Kozlowski wrote:
>> On 16/01/2026 07:50, Neeraj Soni wrote:
>>> Hi,
>>>
>>> On 1/15/2026 2:33 PM, Krzysztof Kozlowski wrote:
>>>> On Wed, Jan 14, 2026 at 03:18:47PM +0530, Neeraj Soni wrote:
>>>>> Starting with sc7280(kodiak), the ICE will have its own device-tree node.
>>>>> So add the qcom,ice property to reference it.
>>>>>
>>>>> Signed-off-by: Neeraj Soni <neeraj.soni@oss.qualcomm.com>
>>>>> ---
>>>>>  Documentation/devicetree/bindings/mmc/sdhci-msm.yaml | 4 ++++
>>>>>  1 file changed, 4 insertions(+)
>>>>>
>>>>> diff --git a/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml b/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml
>>>>> index 938be8228d66..8a6a25ceabe1 100644
>>>>> --- a/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml
>>>>> +++ b/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml
>>>>> @@ -140,6 +140,10 @@ properties:
>>>>>      $ref: /schemas/types.yaml#/definitions/uint32
>>>>>      description: platform specific settings for DLL_CONFIG reg.
>>>>>  
>>>>> +  qcom,ice:
>>>>> +    $ref: /schemas/types.yaml#/definitions/phandle
>>>>> +    description: phandle to the Inline Crypto Engine node
>>>>
>>>> Description should also say: for what purpose.
>>>>
>>>> You either have this phandle or ICE address space on sc7280 and newer.
>>>> You cannot have both, so your schema should encode it properly.
>>>>
>>> Sure. I will update this in next patch.
>>>
>>>> Otherwise you just sent something which already was on the list and it
>>>> even was reviewed:
>>>>
>>>> https://lore.kernel.org/all/ba3da82d-999b-b040-5230-36e60293e0fd@linaro.org/
>>>>
>>>> You even copied the commit msg but did copy the authorship!
>>>>
>>> Sure. Thanks for pointing out. I will fix the authorship in next patch.
>>
>> If you add if:then: cases, the patch will differ, so make it your own.
> 
> Okay.
> 
>> But sending exactly the same patch with the same commit msg as what is
>> already on the lists under your own name is not correct.
>>>>
> Okay this was not intended and have taken care of authorship in my other posts but i will ensure
> not to repeat in future.
> 
>>>> Anyway v3 and v4 were not correct and probably v2 should be used after
>>>> adjusting it with my comments.
>>>>
>>> Okay. As i see your comment in v2 here:
>>> https://lore.kernel.org/all/c8eea30f-5ea2-cfc9-273a-3c6e99a316b9@linaro.org/
>>>
>>> i guess what you want is not to drop the entries for clock but rather capture it
>>> in the "description" of the ICE phandle entry. Is this understanding correct?
>>
>> Clocks should not be touched, but reg should.
>>
> Okay but In sdhci-msm.yaml file:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/mmc/sdhci-msm.yaml#n78
> 
> the currenty entries for "reg-names" do not specify for which hardware register range they are added. So shall i add something like

Read the rest of the binding.

And finally wrap your emails correctly. I am bored asking this over and
over, so if there is silence in the future - you can guess why.

Best regards,
Krzysztof

  reply	other threads:[~2026-01-19 10:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-14  9:48 [PATCH v2 0/2] Enable Inline crypto engine for kodiak Neeraj Soni
2026-01-14  9:48 ` [PATCH v2 1/2] dt-bindings: mmc: sdhci-msm: Add ICE phandle Neeraj Soni
2026-01-15  9:03   ` Krzysztof Kozlowski
2026-01-16  6:50     ` Neeraj Soni
2026-01-16  7:18       ` Krzysztof Kozlowski
2026-01-19  9:47         ` Neeraj Soni
2026-01-19 10:35           ` Krzysztof Kozlowski [this message]
2026-01-14  9:48 ` [PATCH v2 2/2] arm64: dts: qcom: kodiak: enable the inline crypto engine for SDHC Neeraj Soni
2026-01-15  9:05   ` Krzysztof Kozlowski
2026-01-16  5:59     ` Neeraj Soni
2026-01-16  7:19       ` Krzysztof Kozlowski
2026-01-19  9:56         ` Neeraj Soni
2026-01-14 16:18 ` [PATCH v2 0/2] Enable Inline crypto engine for kodiak Rob Herring
2026-01-16 16:54   ` Krzysztof Kozlowski
2026-01-19 10:04     ` Neeraj Soni
2026-01-20  1:29       ` Rob Herring
2026-01-19 12:48   ` Neeraj Soni
2026-01-20  1:25     ` Rob Herring
2026-01-20  6:24       ` Neeraj Soni

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=fce1d7e3-22e2-4a01-aea3-573900da8bd9@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=neeraj.soni@oss.qualcomm.com \
    --cc=robh@kernel.org \
    --cc=ulf.hansson@linaro.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