From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: s3x24xx: Fix gpiochip_add complaining.
Date: Fri, 19 Nov 2010 11:42:02 +0100 [thread overview]
Message-ID: <4CE6547A.9070309@metafoo.de> (raw)
In-Reply-To: <201011191123.22255.anarsoul@gmail.com>
Vasily Khoruzhick wrote:
> On Friday 19 November 2010 11:15:39 Marek Belisko wrote:
>> Make mini2440_defconfig. During kernel startup there is:
>> gpiochip_add: gpios 288..303 (GPIOK) failed to register
>> gpiochip_add: gpios 320..334 (GPIOL) failed to register
>> gpiochip_add: gpios 352..353 (GPIOM) failed to register
>>
>> because s3c2440 doesn't have following gpios. Gpios are
>> available only at upper cpu version (s3c2443).
>
> These warnings are harmless, and your patch prevents building single binary
> kernel for all s3c24xx socs (however, it's already broken by latest pull-
> up/pull-down changes)
>
> Regards
> Vasily
>
Hi
Well it actually causes problems on systems with external gpio expanders, because now
the additional banks will take up the space which was meant for the gpio expander
chip and peripherals connected to it wont be accessible.
I sent a patch[1] about this some time ago, but I guess it was never applied...
- Lars
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2010-September/026382.html
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2010-11-19 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 9:15 [PATCH] ARM: s3x24xx: Fix gpiochip_add complaining Marek Belisko
2010-11-19 9:23 ` Vasily Khoruzhick
2010-11-19 10:42 ` Lars-Peter Clausen [this message]
2010-11-19 10:53 ` Vasily Khoruzhick
2010-11-25 7:15 ` Kukjin Kim
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=4CE6547A.9070309@metafoo.de \
--to=lars@metafoo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).