[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z1LZYOJbl4snJu/u@hu-wasimn-hyd.qualcomm.com>
Date: Fri, 6 Dec 2024 16:30:48 +0530
From: Wasim Nazir <quic_wasimn@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
CC: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio
<konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski
<krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, <linux-arm-msm@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<kernel@...cinc.com>
Subject: Re: [PATCH v3 3/5] dt-bindings: arm: qcom: Document rb8/ride/ride-r3
on QCS9075
On Wed, Nov 20, 2024 at 05:43:12PM +0100, Krzysztof Kozlowski wrote:
> On 19/11/2024 18:49, Wasim Nazir wrote:
> > qcs9075 rb8, ride & ride-r3 boards are based on QCS9075 SoC.
> >
> > QCS9075 is compatible IoT-industrial grade variant of SA8775p SoC
> > without safety monitorng feature of SAfety-IsLand subsystem.
>
> SA or Sa?
> Also some typos above.
SAfety-IsLand (SAIL) was intended. I will rectify it along with
other typos.
>
> > This subsystem continues to supports other features like built-in
> > self-test, error-detection, reset-handling, etc.
>
> Which subsystem? How does it matter for the board? Drop all marketing
> stuff from here and rather explain why this is not related to qcs9100.
> We had quite a lot of talks and I am surprised seeing this without any
> earlier references.
It is for SAIL subsystem. It does not matter to the board but it is for
the SoC.
>
>
>
>
> Best regards,
> Krzysztof
Thanks & Regards,
Wasim
Powered by blists - more mailing lists