From: Nishanth Menon <nm@ti.com>
To: Pascal Huerst <pascal.huerst@gmail.com>,
Nishanth Menon <nm@ti.com>,
wsa@the-dreams.de
Cc: tony@atomide.com, linux-omap@vger.kernel.org,
linux-i2c@vger.kernel.org, Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH v2] omap: i2c: Add calls for pinctrl state select
Date: Tue, 28 Apr 2015 08:11:12 -0500 [thread overview]
Message-ID: <553F86F0.8000107@ti.com> (raw)
In-Reply-To: <553F696A.8060408@gmail.com>
On 04/28/2015 06:05 AM, Pascal Huerst wrote:
[...]
> On 23.04.2015 02:32, Nishanth Menon wrote:
[...]
>> Would you think adding relevant documentation in
>> Documentation/devicetree/bindings/i2c/i2c-omap.txt might be good as
>> well? I mean, folks should know looking at dt documentation that this
>> bus driver does indeed support this option..
>
> I'm not sure about that. Actually this is all handled by the pinctrl
> subsystem, so I would guess that documentation belongs there, since in:
>
> Documentation/devicetree/bindings/i2c/i2c-at91.txt
> Documentation/devicetree/bindings/i2c/i2c-nomadik.txt
>
> is no documentation about that as well. But there is documentation in:
>
> Documentation/pinctrl.txt
>
> right? Otherwise, I would say we should add documentation for all
> devices, so it is consistent.
that is probably good since drivers may or maynot support support the
sleep configuration.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-04-28 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 9:07 [PATCH v2] omap: i2c: Add calls for pinctrl state select pascal.huerst-Re5JQEeQqe8AvxtiuMwx3w
2015-04-23 0:32 ` Nishanth Menon
[not found] ` <55383D9A.4020302-l0cyMroinI0@public.gmane.org>
2015-04-28 11:05 ` Pascal Huerst
2015-04-28 13:11 ` Nishanth Menon [this message]
2015-04-28 13:11 ` Nishanth Menon
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=553F86F0.8000107@ti.com \
--to=nm@ti.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=pascal.huerst@gmail.com \
--cc=tony@atomide.com \
--cc=wsa@the-dreams.de \
/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).