All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mike Leach <mike.leach@linaro.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Stephen Boyd <swboyd@chromium.org>,
	devicetree-owner@vger.kernel.org
Subject: Re: [PATCHv3 0/2] Add support for replicators which loses context on clock removal
Date: Tue, 26 May 2020 12:31:46 +0530	[thread overview]
Message-ID: <8b3592edb443a091891d00e0fa32debc@codeaurora.org> (raw)
In-Reply-To: <20200525161553.GA31527@xps15>

Hi Mathieu,

On 2020-05-25 21:45, Mathieu Poirier wrote:
> Hi Sai,
> 
> On Sat, May 23, 2020 at 12:06:50AM +0530, Sai Prakash Ranjan wrote:
>> This series is mainly to add support for replicators
>> which lose context on removing AMBA clock like on SC7180
>> SoC where replicator in AOSS domain loses context.
>> 
> 
> I am good with this set but need a reviewed-by on the DT binding before 
> I can
> add it to my tree.  The same goes for your other set[1].
> 

Sure, let's wait for an ack from Rob and thanks for the reviews.

Thanks,
Sai

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member
of Code Aurora Forum, hosted by The Linux Foundation

WARNING: multiple messages have this Message-ID (diff)
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
	devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Cc: devicetree-owner@vger.kernel.org,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stephen Boyd <swboyd@chromium.org>,
	linux-arm-kernel@lists.infradead.org,
	Mike Leach <mike.leach@linaro.org>
Subject: Re: [PATCHv3 0/2] Add support for replicators which loses context on clock removal
Date: Tue, 26 May 2020 12:31:46 +0530	[thread overview]
Message-ID: <8b3592edb443a091891d00e0fa32debc@codeaurora.org> (raw)
In-Reply-To: <20200525161553.GA31527@xps15>

Hi Mathieu,

On 2020-05-25 21:45, Mathieu Poirier wrote:
> Hi Sai,
> 
> On Sat, May 23, 2020 at 12:06:50AM +0530, Sai Prakash Ranjan wrote:
>> This series is mainly to add support for replicators
>> which lose context on removing AMBA clock like on SC7180
>> SoC where replicator in AOSS domain loses context.
>> 
> 
> I am good with this set but need a reviewed-by on the DT binding before 
> I can
> add it to my tree.  The same goes for your other set[1].
> 

Sure, let's wait for an ack from Rob and thanks for the reviews.

Thanks,
Sai

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a 
member
of Code Aurora Forum, hosted by The Linux Foundation

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-05-26  7:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 18:36 [PATCHv3 0/2] Add support for replicators which loses context on clock removal Sai Prakash Ranjan
2020-05-22 18:36 ` Sai Prakash Ranjan
2020-05-22 18:36 ` [PATCHv3 1/2] coresight: replicator: Reset replicator if context is lost Sai Prakash Ranjan
2020-05-22 18:36   ` Sai Prakash Ranjan
2020-05-22 18:36 ` [PATCHv3 2/2] dt-bindings: arm: coresight: Add optional property to replicators Sai Prakash Ranjan
2020-05-22 18:36   ` Sai Prakash Ranjan
2020-05-25 16:01   ` Mathieu Poirier
2020-05-25 16:01     ` Mathieu Poirier
2020-05-25 16:15 ` [PATCHv3 0/2] Add support for replicators which loses context on clock removal Mathieu Poirier
2020-05-25 16:15   ` Mathieu Poirier
2020-05-26  7:01   ` Sai Prakash Ranjan [this message]
2020-05-26  7:01     ` Sai Prakash Ranjan
2020-05-28 14:48   ` Rob Herring
2020-05-28 14:48     ` Rob Herring
2020-05-28 17:40     ` Mathieu Poirier
2020-05-28 17:40       ` Mathieu Poirier

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=8b3592edb443a091891d00e0fa32debc@codeaurora.org \
    --to=saiprakash.ranjan@codeaurora.org \
    --cc=devicetree-owner@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=swboyd@chromium.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.