mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gokul Sriram P <quic_gokulsri@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <andersson@kernel.org>,
	<krzk+dt@kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <quic_viswanat@quicinc.com>, <quic_mmanikan@quicinc.com>,
	<quic_varada@quicinc.com>, <quic_srichara@quicinc.com>
Subject: Re: [PATCH 0/4] Add new driver for WCSS secure PIL loading
Date: Fri, 23 Aug 2024 15:19:23 +0530	[thread overview]
Message-ID: <f0134870-7349-4e9d-80e1-d254873d5035@quicinc.com> (raw)
In-Reply-To: <2b5105c6-ccc1-47fb-b22c-010537f39681@kernel.org>


On 8/22/2024 4:58 PM, Krzysztof Kozlowski wrote:
> On 22/08/2024 12:43, Gokul Sriram P wrote:
>> On 8/20/2024 4:42 PM, Krzysztof Kozlowski wrote:
>>> On 20/08/2024 10:55, Gokul Sriram Palanisamy wrote:
>>>> This series depends on q6 clock removal series [1].
>>> How? So this cannot be tested and merged?
>> Yes. Though TrustZone enables these clocks, since Linux Kernel will
>> consider these clock as unused.
>> These clock will be disabled so we cannot bring Q6 out of reset. So we
>> have the dependency set.
>> I posted this as a separate series because [1] 'remove unnecessary q6
>> clocks' series was already reviewed for some
>> versions.
> This is not a dependency in the kernel workflow. Nothing gets broken,
> nothing stops this patch from merging. Your remark is confusing and will
> either start questions or prevent applying the patchset.
>
Ok, got it. It will not break anything. Will post this series as 
independent series in v2.

thanks,

Gokul


      reply	other threads:[~2024-08-23  9:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20  8:55 Gokul Sriram Palanisamy
2024-08-20  8:55 ` [PATCH 1/2] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL Gokul Sriram Palanisamy
2024-08-20 11:20   ` Krzysztof Kozlowski
2024-08-22 10:47     ` Gokul Sriram P
2024-08-22 11:30       ` Krzysztof Kozlowski
     [not found]         ` <982ca02e-a0b0-4dac-9294-ae2c2fb3463f@quicinc.com>
2024-08-23 13:47           ` Krzysztof Kozlowski
2024-08-20  8:55 ` [PATCH 2/2] remoteproc: qcom: add hexagon based WCSS secure PIL driver Gokul Sriram Palanisamy
2024-08-20 11:25   ` Krzysztof Kozlowski
2024-08-22  9:01     ` Gokul Sriram P
2024-08-20  8:55 ` [PATCH 3/4] arm64: dts: qcom: ipq5332: add nodes to bringup q6 Gokul Sriram Palanisamy
2024-08-20 11:21   ` Krzysztof Kozlowski
2024-08-22 10:38     ` Gokul Sriram P
2024-08-20  8:55 ` [PATCH 4/4] arm64: dts: qcom: ipq9574: add nodes to bring up q6 Gokul Sriram Palanisamy
2024-08-20 11:12 ` [PATCH 0/4] Add new driver for WCSS secure PIL loading Krzysztof Kozlowski
2024-08-22 10:43   ` Gokul Sriram P
2024-08-22 11:28     ` Krzysztof Kozlowski
2024-08-23  9:49       ` Gokul Sriram P [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f0134870-7349-4e9d-80e1-d254873d5035@quicinc.com \
    --to=quic_gokulsri@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=quic_mmanikan@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --cc=quic_varada@quicinc.com \
    --cc=quic_viswanat@quicinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®