From: Sudeep Holla <sudeep.holla@arm.com>
To: Mike Leach <mike.leach@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
coresight@lists.linaro.org, linux-doc@vger.kernel.org,
linux-arm-msm@vger.kernel.org, mathieu.poirier@linaro.org,
suzuki.poulose@arm.com, robh+dt@kernel.org, maxime@cerno.tech,
liviu.dudau@arm.com, lorenzo.pieralisi@arm.com,
agross@kernel.org, corbet@lwn.net,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v9 11/15] dt-bindings: arm: Juno platform - add CTI entries to device tree.
Date: Tue, 11 Feb 2020 11:59:03 +0000 [thread overview]
Message-ID: <20200211115852.GA52147@bogus> (raw)
In-Reply-To: <20200210213924.20037-12-mike.leach@linaro.org>
On Mon, Feb 10, 2020 at 09:39:20PM +0000, Mike Leach wrote:
> Add in CTI entries for Juno r0, r1 and r2 to device tree entries.
>
I can take this patch alone unless you have plans to take all in go.
--
Regards,
Sudeep
next prev parent reply other threads:[~2020-02-11 11:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 21:39 [PATCH v9 00/15] CoreSight CTI Driver Mike Leach
2020-02-10 21:39 ` [PATCH v9 01/15] coresight: cti: Initial " Mike Leach
2020-02-21 17:06 ` Mathieu Poirier
2020-02-24 14:07 ` Mike Leach
2020-02-10 21:39 ` [PATCH v9 02/15] coresight: cti: Add sysfs coresight mgmt reg access Mike Leach
2020-02-10 21:39 ` [PATCH v9 03/15] coresight: cti: Add sysfs access to program function regs Mike Leach
2020-02-10 21:39 ` [PATCH v9 04/15] coresight: cti: Add sysfs trigger / channel programming API Mike Leach
2020-02-10 21:39 ` [PATCH v9 05/15] dt-bindings: arm: Adds CoreSight CTI hardware definitions Mike Leach
2020-02-10 21:39 ` [PATCH v9 06/15] coresight: cti: Add device tree support for v8 arch CTI Mike Leach
2020-02-10 21:39 ` [PATCH v9 07/15] coresight: cti: Add device tree support for custom CTI Mike Leach
2020-02-10 21:39 ` [PATCH v9 08/15] coresight: cti: Enable CTI associated with devices Mike Leach
2020-02-17 23:12 ` Mathieu Poirier
2020-02-21 0:20 ` Suzuki K Poulose
2020-02-21 16:51 ` Mathieu Poirier
2020-02-25 15:03 ` Mike Leach
2020-02-10 21:39 ` [PATCH v9 09/15] coresight: cti: Add connection information to sysfs Mike Leach
2020-02-10 21:39 ` [PATCH v9 10/15] dt-bindings: qcom: Add CTI options for qcom msm8916 Mike Leach
2020-02-10 21:39 ` [PATCH v9 11/15] dt-bindings: arm: Juno platform - add CTI entries to device tree Mike Leach
2020-02-11 11:59 ` Sudeep Holla [this message]
2020-02-12 22:12 ` Mathieu Poirier
2020-02-13 11:08 ` Sudeep Holla
2020-02-10 21:39 ` [PATCH v9 12/15] dt-bindings: hisilicon: Add CTI bindings for hi-6220 Mike Leach
2020-02-10 21:39 ` [PATCH v9 13/15] docs: coresight: Update documentation for CoreSight to cover CTI Mike Leach
2020-02-10 21:39 ` [PATCH v9 14/15] docs: sysfs: coresight: Add sysfs ABI documentation for CTI Mike Leach
2020-02-10 21:39 ` [PATCH v9 15/15] Update MAINTAINERS to add reviewer for CoreSight Mike Leach
2020-02-24 15:46 ` [PATCH v9 00/15] CoreSight CTI Driver Marc Gonzalez
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=20200211115852.GA52147@bogus \
--to=sudeep.holla@arm.com \
--cc=agross@kernel.org \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=maxime@cerno.tech \
--cc=mike.leach@linaro.org \
--cc=robh+dt@kernel.org \
--cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).