linux-kernel - Re: [RFD] voltage/current regulator consumer interface

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] [day] [month] [year] [list]

Date:	Mon, 27 Apr 2009 15:21:06 +0100
From:	Mark Brown <broonie@...ena.org.uk>
To:	James Kosin <jkosin@...a.intcomgrp.com>
Cc:	Pavel Machek <pavel@....cz>, Mike Rapoport <mike@...pulab.co.il>,
	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...mlogic.co.uk>
Subject: Re: [RFD] voltage/current regulator consumer interface

On Mon, Apr 27, 2009 at 09:47:32AM -0400, James Kosin wrote:
> Mark Brown wrote:

> > This all started because this approach was nacked for serial drivers.
> > In any case, I'm not sure that'll scale - it may not be desirable or
> > reasonable to do something like that for all devices.  For example, the
> > devices may be connected via a technology that's not suitable (I've
> > worked on systems which used ethernet here).

> Ethernet can be treated as a serial interface as well down to the
> simplest level.  I'm leaving out a lot is making this assumption; but,
> it is true to a fault.

The big difference with ethernet is that it's multi-drop - you can't
turn on the power based on the ethernet interface being in use since
there can be more than one device connected.

> The same applies to disk devices, now we have IDE/SATA/etc. the disk
> device itself doesn't depend on the interface physically, the kernel
> treats all these as suitable interfaces for disk/CDROM/tape devices and
> the world is not turned on its ear just because there is a different
> physical interface.

You're suggesting modifying the link layer to do different things based
on which device is connnected to it; in any case the issue here is that
this class of hardware has no in-kernel driver to provide an abstaction
- it's all done by a user space daemon or similar.
--
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/