Re: [PATCH v3 1/6] dt-bindings: crypto: qcom,inline-crypto-engine: Fix legacy/new SoC strictness split

[Kuldeep Singh]

>> To re-iterate: You change the ABI for Hawi, this must be expressed and
>> explained why.
> 
> Ohh I see, hawi is different case(compared to milos/eliza) where
> bindings define the compatible but somehow was relaxed(got missed
> probably) from 2 clocks recommendation.
> Just hawi compatible is defined but no DT entry is present actually.
> 
>> I do not see any change in commit msg (listing "new SoC"
>> is not what I meant is not relevant here - it even suggests like
>> everything is here done without impact).

Hi Krzysztof,

It seems Herbert picked bindings patches of hawi/maili/nord and they are
now part of 2 clocks list.
This means there's no special case of hawi now and current change will
remain intact.

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/crypto/qcom,inline-crypto-engine.yaml#n60

Next rev just require rebasing. I'll do and post that.

-- 
Regards
Kuldeep