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: Thu, 10 Jan 2013 17:49:13 +0530 [thread overview]
Message-ID: <50EEB1C1.9060306@ti.com> (raw)
In-Reply-To: <F3DBB1B3EF102E4994C89758CFCA32412B80CA@DBDE01.ent.ti.com>
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.
Thanks,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: Sekhar Nori <nsekhar@ti.com>
To: "Kumar, Anil" <anilkumar.v@ti.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
Kevin Hilman <khilman@deeprootsystems.com>,
"hs@denx.de" <hs@denx.de>
Subject: Re: [PATCH V2 3/3] ARM: davinci: da850: add NAND driver entries
Date: Thu, 10 Jan 2013 17:49:13 +0530 [thread overview]
Message-ID: <50EEB1C1.9060306@ti.com> (raw)
In-Reply-To: <F3DBB1B3EF102E4994C89758CFCA32412B80CA@DBDE01.ent.ti.com>
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.
Thanks,
Sekhar
next prev parent reply other threads:[~2013-01-10 12:19 UTC|newest]
Thread overview: 20+ 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 ` 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 ` 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 ` Kumar, Anil
2013-01-08 8:20 ` [PATCH V2 3/3] ARM: davinci: da850: add NAND driver entries Kumar, Anil
2013-01-08 8:20 ` Kumar, Anil
2013-01-09 12:47 ` Sekhar Nori
2013-01-09 12:47 ` Sekhar Nori
2013-01-10 7:37 ` Kumar, Anil
2013-01-10 7:37 ` Kumar, Anil
2013-01-10 12:19 ` Sekhar Nori [this message]
2013-01-10 12:19 ` Sekhar Nori
2013-01-15 10:36 ` Kumar, Anil
2013-01-15 10:36 ` Kumar, Anil
2013-01-15 11:11 ` Sekhar Nori
2013-01-15 11:11 ` Sekhar Nori
2013-01-17 10:30 ` Linus Walleij
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=50EEB1C1.9060306@ti.com \
--to=nsekhar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 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.