From: dirk.behme@de.bosch.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: i.MX6: set ARCH_NR_GPIO to 244
Date: Mon, 30 Jul 2012 08:40:58 +0200 [thread overview]
Message-ID: <50162C7A.1060307@de.bosch.com> (raw)
In-Reply-To: <20120730011426.GB30774@S2101-09.ap.freescale.net>
On 30.07.2012 03:14, Shawn Guo wrote:
> On Sun, Jul 29, 2012 at 06:18:21PM +0200, Dirk Behme wrote:
>> Hmm, sorry if I missed anything, but how is adding a 'default ..
>> SOC_IMX6Q' related to any defconfig? If you want to deselect
>> SOC_IMX6Q using the way you like you'll get the standard 256 (if I
>> remember correctly).
>>
> I'm essentially questioning about the point of the patch. It intends
> to save a little space for imx6q build without caring about imx3 and
> imx5. That said, when imx6q is excluded from the build, we are still
> wasting those space.
It's my understanding that the ARCH_NR_GPIO Kconfig was introduced
recently for optimization/conversion/cleanup reasons. So from my point
of view it's in a first step better to use it for iMX6 than ignoring
this optimization/conversion/cleanup.
But yes, it's even better to enable it for imx3/imx5, too. As I don't
know these platforms, two questions:
- Do you like to propose a better macro than SOC_IMX6Q to cover
imx3/imx6, too?
- Do imx3 and imx5 have the same GPIO number like imx6? I.e. 7 banks
with 32 pins == 224 GPIOs?
> Looking at current users of this definition, you will find all of them
> are defining a number bigger than 256 for extending the maximum number.
> It might be a sign that having a gpio array which is a little bigger
> than necessary is not a concern on machines today.
Or it might be a sign that they *have* more than 256? I don't know. But
what's the issue using a matching number if possible?
Best regards
Dirk
next prev parent reply other threads:[~2012-07-30 6:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 12:37 [PATCH 1/2] ARM: i.MX6: set ARCH_NR_GPIO to 244 Dirk Behme
2012-07-25 12:37 ` [PATCH 2/2] ARM: dts: imx6q: Invert the GPIO controller order Dirk Behme
2012-07-28 13:41 ` Shawn Guo
2012-07-30 7:28 ` Thomae Matthias (CM-AI/PJ-CF31)
2012-07-30 9:01 ` Shawn Guo
2012-07-30 14:24 ` Russell King - ARM Linux
2012-07-31 8:15 ` Dirk Behme
2012-07-25 14:12 ` [PATCH 1/2] ARM: i.MX6: set ARCH_NR_GPIO to 244 Fabio Estevam
2012-07-25 14:51 ` Dirk Behme
2012-07-28 13:32 ` Shawn Guo
2012-07-29 16:18 ` Dirk Behme
2012-07-30 1:14 ` Shawn Guo
2012-07-30 6:40 ` Dirk Behme [this message]
2012-07-30 8:46 ` Shawn Guo
2012-07-30 11:14 ` Dirk Behme
2012-07-30 14:29 ` Russell King - ARM Linux
2012-07-31 1:16 ` Shawn Guo
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=50162C7A.1060307@de.bosch.com \
--to=dirk.behme@de.bosch.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.