[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201109231848.52318.arnd@arndb.de>
Date: Fri, 23 Sep 2011 18:48:52 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Stephen Warren <swarren@...dia.com>
Cc: Russell King <linux@....linux.org.uk>,
Nicolas Pitre <nico@...xnic.net>,
Olof Johansson <olof@...om.net>,
Colin Cross <ccross@...roid.com>,
Erik Gilling <konkers@...roid.com>,
Grant Likely <grant.likely@...retlab.ca>,
Peter De Schrijver <pdeschrijver@...dia.com>,
linux-tegra@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] arm/tegra: Convert gpio & pinmux to platform devices
On Thursday 22 September 2011, Stephen Warren wrote:
>
> This series converts the Tegra GPIO and pinmux drivers to be regular
> platform devices.
Looks good overall.
> The series is extracted from an earlier series I posted that augmented
> these drivers to initialize HW state from the device-tree. I'm holding
> off on that aspect of the changes, since it's not entirely clear to me
> whether the new pinmux API should drive the initial pinmux state setup
> via "system hog" definitions, or whether pinmux drivers should indeed
> do their own thing.
I think at least you should try to do an ioremap of the pinmux register
area in the pinmux probe function and make sure that it's called early
enough, if at all possible.
Right now, there is an empty probe() function, which is a bit silly,
and the pg_readl()/pg_writel() functions use hardcoded register
addresses.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists