devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Chris Paterson <chris.paterson2@renesas.com>,
	devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH  1/2] ARM: dts: iwg20d-q7: Add RTC support
Date: Wed, 9 Aug 2017 11:02:30 +0200	[thread overview]
Message-ID: <20170809090230.GM2705@verge.net.au> (raw)
In-Reply-To: <1502197465-61546-2-git-send-email-biju.das@bp.renesas.com>

On Tue, Aug 08, 2017 at 02:04:24PM +0100, Biju Das wrote:
> Define the iWave RainboW-G20D-Qseven board dependent part of the
> RTC device node.
> 
> Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> ---
>  arch/arm/boot/dts/r8a7743-iwg20d-q7.dts | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)

This has a compile-time dependency on
"[PATCH  2/2] ARM: dts: r8a7743: Add I2C DT support"
for the i2c2 node, right?

> 
> diff --git a/arch/arm/boot/dts/r8a7743-iwg20d-q7.dts b/arch/arm/boot/dts/r8a7743-iwg20d-q7.dts
> index 081af01..b3a1efa 100644
> --- a/arch/arm/boot/dts/r8a7743-iwg20d-q7.dts
> +++ b/arch/arm/boot/dts/r8a7743-iwg20d-q7.dts
> @@ -31,6 +31,11 @@
>  		groups = "avb_mdio", "avb_gmii";
>  		function = "avb";
>  	};
> +
> +	i2c2_pins: i2c2 {
> +		groups = "i2c2";
> +		function = "i2c2";
> +	};
>  };
>  
>  &scif0 {
> @@ -54,3 +59,16 @@
>  		micrel,led-mode = <1>;
>  	};
>  };
> +
> +&i2c2 {
> +	pinctrl-0 = <&i2c2_pins>;
> +	pinctrl-names = "default";
> +
> +	status = "okay";
> +	clock-frequency = <400000>;
> +
> +	rtc@68 {
> +		compatible = "bq32000";
> +		reg = <0x68>;
> +	};
> +};
> -- 
> 1.9.1
> 

  reply	other threads:[~2017-08-09  9:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 13:04 [PATCH 0/2] Add BQ32000 RTC support for iWave RZ/G1M board Biju Das
2017-08-08 13:04 ` [PATCH 1/2] ARM: dts: iwg20d-q7: Add RTC support Biju Das
2017-08-09  9:02   ` Simon Horman [this message]
2017-08-14  5:38     ` Simon Horman
2017-08-14 14:11   ` Geert Uytterhoeven
     [not found]     ` <CAMuHMdUU5fb6G7Wc9ZzfFhLxcUuZFakPdVGh3q_cfUzxZ1AarA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-08-14 14:26       ` Biju Das
     [not found]         ` <KL1PR06MB1702571F2F9B75205A11280AB88C0-k6wCOA2IOKSx7cDWSRonpW0DtJ1/0DrXvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-08-15 15:45           ` Simon Horman
2017-08-08 13:04 ` [PATCH 2/2] ARM: shmobile: Enable BQ32000 rtc in shmobile_defconfig Biju Das
     [not found]   ` <1502197465-61546-3-git-send-email-biju.das-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-08-09  9:04     ` Simon Horman
2017-08-17  9:01       ` Simon Horman
2017-08-17  9:04         ` Biju Das

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=20170809090230.GM2705@verge.net.au \
    --to=horms@verge.net.au \
    --cc=biju.das@bp.renesas.com \
    --cc=chris.paterson2@renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.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).