From: Leo Yan <leo.yan@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Wei Xu <xuwei5@hisilicon.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Michael Turquette <mturquette@baylibre.com>,
Li Pengcheng <lipengcheng8@huawei.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 0/2] Add support for Hi6220 coresight
Date: Sat, 7 Oct 2017 20:18:02 +0800 [thread overview]
Message-ID: <20171007121802.GC23080@leoy-linaro> (raw)
In-Reply-To: <20170901013301.GN21656@codeaurora.org>
Hi Stephen, Wei,
On Thu, Aug 31, 2017 at 06:33:01PM -0700, Stephen Boyd wrote:
> On 09/01, Leo Yan wrote:
> > This patch series adds support for coresight on Hi6220; the first patch
> > is to fix coresight PLL so can avoid system hang after we enable
> > coresight, the second patch is to add DT binding according to coresight
> > topology.
> >
> > The patch has been tested on Hikey; By using OpenCSD snapshot mode, it
> > can successfully decode ETF and ETB trace data.
> >
>
> I can take the first one and second one goes through arm-soc?
Could you pick these two patches for Hi6220 coresight enabling for
this merge window? Or need me resend these two patches?
Thanks,
Leo Yan
next prev parent reply other threads:[~2017-10-07 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 0:47 [PATCH 0/2] Add support for Hi6220 coresight Leo Yan
2017-09-01 0:47 ` [PATCH 1/2] clk: hi6220: mark clock cs_atb_syspll as critical Leo Yan
2017-09-01 0:47 ` [PATCH 2/2] arm64: dts: hi6220: add coresight binding Leo Yan
2017-09-01 1:33 ` [PATCH 0/2] Add support for Hi6220 coresight Stephen Boyd
2017-10-07 12:18 ` Leo Yan [this message]
2017-10-13 8:57 ` Wei Xu
2017-11-01 15:48 ` Michael Turquette
2017-11-02 10:41 ` Leo Yan
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=20171007121802.GC23080@leoy-linaro \
--to=leo.yan@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipengcheng8@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).