public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel•com (Nicolas Ferre)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 2/2] arm: at91: dt: at91sam9x5: add i2c-gpio pinctrl
Date: Wed, 13 Mar 2013 11:29:13 +0100	[thread overview]
Message-ID: <514054F9.9060700@atmel.com> (raw)
In-Reply-To: <20130313102507.GB9249@ludovic.desroches@atmel.com>

On 03/13/2013 11:25 AM, Ludovic Desroches :
> On Tue, Mar 12, 2013 at 05:54:46PM +0100, Richard Genoud wrote:
>> i2c-gpio is sometimes used in place of i2c-at91.
>> This adds the pin muxes for the gpios.
>>
>> Signed-off-by: Richard Genoud <richard.genoud@gmail•com>
> 
> Since i2c-gpio nodes are already in the a91sam9x5 why not adding pin muxes.
> If not, we should remove these nodes but I think it is quite convenient to keep them in order to easily switch from i2c-at91 to i2c-gpio for debug purpose or others.
> 
> Acked-by: Ludovic Desroches <ludovic.desroches@atmel•com>

Agreed, queued to at91-3.10-dt branch.

Thanks.

>> ---
>>  based on v3.9-rc2
>>
>>  arch/arm/boot/dts/at91sam9x5.dtsi |   30 ++++++++++++++++++++++++++++++
>>  1 files changed, 30 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/at91sam9x5.dtsi b/arch/arm/boot/dts/at91sam9x5.dtsi
>> index 8cbcff4..d18aff5 100644
>> --- a/arch/arm/boot/dts/at91sam9x5.dtsi
>> +++ b/arch/arm/boot/dts/at91sam9x5.dtsi
>> @@ -343,6 +343,30 @@
>>  					};
>>  				};
>>  
>> +				i2c_gpio0 {
>> +					pinctrl_i2c_gpio0: i2c_gpio0-0 {
>> +						atmel,pins =
>> +							<0 30 0x0 0x2	/* PA30 gpio multidrive I2C0 data */
>> +							 0 31 0x0 0x2>;	/* PA31 gpio multidrive I2C0 clock */
>> +					};
>> +				};
>> +
>> +				i2c_gpio1 {
>> +					pinctrl_i2c_gpio1: i2c_gpio1-0 {
>> +						atmel,pins =
>> +							<2 0 0x0 0x2	/* PC0 gpio multidrive I2C1 data */
>> +							 2 1 0x0 0x2>;	/* PC1 gpio multidrive I2C1 clock */
>> +					};
>> +				};
>> +
>> +				i2c_gpio2 {
>> +					pinctrl_i2c_gpio2: i2c_gpio2-0 {
>> +						atmel,pins =
>> +							<1 4 0x0 0x2	/* PB4 gpio multidrive I2C2 data */
>> +							 1 5 0x0 0x2>;	/* PB5 gpio multidrive I2C2 clock */
>> +					};
>> +				};
>> +
>>  				pioA: gpio at fffff400 {
>>  					compatible = "atmel,at91sam9x5-gpio", "atmel,at91rm9200-gpio";
>>  					reg = <0xfffff400 0x200>;
>> @@ -583,6 +607,8 @@
>>  		i2c-gpio,delay-us = <2>;	/* ~100 kHz */
>>  		#address-cells = <1>;
>>  		#size-cells = <0>;
>> +		pinctrl-names = "default";
>> +		pinctrl-0 = <&pinctrl_i2c_gpio0>;
>>  		status = "disabled";
>>  	};
>>  
>> @@ -596,6 +622,8 @@
>>  		i2c-gpio,delay-us = <2>;	/* ~100 kHz */
>>  		#address-cells = <1>;
>>  		#size-cells = <0>;
>> +		pinctrl-names = "default";
>> +		pinctrl-0 = <&pinctrl_i2c_gpio1>;
>>  		status = "disabled";
>>  	};
>>  
>> @@ -609,6 +637,8 @@
>>  		i2c-gpio,delay-us = <2>;	/* ~100 kHz */
>>  		#address-cells = <1>;
>>  		#size-cells = <0>;
>> +		pinctrl-names = "default";
>> +		pinctrl-0 = <&pinctrl_i2c_gpio2>;
>>  		status = "disabled";
>>  	};
>>  };
>> -- 
>> 1.7.2.5
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 
> 


-- 
Nicolas Ferre

  reply	other threads:[~2013-03-13 10:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 16:54 [PATCH 1/2] arm: at91: dt: at91sam9x5: add i2c pinctrl Richard Genoud
2013-03-12 16:54 ` [PATCH 2/2] arm: at91: dt: at91sam9x5: add i2c-gpio pinctrl Richard Genoud
2013-03-12 16:54   ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-13 10:25   ` Ludovic Desroches
2013-03-13 10:29     ` Nicolas Ferre [this message]
2013-03-13 10:07 ` [PATCH 1/2] arm: at91: dt: at91sam9x5: add i2c pinctrl Ludovic Desroches
2013-03-13 10:29   ` Nicolas Ferre

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=514054F9.9060700@atmel.com \
    --to=nicolas.ferre@atmel$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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