[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e4d4dbf-0288-4155-8149-c233aa8c3a9d@kernel.org>
Date: Tue, 4 Mar 2025 09:12:08 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Viken Dadhaniya <quic_vdadhani@...cinc.com>
Cc: andi.shyti@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, gregkh@...uxfoundation.org, jirislaby@...nel.org,
broonie@...nel.or, andersson@...nel.org, konradybcio@...nel.org,
johan+linaro@...nel.org, dianders@...omium.org, agross@...nel.org,
linux-arm-msm@...r.kernel.org, linux-i2c@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org, linux-spi@...r.kernel.org,
quic_msavaliy@...cinc.com, quic_anupkulk@...cinc.com
Subject: Re: [PATCH v3 0/9] Add support to load QUP SE firmware from
On 04/03/2025 09:11, Krzysztof Kozlowski wrote:
> On Mon, Mar 03, 2025 at 06:13:40PM +0530, Viken Dadhaniya wrote:
>> In Qualcomm SoCs, firmware loading for Serial Engines (SE) in the QUP
>> hardware has traditionally been managed by TrustZone (TZ). This setup
>> handled Serial Engines(SE) assignments and access control permissions,
>> ensuring a high level of security but limiting flexibility and
>> accessibility.
>
>
> The most important part of cover letter (or patch changelog - not
> present either) is to explain dependencies and merging stratgy. This
Actually you have changelog per patch but this information is missing
there as well.
> cannot be taken by respective maintainers directly and you *MUST*
> clearly express it.
>
> Best regards,
> Krzysztof
>
Best regards,
Krzysztof
Powered by blists - more mailing lists