From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: s3x24xx: Fix gpiochip_add complaining.
Date: Fri, 19 Nov 2010 12:53:58 +0200 [thread overview]
Message-ID: <201011191253.58812.anarsoul@gmail.com> (raw)
In-Reply-To: <4CE6547A.9070309@metafoo.de>
On Friday 19 November 2010 12:42:02 Lars-Peter Clausen wrote:
> 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.
Ok, but it would be nice to see some runtime soc-type detection for gpiolib.
s3c2410/s3c2440/s3c2442 doesn't differ too much (actually, they're same in
gpiopart, s3c2410 lacks some gpiobanks that s3c244[0,2] have, and difference
in pull-up/pull-down on s3c2440 and s3c2442).
I think it's not good to make artificial restrictions for building single
binary kernel for these socs.
> I sent a patch[1] about this some time ago, but I guess it was never
> applied...
Try pinging Ben or Kukjin :)
Regards
Vasily
WARNING: multiple messages have this Message-ID (diff)
From: Vasily Khoruzhick <anarsoul@gmail.com>
To: "Lars-Peter Clausen" <lars@metafoo.de>
Cc: linux-arm-kernel@lists.infradead.org,
Kukjin Kim <kgene.kim@samsung.com>,
Ben Dooks <ben-linux@fluff.org>,
Marek Belisko <marek.belisko@open-nandra.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: s3x24xx: Fix gpiochip_add complaining.
Date: Fri, 19 Nov 2010 12:53:58 +0200 [thread overview]
Message-ID: <201011191253.58812.anarsoul@gmail.com> (raw)
In-Reply-To: <4CE6547A.9070309@metafoo.de>
On Friday 19 November 2010 12:42:02 Lars-Peter Clausen wrote:
> 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.
Ok, but it would be nice to see some runtime soc-type detection for gpiolib.
s3c2410/s3c2440/s3c2442 doesn't differ too much (actually, they're same in
gpiopart, s3c2410 lacks some gpiobanks that s3c244[0,2] have, and difference
in pull-up/pull-down on s3c2440 and s3c2442).
I think it's not good to make artificial restrictions for building single
binary kernel for these socs.
> I sent a patch[1] about this some time ago, but I guess it was never
> applied...
Try pinging Ben or Kukjin :)
Regards
Vasily
next prev parent reply other threads:[~2010-11-19 10:53 UTC|newest]
Thread overview: 8+ 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
2010-11-19 10:42 ` Lars-Peter Clausen
2010-11-19 10:53 ` Vasily Khoruzhick [this message]
2010-11-19 10:53 ` Vasily Khoruzhick
2010-11-25 7:15 ` Kukjin Kim
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=201011191253.58812.anarsoul@gmail.com \
--to=anarsoul@gmail.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.