devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Figa <t.figa@samsung.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Tomasz Figa <tomasz.figa@gmail.com>,
	Doug Anderson <dianders@google.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	Thomas Abraham <thomas.abraham@linaro.org>,
	Simon Glass <sjg@chromium.org>, Olof Johansson <olof@lixom.net>,
	Kukjin Kim <kgene.kim@gmail.com>
Subject: Re: Pulls and drive strengths in the pinctrl world
Date: Fri, 17 May 2013 14:38:14 +0200	[thread overview]
Message-ID: <4505921.rFrq65cY6P@amdc1227> (raw)
In-Reply-To: <CACRpkdZvN_0fd6N11NeSRtVZd5A1oE9TEhbOOz6Q27x6M39bcQ@mail.gmail.com>

Hi Linus,

On Friday 17 of May 2013 13:59:54 Linus Walleij wrote:
> On Fri, May 17, 2013 at 11:09 AM, Tomasz Figa <tomasz.figa@gmail.com> wrote:
> >> Just add another state, pctldev->hog_shutdown to this, and
> >> add an operation pinctrl_force_poweroff() in the same spirit as
> >> pinctrl_force_sleep() that we already have.
> >> 
> >> Add a new state to include/linux/pinctrl/pinctrl-state.h:
> >> #define PINCTRL_STATE_POWEROFF "poweroff"
> >> 
> >> And define you pin table to hog these pins with the mentioned
> >> default and poweroff states.
> >> 
> >> Result: pinctrl core keeps track of your offstate too.
> > 
> > Power down mode settings on our pin controller are completely unrelated to
> > normal mode settings. You can set them once in appropriate registers and
> > pins are switched to them automatically when the SoC enters sleep mode.
> 
> Aha so it's actually automatic sleep modes, not power down
> (as in, disconnect the power and then push the "on" button to
> get it back up).
> 
> Please remember to document it per above in the code and the
> device tree, so everybody understands what it is.

Sure.

> > So IMHO in our case power mode settings are just additional pin
> > configuration options, next to pull-up/-down and driver strength.
> 
> I see. Yes that is different.
> 
> You might want to have a debugfs file in your driver for inspecting
> them though, that sounds like it could be helpful. I'd recommend
> augmenting your .pin_config_dbg_show() callback in the
> struct pinconf_ops to display this for each pin, in addition to the
> current configuration.

Seems reasonable.

Best regards,
-- 
Tomasz Figa
Linux Kernel Developer
Samsung R&D Institute Poland
Samsung Electronics

  reply	other threads:[~2013-05-17 12:38 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 16:44 Pulls and drive strengths in the pinctrl world Doug Anderson
2013-05-15 17:26 ` Tomasz Figa
2013-05-15 18:15   ` Olof Johansson
2013-05-15 21:19   ` Doug Anderson
2013-05-15 21:36     ` Tomasz Figa
2013-05-15 21:57       ` Doug Anderson
2013-05-15 18:29 ` Linus Walleij
2013-05-15 21:31   ` Doug Anderson
2013-05-15 21:41     ` Tomasz Figa
2013-05-15 21:43       ` Tomasz Figa
2013-05-15 22:01       ` Doug Anderson
2013-05-15 22:06         ` Tomasz Figa
2013-05-15 23:55           ` Doug Anderson
2013-05-16  0:13             ` Tomasz Figa
2013-05-16  0:22               ` Stephen Warren
     [not found]                 ` <519426A8.8090908-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-17 12:26                   ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-17 21:17                     ` Tomasz Figa
2013-05-18  8:18                       ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-18 14:57                         ` Tomasz Figa
2013-05-18 16:30                           ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-18 17:13                             ` Tomasz Figa
2013-05-19  9:17                               ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-19  9:46                                 ` Tomasz Figa
2013-05-19 10:39                                   ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-19 10:56                                     ` Tomasz Figa
2013-05-23 21:42                                 ` Stephen Warren
     [not found]                                   ` <519E8D41.9040508-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-05-24  9:10                                     ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-23 21:39                             ` Stephen Warren
2013-05-21 18:28                     ` Tomasz Figa
2013-05-21 19:09                       ` Jean-Christophe PLAGNIOL-VILLARD
2013-05-16  0:55               ` Doug Anderson
2013-05-16 18:00                 ` Doug Anderson
2013-05-15 23:51   ` Stephen Warren
2013-05-16  0:03     ` Doug Anderson
2013-05-16  0:19       ` Tomasz Figa
2013-05-16  0:58         ` Doug Anderson
2013-05-17  8:38       ` Linus Walleij
2013-05-17  9:09         ` Tomasz Figa
2013-05-17 11:59           ` Linus Walleij
2013-05-17 12:38             ` Tomasz Figa [this message]
2013-05-17 14:56               ` Doug Anderson

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=4505921.rFrq65cY6P@amdc1227 \
    --to=t.figa@samsung.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dianders@google.com \
    --cc=kgene.kim@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=sjg@chromium.org \
    --cc=swarren@wwwdotorg.org \
    --cc=thomas.abraham@linaro.org \
    --cc=tomasz.figa@gmail.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).