From: Linus Walleij <linus.walleij@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Thomas Abraham <thomas.abraham@linaro.org>,
Rajendra Nayak <rnayak@ti.com>,
linux-omap@vger.kernel.org, linaro-dev@lists.linaro.org,
linus.walleij@stericsson.com,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [RFC 1/3] pinctrl: add a driver for the OMAP pinmux
Date: Fri, 25 Nov 2011 09:53:45 +0100 [thread overview]
Message-ID: <CACRpkdabC1Tf=bf-LV4_2XSOrWqU7sr_rrjXFaqv3GnKM54UGA@mail.gmail.com> (raw)
In-Reply-To: <20111124195452.GG13928@atomide.com>
On Thu, Nov 24, 2011 at 8:54 PM, Tony Lindgren <tony@atomide.com> 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
prev parent reply other threads:[~2011-11-25 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1321274409-24643-1-git-send-email-rnayak@ti.com>
[not found] ` <1321274409-24643-2-git-send-email-rnayak@ti.com>
[not found] ` <20111114172312.GI31337@atomide.com>
[not found] ` <4EC1EB9D.1000503@ti.com>
[not found] ` <CACRpkdYuw+AfVtgfsbpkd=uvfWd8yE-n25EC0FDffhiGUS2MBw@mail.gmail.com>
[not found] ` <CAJuYYwSgzkDed5-R=PaBR_F6ssj_EhxLDfCREXUA=UaynkgZyg@mail.gmail.com>
2011-11-17 13:57 ` [RFC 1/3] pinctrl: add a driver for the OMAP pinmux Linus Walleij
[not found] ` <CACRpkdbBQoOU8hyew6tXth3Ohrg5_rN7M+tbVsYFcOjgq73aCw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-22 11:09 ` Thomas Abraham
2011-11-22 12:05 ` Linus Walleij
2011-11-22 17:54 ` Tony Lindgren
2011-11-23 0:28 ` Stephen Warren
2011-11-23 10:14 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF174F08C5B3-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-11-24 10:09 ` Linus Walleij
2011-11-23 15:21 ` Koen Kooi
2011-11-24 5:07 ` Hiremath, Vaibhav
2011-11-24 10:04 ` Linus Walleij
2011-11-24 19:54 ` Tony Lindgren
2011-11-25 8:53 ` Linus Walleij [this message]
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='CACRpkdabC1Tf=bf-LV4_2XSOrWqU7sr_rrjXFaqv3GnKM54UGA@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=thomas.abraham@linaro.org \
--cc=tony@atomide.com \
/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).