From: "James Tai [戴志峰]" <james.tai@realtek.com>
To: Robin Murphy <robin.murphy@arm.com>,
"linux-realtek-soc@lists.infradead.org"
<linux-realtek-soc@lists.infradead.org>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Andreas Färber" <afaerber@suse.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v3 2/2] arm64: dts: realtek: Add RTD1319 SoC and Realtek PymParticle EVB
Date: Thu, 16 Apr 2020 15:00:19 +0000 [thread overview]
Message-ID: <635ba17aaf444d0c8f8f44af3e905c8e@realtek.com> (raw)
In-Reply-To: <05b02ba8-2959-48d8-be3f-c4a1a0bc88a4@arm.com>
Hi Robin,
> On 2020-02-04 2:52 pm, James Tai wrote:
> [...]
> > + arm_pmu: pmu {
> > + compatible = "arm,armv8-pmuv3";
>
> The binding updates have landed now, so you can use "arm,cortex-a55-pmu"
> here.
>
Okay. I'll modify it in v4.
Thank you.
Regards,
James
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-04-16 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 14:52 [PATCH v3 0/2] Initial RTD1319 SoC and Realtek PymParticle EVB support James Tai
2020-02-04 14:52 ` [PATCH v3 1/2] dt-bindings: arm: realtek: Document RTD1319 and Realtek PymParticle EVB James Tai
2020-02-05 16:47 ` Rob Herring
2020-02-07 2:53 ` James Tai [戴志峰]
2020-04-13 0:17 ` Andreas Färber
2020-04-15 8:58 ` James Tai [戴志峰]
2020-04-15 9:19 ` Andreas Färber
2020-02-04 14:52 ` [PATCH v3 2/2] arm64: dts: realtek: Add RTD1319 SoC " James Tai
2020-04-15 11:41 ` Andreas Färber
2020-04-16 8:47 ` James Tai [戴志峰]
2020-04-16 9:45 ` Robin Murphy
2020-04-16 15:00 ` James Tai [戴志峰] [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=635ba17aaf444d0c8f8f44af3e905c8e@realtek.com \
--to=james.tai@realtek.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@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).