From: Stephen Warren <swarren@wwwdotorg.org>
To: hanumant <hanumant@codeaurora.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Andersson <Bjorn.Andersson@sonymobile.com>,
"Bird, Tim" <Tim.Bird@sonymobile.com>,
ext Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] pinctrl: msm: Add support for MSM TLMM pinmux
Date: Tue, 30 Jul 2013 15:22:39 -0600 [thread overview]
Message-ID: <51F82E9F.9010309@wwwdotorg.org> (raw)
In-Reply-To: <51F82BCC.1080409@codeaurora.org>
On 07/30/2013 03:10 PM, hanumant wrote:
...
> We actually have the same TLMM pinmux used by several socs of a family.
> The number of pins on each soc may vary.
> Also a given soc gets used in a number of boards.
> The device tree for a given soc is split into the different boards that
> its in ie the boards inherit a common soc.dtsi but have separate dts.
> The boards for the same soc may use different pin groups for
> accomplishing a function, since we have multiple i2c, spi uart etc
> peripheral instances on a soc. A different instance of each of the above
> peripherals, can be used in different boards, utilizing different
> or subset of same pin groups.
> Thus I would need to have multiple C files for one soc, based on the
> boards that it goes into.
The pinctrl driver should be exposing the raw capabilities of the HW.
All the board-specific configuration should be expressed in DT. So, the
driver shouldn't have to know anything about different boards at
compile-time.
next prev parent reply other threads:[~2013-07-30 21:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 21:41 [PATCH] pinctrl: msm: Add support for MSM TLMM pinmux Hanumant Singh
2013-07-29 16:37 ` Linus Walleij
2013-07-29 17:32 ` Stephen Warren
2013-07-30 21:10 ` hanumant
2013-07-30 21:22 ` Stephen Warren [this message]
2013-07-31 0:01 ` Hanumant Singh
2013-07-31 0:08 ` Stephen Warren
2013-07-31 0:13 ` Hanumant Singh
2013-07-31 3:59 ` Stephen Warren
2013-07-31 19:46 ` Hanumant Singh
2013-07-31 21:06 ` Stephen Warren
2013-08-01 0:17 ` Hanumant Singh
2013-08-06 23:45 ` Hanumant Singh
2013-08-07 16:00 ` Stephen Warren
2013-08-14 19:16 ` Linus Walleij
2013-07-29 23:39 ` Bjorn Andersson
2013-08-07 18:07 ` Hanumant Singh
2013-08-14 19:29 ` Linus Walleij
2013-08-15 17:44 ` Hanumant Singh
2013-08-15 20:47 ` Linus Walleij
2013-08-15 21:28 ` Hanumant Singh
2013-08-28 8:32 ` Linus Walleij
2013-08-15 21:50 ` Josh Cartwright
2013-08-15 21:58 ` Hanumant Singh
2013-08-15 23:10 ` Josh Cartwright
2013-08-15 23:14 ` Hanumant Singh
-- strict thread matches above, loose matches on Subject: below --
2013-06-21 21:52 Hanumant Singh
2013-06-24 12:18 ` Linus Walleij
2013-06-25 17:41 ` hanumant
2013-06-27 8:26 ` Linus Walleij
2013-06-27 15:17 ` hanumant
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=51F82E9F.9010309@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=Tim.Bird@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=hanumant@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.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