All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"Nori, Sekhar" <nsekhar@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Hiremath, Vaibhav" <hvaibhav@ti.com>,
	"Hebbar, Gururaja" <gururaja.hebbar@ti.com>,
	"zonque@gmail.com" <zonque@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [v2, 3/3] ARM: dts: AM33XX: Add NAND flash device tree data to am335x-evm
Date: Thu, 30 May 2013 09:24:24 +0200	[thread overview]
Message-ID: <51A6FEA8.5030704@ti.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9C5629@DBDE04.ent.ti.com>

Hi Pekon,

On 05/20/2013 06:44 AM, Gupta, Pekon wrote:
>  
>>>>>
>>>>>  	am33xx_pinmux: pinmux@44e10800 {
>>>>>  		pinctrl-names = "default";
>>>>> -		pinctrl-0 = <&matrix_keypad_s0 &volume_keys_s0>;
>>>>> +		pinctrl-0 = <&matrix_keypad_s0 &volume_keys_s0
>>>>> +			&nandflash_pins_s0>;
>>>>
>>>> Why add this to the board level fallback (called pinctrl hogs, I think)?
>>>> This can be part of nand node you added below so that the pinctrl will
>>>> take effect when nand gets probed instead of all the time.
>>>
>>> Yes we should have all the pinctrl entries under the related drivers.
>>> This makes it easy remux pins during runtime if needed, and also
>>> allows unloading pinctrl-single.ko for development.
>>>
>> Yes, accepted. This has been already fixed in v3 of this patch set.
>> If all fine, then please pull this for next merge..
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046712.html
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046814.html
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046710.html
>>
>>
>> with regards, pekon
> 
> Request you to please accept | provide feedbacks on this patch series.
> These are waiting acceptance since Jan-2013, and are necessary for 
> DT based configs for board having NAND support.
> 
> with regards, pekon

Sorry, I missed that series.

I'm applying it right now.

Thanks,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: Benoit Cousson <b-cousson@ti.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"Nori, Sekhar" <nsekhar@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Hiremath, Vaibhav" <hvaibhav@ti.com>,
	"Hebbar, Gururaja" <gururaja.hebbar@ti.com>,
	"zonque@gmail.com" <zonque@gmail.com>,
	"Philip, Avinash" <avinashphilip@ti.com>,
	"jacmet@sunsite.dk" <jacmet@sunsite.dk>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [v2, 3/3] ARM: dts: AM33XX: Add NAND flash device tree data to am335x-evm
Date: Thu, 30 May 2013 09:24:24 +0200	[thread overview]
Message-ID: <51A6FEA8.5030704@ti.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9C5629@DBDE04.ent.ti.com>

Hi Pekon,

On 05/20/2013 06:44 AM, Gupta, Pekon wrote:
>  
>>>>>
>>>>>  	am33xx_pinmux: pinmux@44e10800 {
>>>>>  		pinctrl-names = "default";
>>>>> -		pinctrl-0 = <&matrix_keypad_s0 &volume_keys_s0>;
>>>>> +		pinctrl-0 = <&matrix_keypad_s0 &volume_keys_s0
>>>>> +			&nandflash_pins_s0>;
>>>>
>>>> Why add this to the board level fallback (called pinctrl hogs, I think)?
>>>> This can be part of nand node you added below so that the pinctrl will
>>>> take effect when nand gets probed instead of all the time.
>>>
>>> Yes we should have all the pinctrl entries under the related drivers.
>>> This makes it easy remux pins during runtime if needed, and also
>>> allows unloading pinctrl-single.ko for development.
>>>
>> Yes, accepted. This has been already fixed in v3 of this patch set.
>> If all fine, then please pull this for next merge..
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046712.html
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046814.html
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046710.html
>>
>>
>> with regards, pekon
> 
> Request you to please accept | provide feedbacks on this patch series.
> These are waiting acceptance since Jan-2013, and are necessary for 
> DT based configs for board having NAND support.
> 
> with regards, pekon

Sorry, I missed that series.

I'm applying it right now.

Thanks,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [v2, 3/3] ARM: dts: AM33XX: Add NAND flash device tree data to am335x-evm
Date: Thu, 30 May 2013 09:24:24 +0200	[thread overview]
Message-ID: <51A6FEA8.5030704@ti.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9C5629@DBDE04.ent.ti.com>

Hi Pekon,

On 05/20/2013 06:44 AM, Gupta, Pekon wrote:
>  
>>>>>
>>>>>  	am33xx_pinmux: pinmux at 44e10800 {
>>>>>  		pinctrl-names = "default";
>>>>> -		pinctrl-0 = <&matrix_keypad_s0 &volume_keys_s0>;
>>>>> +		pinctrl-0 = <&matrix_keypad_s0 &volume_keys_s0
>>>>> +			&nandflash_pins_s0>;
>>>>
>>>> Why add this to the board level fallback (called pinctrl hogs, I think)?
>>>> This can be part of nand node you added below so that the pinctrl will
>>>> take effect when nand gets probed instead of all the time.
>>>
>>> Yes we should have all the pinctrl entries under the related drivers.
>>> This makes it easy remux pins during runtime if needed, and also
>>> allows unloading pinctrl-single.ko for development.
>>>
>> Yes, accepted. This has been already fixed in v3 of this patch set.
>> If all fine, then please pull this for next merge..
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046712.html
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046814.html
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046710.html
>>
>>
>> with regards, pekon
> 
> Request you to please accept | provide feedbacks on this patch series.
> These are waiting acceptance since Jan-2013, and are necessary for 
> DT based configs for board having NAND support.
> 
> with regards, pekon

Sorry, I missed that series.

I'm applying it right now.

Thanks,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: Benoit Cousson <b-cousson@ti.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"Philip, Avinash" <avinashphilip@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org" 
	<devicetree-discuss@lists.ozlabs.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Hebbar, Gururaja" <gururaja.hebbar@ti.com>,
	"Hiremath, Vaibhav" <hvaibhav@ti.com>,
	"zonque@gmail.com" <zonque@gmail.com>,
	"jacmet@sunsite.dk" <jacmet@sunsite.dk>,
	"Nori, Sekhar" <nsekhar@ti.com>
Subject: Re: [v2, 3/3] ARM: dts: AM33XX: Add NAND flash device tree data to am335x-evm
Date: Thu, 30 May 2013 09:24:24 +0200	[thread overview]
Message-ID: <51A6FEA8.5030704@ti.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E9C5629@DBDE04.ent.ti.com>

Hi Pekon,

On 05/20/2013 06:44 AM, Gupta, Pekon wrote:
>  
>>>>>
>>>>>  	am33xx_pinmux: pinmux@44e10800 {
>>>>>  		pinctrl-names = "default";
>>>>> -		pinctrl-0 = <&matrix_keypad_s0 &volume_keys_s0>;
>>>>> +		pinctrl-0 = <&matrix_keypad_s0 &volume_keys_s0
>>>>> +			&nandflash_pins_s0>;
>>>>
>>>> Why add this to the board level fallback (called pinctrl hogs, I think)?
>>>> This can be part of nand node you added below so that the pinctrl will
>>>> take effect when nand gets probed instead of all the time.
>>>
>>> Yes we should have all the pinctrl entries under the related drivers.
>>> This makes it easy remux pins during runtime if needed, and also
>>> allows unloading pinctrl-single.ko for development.
>>>
>> Yes, accepted. This has been already fixed in v3 of this patch set.
>> If all fine, then please pull this for next merge..
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046712.html
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046814.html
>>
>> http://lists.infradead.org/pipermail/linux-mtd/2013-May/046710.html
>>
>>
>> with regards, pekon
> 
> Request you to please accept | provide feedbacks on this patch series.
> These are waiting acceptance since Jan-2013, and are necessary for 
> DT based configs for board having NAND support.
> 
> with regards, pekon

Sorry, I missed that series.

I'm applying it right now.

Thanks,
Benoit



  reply	other threads:[~2013-05-30  7:24 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  8:02 [PATCH v2 0/3] Add device tree support for NAND flash in am335x-evm Philip Avinash
2013-01-24  8:02 ` Philip Avinash
2013-01-24  8:02 ` Philip Avinash
     [not found] ` <cover.1359007746.git.avinashphilip-l0cyMroinI0@public.gmane.org>
2013-01-24  8:02   ` [PATCH v2 1/3] ARM: dts: AM33XX: Add ELM node Philip Avinash
2013-05-02  9:43     ` [PATCH v3,1/3] " Gupta, Pekon
2013-04-29  7:53     ` [v2,1/3] " Gupta, Pekon
2013-01-24  8:02     ` [PATCH v2 1/3] " Philip Avinash
2013-04-30  5:01     ` [v2,1/3] " Sekhar Nori
2013-04-30  5:01       ` Sekhar Nori
2013-04-30  5:01       ` Sekhar Nori
2013-04-30  5:01       ` Sekhar Nori
2013-01-24  8:02   ` [PATCH v2 2/3] ARM: dts: AM33XX: Add GPMC node Philip Avinash
2013-05-02  9:44     ` [PATCH v3,2/3] " Gupta, Pekon
2013-04-29  7:55     ` [v2,2/3] " Gupta, Pekon
2013-01-24  8:02     ` [PATCH v2 2/3] " Philip Avinash
2013-05-09  0:16     ` [PATCH v3,2/3] " Tony Lindgren
2013-05-09  0:16       ` Tony Lindgren
2013-05-09  0:16       ` Tony Lindgren
2013-05-09  0:16       ` Tony Lindgren
2013-01-24  8:02   ` [PATCH v2 3/3] ARM: dts: AM33XX: Add NAND flash device tree data to am335x-evm Philip Avinash
2013-04-29  7:55     ` [v2, " Gupta, Pekon
2013-04-29  7:55     ` Gupta, Pekon
2013-01-24  8:02     ` [PATCH v2 " Philip Avinash
2013-04-30  5:05     ` [v2, " Sekhar Nori
2013-04-30  5:05       ` Sekhar Nori
2013-04-30  5:05       ` Sekhar Nori
2013-04-30  5:05       ` Sekhar Nori
2013-05-08 23:54       ` Tony Lindgren
2013-05-08 23:54         ` Tony Lindgren
2013-05-08 23:54         ` Tony Lindgren
2013-05-09  4:12         ` Gupta, Pekon
2013-05-09  4:12           ` Gupta, Pekon
2013-05-09  4:12           ` Gupta, Pekon
2013-05-20  4:44           ` Gupta, Pekon
2013-05-20  4:44             ` Gupta, Pekon
2013-05-20  4:44             ` Gupta, Pekon
2013-05-30  7:24             ` Benoit Cousson [this message]
2013-05-30  7:24               ` Benoit Cousson
2013-05-30  7:24               ` Benoit Cousson
2013-05-30  7:24               ` Benoit Cousson
2013-05-30  7:31               ` Gupta, Pekon
2013-05-30  7:31                 ` Gupta, Pekon
2013-05-30  7:31                 ` Gupta, Pekon
2013-05-30  7:31                 ` Gupta, Pekon
2013-05-30  7:36                 ` Gupta, Pekon
2013-05-30  7:36                   ` Gupta, Pekon
2013-05-30  7:36                   ` Gupta, Pekon
2013-05-30  7:39                 ` Benoit Cousson
2013-05-30  7:39                   ` Benoit Cousson
2013-05-30  7:39                   ` Benoit Cousson
2013-05-30  7:39                   ` Benoit Cousson
2013-01-31  9:36   ` [PATCH v2 0/3] Add device tree support for NAND flash in am335x-evm Philip, Avinash
2013-01-31  9:36     ` Philip, Avinash
2013-01-31  9:36     ` Philip, Avinash

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=51A6FEA8.5030704@ti.com \
    --to=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=gururaja.hebbar@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nsekhar@ti.com \
    --cc=pekon@ti.com \
    --cc=tony@atomide.com \
    --cc=zonque@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.