From: nsekhar@ti•com (Sekhar Nori)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V2 3/3] ARM: davinci: da850: add NAND driver entries
Date: Tue, 15 Jan 2013 16:41:53 +0530 [thread overview]
Message-ID: <50F53979.4050509@ti.com> (raw)
In-Reply-To: <F3DBB1B3EF102E4994C89758CFCA32412B96F9@DBDE01.ent.ti.com>
On 1/15/2013 4:06 PM, Kumar, Anil wrote:
> On Thu, Jan 10, 2013 at 17:49:13, Nori, Sekhar wrote:
>> On 1/10/2013 1:07 PM, Kumar, Anil wrote:
>>> On Wed, Jan 09, 2013 at 18:17:46, Nori, Sekhar wrote:
>>
>>> I do not think that it is good idea to move NAND pin mux information
>>> into da850.dtsi because this information is evm specific.
>>> if we will use this approach then we must use the same approach for
>>> other modules also as ASoC etc.
>>
>> Why do you consider this EVM specific. IOW, which pins do you see
>> changing on another board? BTW, if there are additional pins needed than
>> what are listed, we can always add more pinux entries in the .dts files.
>> The pins present in dtsi file should the base case.
>
> Ok, we can use this approach for DaVinci as its SoC modules do not
> have multiple pin configuration option. I will do the changes in
> next patch series.
You could do this even if this was the case by defining multiple pin groups.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-01-15 11:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 8:20 [PATCH V2 0/3] ARM: davinci: da850: add pinctrl support Kumar, Anil
2013-01-08 8:20 ` [PATCH V2 1/3] ARM: davinci: da850: add pinctrl driver entries Kumar, Anil
2013-01-08 8:20 ` [PATCH V2 2/3] ARM: davinci: da8xx defconfig: enable pinctrl config option Kumar, Anil
2013-01-08 8:20 ` [PATCH V2 3/3] ARM: davinci: da850: add NAND driver entries Kumar, Anil
2013-01-09 12:47 ` Sekhar Nori
2013-01-10 7:37 ` Kumar, Anil
2013-01-10 12:19 ` Sekhar Nori
2013-01-15 10:36 ` Kumar, Anil
2013-01-15 11:11 ` Sekhar Nori [this message]
2013-01-17 10:30 ` Linus Walleij
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=50F53979.4050509@ti.com \
--to=nsekhar@ti$(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