linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: EXYNOS: add support GPIO for EXYNOS5250
Date: Thu, 2 Feb 2012 11:27:26 -0700	[thread overview]
Message-ID: <20120202182726.GO15343@ponder.secretlab.ca> (raw)
In-Reply-To: <20120131224043.GD8338@n2100.arm.linux.org.uk>

On Tue, Jan 31, 2012 at 10:40:43PM +0000, Russell King - ARM Linux wrote:
> On Wed, Feb 01, 2012 at 12:50:39AM +0900, Kukjin Kim wrote:
> > From: Sangsu Park <sangsu4u.park@samsung.com>
> > 
> > This patch adds follwing.
> > - IO-map for EXYNOS5250 GPIO support
> > - EXYNOS5250 GPIO bank size/number definitions
> > - memory map definition for S5P GPIO4
> > 
> > Signed-off-by: Sangsu Park <sangsu4u.park@samsung.com>
> > Signed-off-by: Kukjin Kim <kgene.kim@samsung.com>
> 
> Do you actually need these static mapping definitions?  The samsung
> gpiolib initialization is called from a core_initcall(), and at this
> time ioremap() is fully capable of working.

Indeed.  Please get rid of the S5P_VA_GPIO* macros and use ioremap to
set up the registers mappings.  I understand that the existing code
already does that, but I don't want to see any more added.  Also, it
is easy to fix by adding the ioremap calls to samsung_gpio_init()

g.

  parent reply	other threads:[~2012-02-02 18:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31 15:50 [PATCH 0/2] ARM: EXYNOS: support GPIO for EXYNOS5250 Kukjin Kim
2012-01-31 15:50 ` [PATCH 1/2] ARM: EXYNOS: add " Kukjin Kim
2012-01-31 16:34   ` Sylwester Nawrocki
2012-02-02 18:22     ` Grant Likely
2012-02-04 13:46       ` Sylwester Nawrocki
2012-01-31 22:40   ` Russell King - ARM Linux
2012-01-31 23:56     ` Kyungmin Park
2012-02-09 11:48       ` Kukjin Kim
2012-02-02 18:27     ` Grant Likely [this message]
2012-02-09 11:44       ` Kukjin Kim
2012-01-31 15:50 ` [PATCH 2/2] gpio/samsung: add support GPIOlib " 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=20120202182726.GO15343@ponder.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --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).