[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2a8c20ce-0c90-4e59-ab77-7c71de21e502@kernel.org>
Date: Fri, 23 Aug 2024 15:47:43 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Gokul Sriram P <quic_gokulsri@...cinc.com>,
q@...k-bin.smtp.subspace.kernel.org
Cc: andersson@...nel.org, krzk+dt@...nel.org, linux-arm-msm@...r.kernel.org,
linux-remoteproc@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, quic_viswanat@...cinc.com,
quic_mmanikan@...cinc.com, quic_varada@...cinc.com, quic_srichara@...cinc.com
Subject: Re: [PATCH 1/2] dt-bindings: remoteproc: qcom: document hexagon based
WCSS secure PIL
On 23/08/2024 11:47, Gokul Sriram P wrote:
>
> On 8/22/2024 5:00 PM, Krzysztof Kozlowski wrote:
>>> IM_SLEEP_CLK - Internal Module sleep clock needed for Q6 reset.
>>>
>>> SLEEP is not an acronym here.
>> Then probably you mean "Internal sleep", although "internal" is also
>> confusing. Devices do not receive as input something which is internal
>> to them.
>>
>>>>> +
>>>>> + clock-names:
>>>>> + items:
>>>>> + - const: im_sleep
>>>> sleep? Are there different sleep clocks here?
>>> We have different branches of sleep clk each enabled separately.
>>>
>>> im_sleep is one of those branches that q6 uses.
>> So this device misses other branches? Then provide them. Otherwise it is
>> just "sleep".
>
> ok, I shall keep it as simply "sleep" and move on? Other branches of
> sleep clk are irrelevant to remoteproc.
Then it is "sleep". The name here describes the clock input in this
device, not the clock in other places.
Best regards,
Krzysztof
Powered by blists - more mailing lists