From: hanumant <hanumant@codeaurora.org>
To: "Bird, Tim" <Tim.Bird@sonymobile.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"\"Andersson, Björn\"" <Bjorn.Andersson@sonymobile.com>,
"David Brown" <davidb@codeaurora.org>
Subject: Re: pinctrl and device-tree support in qcom drivers
Date: Fri, 26 Jul 2013 10:30:09 -0700 [thread overview]
Message-ID: <51F2B221.5000806@codeaurora.org> (raw)
In-Reply-To: <E12ED16DF2DF754897A674F2B0E8F6C446AFF250CA@seldmbx01.corpusers.net>
On 7/25/2013 3:56 PM, Bird, Tim wrote:
>
> I don't think there's anything tricky here. I'm willing to
> do some legwork to get the i2c-qup driver working with
> device tree. Right now it does a lot of pin handling internally
> itself (I believe it brings up the needed gpios, functions, etc.
> from boot state).
>
> My question is whether I should just do that, or if the pinctrl
> support for these pins is required first, in order to mainline the
> Sony vibrator driver.
David can advise on the i2c-qup driver support from Qualcomm.
But when that does happen it will use the pinctrl framework to manage
the i2c bus lines.
I will try to push through the pinctrl patch as quickly as possible.
Right now as Linus mentioned, its waiting for his review.
For your vibrator module, do you only rely on the i2c bus lines or
do you also need some pins as reset or interrupt line?
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-07-26 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E12ED16DF2DF754897A674F2B0E8F6C446AFF250C9@seldmbx01.corpusers.net>
2013-07-25 22:00 ` pinctrl and device-tree support in qcom drivers Linus Walleij
2013-07-25 22:56 ` Bird, Tim
2013-07-26 17:30 ` hanumant [this message]
2013-07-26 23:21 ` Bird, Tim
2013-07-26 22:47 ` Linus Walleij
2013-07-26 23:21 ` Bird, Tim
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=51F2B221.5000806@codeaurora.org \
--to=hanumant@codeaurora.org \
--cc=Bjorn.Andersson@sonymobile.com \
--cc=Tim.Bird@sonymobile.com \
--cc=davidb@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.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;
as well as URLs for NNTP newsgroup(s).