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]
Date:	Tue, 24 Feb 2009 22:26:22 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	Paulius Zaleckas <paulius.zaleckas@...tonika.lt>, greg@...ah.com,
	s.hauer@...gutronix.de, linux-arm-kernel@...ts.arm.linux.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 2/3] mxc: move serial driver init()/exit() to platform_device

On Tue, Feb 24, 2009 at 11:09:00PM +0100, Guennadi Liakhovetski wrote:
> On Tue, 24 Feb 2009, Russell King - ARM Linux wrote:
> 
> > I really don't like this approach to controlling multiplex pins, which
> > is to setup the SoC pin configuration when the driver is being bound and
> > to remove it when the driver is unbound.
> 
> What do you think about the reasoning given by Sascha here: 
> http://marc.info/?l=linux-arm-kernel&m=123453175927569&w=2 which is power 
> saving?

That kind of power saving methodology is far better being triggered from
the use of the driver, not whether it is loaded or not if and only if it
is appropriate and necessary for the hardware.

For example, if you do this with a serial port which is connected to the
external world, and you're monitoring it, you don't want your monitoring
to see a break condition every time the port is closed and re-opened.

If you talk about an I2S codec, you'd want to configure the SoCs outputs
to the codec to be logic 0 when powering it down because it isn't being
used.

That's all unrelated to whether the driver is loaded or not, or bound to
a device or not.
--
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