[PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib

Alan Cox alan at lxorguk.ukuu.org.uk
Wed Apr 20 10:54:07 EDT 2011

On Wed, 20 Apr 2011 14:32:35 +0200
Linus Walleij <linus.walleij at linaro.org> wrote:

> 2011/4/19 Kyungmin Park <kmpark at infradead.org>:
> > One more consideration, not mentioned previous time, is that pin
> > configuration for power down mode.
> > Samsung SoCs has retention GPIO configurations at sleep (suspend)
> > mode. and restore it at resume time.
> > it's need to reduce power and proper operation after suspend.
> Isn't this supposed to be handled by runtime_pm hooks inside
> your GPIO driver rather than by someone else talking to
> the GPIO driver trying to spool/unspool the state from the
> outside in some other place?
> Or am I getting things backwards now...?

IMHO that rather depends upon what knows the right things to do. The
platform may know the right way to manage GPIO pins but it may also be
that only the driver knows because the correct suspended pin states
depend on the driver or on the current runtime configuration - eg if a
specific GPIO must be left enabled for wakeup to work then it depends
whether that device is active not on the platform level properties.

More information about the linux-arm-kernel mailing list