From: Hanumant Singh <hanumant@codeaurora.org>
To: Josh Cartwright <joshc@codeaurora.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bjorn Andersson <bjorn@kryo.se>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] pinctrl: msm: Add support for MSM TLMM pinmux
Date: Thu, 15 Aug 2013 14:58:31 -0700 [thread overview]
Message-ID: <520D4F07.8000609@codeaurora.org> (raw)
In-Reply-To: <20130815215004.GC4035@joshc.qualcomm.com>
On 8/15/2013 2:50 PM, Josh Cartwright wrote:
> On Thu, Aug 15, 2013 at 10:44:03AM -0700, Hanumant Singh wrote:
>> On 8/14/2013 12:29 PM, Linus Walleij wrote:
>>> On Tue, Jul 30, 2013 at 1:39 AM, Bjorn Andersson <bjorn@kryo.se> wrote:
>>>> On Wed, Jul 24, 2013 at 1:41 PM, Hanumant Singh <hanumant@codeaurora.org> wrote:
>>>
>>>> As a general note on the patch, the pins and pin groups are defined by
>>>> the soc, I'm therefore not convinced that these should be configured
>>> >from the devicetree. It's at least not how it's done in other
>>>> platforms.
>>>
>>> Now we are three people sayin the same thing so it should
>>> be a good hint to the implementer :-)
>>>
>>
>> Ok i can switch to using pin groups defined in per soc files.
>> But in our case we have one soc going into different types of boards.
>> (atleast 3). In each of the boards the same external devices end up using
>> different pins. For ex camera on board 1 uses different pin group
>> then the same camera on board 2. Both having the same SOC.
>> So in this case the design would be to have all possible pin groups
>> for different boards enumerated in the same soc-pinctrl.c file?
>>
>> Also in this implementation I will have.
>> 1) pinctrl-msm.c => DT parsing and interface to framework.
>> 2) pinctrl-msm-tlmm<version>.c => Register programming and pin types
>> supported by a particular TLMM pinmux version.
>
> It isn't clear to me what you are trying to separate out between 1) and
> 2). Seems like there should only be pinctrl-msm-tlmm<version>.c.
>
The idea is that we should be able to plug in the next TLMM version 4,
with the pintypes that it supports and its register programming
semantics without any changes to the DT parsing or interface to the
framework. The DT information describes the states of the pingroups.
How we handle them with respect to the pinctrl framework, does not
change with different versions of the TLMM.
Thanks
Hanumant
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
next prev parent reply other threads:[~2013-08-15 21:58 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
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 [this message]
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=520D4F07.8000609@codeaurora.org \
--to=hanumant@codeaurora.org \
--cc=bjorn@kryo.se \
--cc=joshc@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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