From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: shmobile: r8a7778: Add SoC-specific TMU compatible property
Date: Mon, 27 Oct 2014 09:27:48 +0900 [thread overview]
Message-ID: <20141027002747.GL25692@verge.net.au> (raw)
In-Reply-To: <1414150563-6645-2-git-send-email-geert+renesas@glider.be>
On Fri, Oct 24, 2014 at 01:36:03PM +0200, Geert Uytterhoeven wrote:
> The TMU timers used the generic compatible property only.
> Add the SoC-specific one, to make it future proof.
Thanks, I have queued this up.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> arch/arm/boot/dts/r8a7778.dtsi | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/boot/dts/r8a7778.dtsi b/arch/arm/boot/dts/r8a7778.dtsi
> index 1e80e4c694828e15..96297f67fda8e632 100644
> --- a/arch/arm/boot/dts/r8a7778.dtsi
> +++ b/arch/arm/boot/dts/r8a7778.dtsi
> @@ -163,7 +163,7 @@
> };
>
> tmu0: timer@ffd80000 {
> - compatible = "renesas,tmu";
> + compatible = "renesas,tmu-r8a7778", "renesas,tmu";
> reg = <0xffd80000 0x30>;
> interrupts = <0 32 IRQ_TYPE_LEVEL_HIGH>,
> <0 33 IRQ_TYPE_LEVEL_HIGH>,
> @@ -175,7 +175,7 @@
> };
>
> tmu1: timer@ffd81000 {
> - compatible = "renesas,tmu";
> + compatible = "renesas,tmu-r8a7778", "renesas,tmu";
> reg = <0xffd81000 0x30>;
> interrupts = <0 36 IRQ_TYPE_LEVEL_HIGH>,
> <0 37 IRQ_TYPE_LEVEL_HIGH>,
> @@ -187,7 +187,7 @@
> };
>
> tmu2: timer@ffd82000 {
> - compatible = "renesas,tmu";
> + compatible = "renesas,tmu-r8a7778", "renesas,tmu";
> reg = <0xffd82000 0x30>;
> interrupts = <0 40 IRQ_TYPE_LEVEL_HIGH>,
> <0 41 IRQ_TYPE_LEVEL_HIGH>,
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-10-27 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 11:36 [PATCH 1/2] ARM: shmobile: r8a73a4: Add SoC-specific CMT compatible property Geert Uytterhoeven
2014-10-24 11:36 ` [PATCH 2/2] ARM: shmobile: r8a7778: Add SoC-specific TMU " Geert Uytterhoeven
2014-10-27 0:27 ` Simon Horman [this message]
2014-10-27 0:27 ` [PATCH 1/2] ARM: shmobile: r8a73a4: Add SoC-specific CMT " Simon Horman
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=20141027002747.GL25692@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).