lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTim7pGJVEngS7jJHgcn1FTMEiUC83w@mail.gmail.com>
Date:	Wed, 20 Apr 2011 21:38:59 +0900
From:	Kyungmin Park <kmpark@...radead.org>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Ben Nizette <bn@...sdigital.com>, linux-kernel@...r.kernel.org,
	Grant Likely <grant.likely@...retlab.ca>,
	Lee Jones <lee.jones@...aro.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib

On Wed, Apr 20, 2011 at 9:32 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
> 2011/4/19 Kyungmin Park <kmpark@...radead.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?

It's different from normal gpio input/output pin. It has different
offset and configuration.
As I know, current gpiolib doesn't support it.

Of course these should be handled at board file instead of drivers.

Thank you,
Kyungmin Park
>
> Or am I getting things backwards now...?
>
> Yours,
> Linus Walleij
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ