linux-kernel - Re: regulator voltage aggregation

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: <20100817192806.09744719@lxorguk.ukuu.org.uk>
Date:	Tue, 17 Aug 2010 19:28:06 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Bobby Crabtree <bobbyc@...eaurora.org>
Cc:	broonie@...nsource.wolfsonmicro.com, lrg@...mlogic.co.uk,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: regulator voltage aggregation

O> int regulator_set_optimum_voltage(struct regulator *regulator,
>                 int min_uV, int max_uV);

Pedantic hat on - how can it be optimum if its a range ? (and an
adjective but that is really pedantic) ;))

Surely it's not the optimal value, it's the range at which it works at
all you are defining (between off, and escaping smoke).

set_voltage_range() sounds rather more natural to me.

Alan
--
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/