From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: [RFC 1/3] pinctrl: add a driver for the OMAP pinmux Date: Fri, 25 Nov 2011 09:53:45 +0100 Message-ID: References: <1321274409-24643-2-git-send-email-rnayak@ti.com> <20111114172312.GI31337@atomide.com> <4EC1EB9D.1000503@ti.com> <20111122175409.GE31337@atomide.com> <20111124195452.GG13928@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <20111124195452.GG13928@atomide.com> Sender: linux-samsung-soc-owner@vger.kernel.org To: Tony Lindgren Cc: Thomas Abraham , Rajendra Nayak , linux-omap@vger.kernel.org, linaro-dev@lists.linaro.org, linus.walleij@stericsson.com, linux-samsung-soc , devicetree-discuss@lists.ozlabs.org List-Id: devicetree@vger.kernel.org On Thu, Nov 24, 2011 at 8:54 PM, Tony Lindgren wrote: > We should probably pass over > the static board specific mapping as platform_data to the pinmux device > and make it be part of struct pinctrl_dev. Then new driver instances > can have their own pctldev->mapping and we can support both platform_data > and device tree based drivers on the same system. That sounds like a real good idea and I think it'll work fine. You can use the map in mach-u300/core.c as guinea pig for refactoring if you like. I think that's the only map that's in-tree ftm. Thanks, Linus Walleij