From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm64: dts: juno: Adds missing CoreSight STM component.
Date: Thu, 12 Jan 2017 12:11:47 +0000 [thread overview]
Message-ID: <4388546d-f78e-e47f-5edc-eb0a78c3a27f@arm.com> (raw)
In-Reply-To: <DB6PR0802MB2198449A31AD8624B48045428C790@DB6PR0802MB2198.eurprd08.prod.outlook.com>
On 12/01/17 11:24, Mike Leach wrote:
> Hi Sudeep,
>
> I'm fine with that - less duplication the better.
>
> I've not played with .dts files much to I hadn't realised that type
> of construction was possible.
>
OK I spent some time and I think we can do the same for other coresight
components too. I will modify post the series but I need your help to
validate the change running core-sight tests.
--
Regards,
Sudeep
prev parent reply other threads:[~2017-01-12 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 20:44 [PATCH v2 0/2] arm64: dts: juno: Updates for juno r1/r2 boards Mike Leach
2017-01-11 20:44 ` [PATCH v2 1/2] arm64: dts: juno: Fix CoreSight support for Juno r1/r2 variants Mike Leach
2017-01-11 20:44 ` [PATCH v2 2/2] arm64: dts: juno: Adds missing CoreSight STM component Mike Leach
2017-01-12 11:14 ` Sudeep Holla
2017-01-12 11:24 ` Mike Leach
2017-01-12 12:11 ` Sudeep Holla [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=4388546d-f78e-e47f-5edc-eb0a78c3a27f@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).