[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7b8f488a-deac-4089-be7a-c0d76afca0fa@kernel.org>
Date: Thu, 22 Aug 2024 13:30:58 +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 22/08/2024 12:47, Gokul Sriram P wrote:
>>> +
>>> + interrupts:
>>> + items:
>>> + - description: Watchdog interrupt
>>> + - description: Fatal interrupt
>>> + - description: Ready interrupt
>>> + - description: Handover interrupt
>>> + - description: Stop acknowledge interrupt
>>> +
>>> + interrupt-names:
>>> + items:
>>> + - const: wdog
>>> + - const: fatal
>>> + - const: ready
>>> + - const: handover
>>> + - const: stop-ack
>>> +
>>> + clocks:
>>> + items:
>>> + - description: IM SLEEP clock
>> What is IM? Explain all acronyms.
>>
>> What is SLEEP?
>
> 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".
Best regards,
Krzysztof
Powered by blists - more mailing lists