public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Matt Ranostay <mranostay@gmail.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux@arm.linux.org.uk,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, pantelis.antoniou@gmail.com,
	matt.porter@linaro.org
Subject: Re: [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition
Date: Mon, 12 May 2014 12:50:50 -0700	[thread overview]
Message-ID: <20140512195050.GB5668@atomide.com> (raw)
In-Reply-To: <1399686184-1594-1-git-send-email-mranostay@gmail.com>

* Matt Ranostay <mranostay@gmail.com> [140509 18:43]:
> Add missing i2c2 bus define to access various cape and
> prototype/breakout board devices.
> 
> Signed-off-by: Matt Ranostay <mranostay@gmail.com>
> ---
>  arch/arm/boot/dts/am335x-bone-common.dtsi | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/am335x-bone-common.dtsi b/arch/arm/boot/dts/am335x-bone-common.dtsi
> index 2e7d932..5fdae2e 100644
> --- a/arch/arm/boot/dts/am335x-bone-common.dtsi
> +++ b/arch/arm/boot/dts/am335x-bone-common.dtsi
> @@ -84,6 +84,13 @@
>  		>;
>  	};
>  
> +	i2c2_pins: pinmux_i2c2_pins {
> +		pinctrl-single,pins = <
> +			0x178 (PIN_INPUT_PULLUP | MUX_MODE3)	/* uart1_ctsn.i2c2_sda */
> +			0x17c (PIN_INPUT_PULLUP | MUX_MODE3)	/* uart1_rtsn.i2c2_scl */
> +		>;
> +	};
> +
>  	uart0_pins: pinmux_uart0_pins {
>  		pinctrl-single,pins = <
>  			0x170 (PIN_INPUT_PULLUP | MUX_MODE0)	/* uart0_rxd.uart0_rxd */
>
> @@ -222,6 +229,15 @@
>  
>  };
>  
> +
> +&i2c2 {
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&i2c2_pins>;
> +
> +	status = "okay";
> +	clock-frequency = <100000>;
> +};
> +

If these pins are not used for i2c2 on some capes, this device
should be set to status = "disabled" state by default. Then
u-boot could re-enable it on the boards that have i2c2 in use.

Regards,

Tony

  reply	other threads:[~2014-05-12 19:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-10  1:43 [PATCH v2] ARM: dts: am335x-bone-common: Add i2c2 definition Matt Ranostay
2014-05-12 19:50 ` Tony Lindgren [this message]
2014-05-12 19:59   ` Robert Nelson
2014-05-12 20:15     ` Tony Lindgren
2014-05-12 20:27       ` Robert Nelson
2014-05-12 20:42         ` Tony Lindgren
2014-05-12 20:57           ` Robert Nelson
2014-05-12 21:07             ` Tony Lindgren
2014-05-13 12:53             ` Tom Rini
2014-05-13 14:06               ` Javier Martinez Canillas
2014-05-13 14:13                 ` Tom Rini
2014-05-13 14:22                 ` Matt Porter
2014-05-13 14:39                   ` Javier Martinez Canillas
2014-05-13 17:07                     ` Pantelis Antoniou
2014-05-13 17:51                       ` Javier Martinez Canillas
2014-05-13 20:24                         ` John Syn
2014-05-14  3:39                           ` Pantelis Antoniou
2014-05-14  5:44                             ` John Syn
2014-05-14  7:12                               ` Javier Martinez Canillas
2014-05-14  3:24                         ` Pantelis Antoniou

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=20140512195050.GB5668@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=matt.porter@linaro.org \
    --cc=mranostay@gmail.com \
    --cc=pantelis.antoniou@gmail.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