linux-kernel - Re: [PATCH] regulator: ab8500: Provide map

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:	Sun, 21 Jul 2013 16:45:23 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Liam Girdwood <lgirdwood@...il.com>,
	Lee Jones <lee.jones@...aro.org>,
	Bengt Jonsson <bengt.g.jonsson@...ricsson.com>,
	linaro-kernel <linaro-kernel@...ts.linaro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Mark Brown <broonie@...aro.org>
Subject: Re: [PATCH] regulator: ab8500: Provide map_voltage() functions

On Wed, Jul 3, 2013 at 11:16 AM, Mark Brown <broonie@...nel.org> wrote:

> From: Mark Brown <broonie@...aro.org>
>
> Since all the voltage tables for ab8500 are sorted in ascending order we
> can improve performance by using regulator_map_voltage_ascend(). A couple
> of the regulators can actually use linear maps which would be even better.
>
> Signed-off-by: Mark Brown <broonie@...aro.org>

Hm. Have you looked closer at this one voltage table in this driver:

static const unsigned int ldo_vaux56_voltages[] = {
    1800000,
    1050000,
    1100000,
    1200000,
    1500000,
    2200000,
    2500000,
    2790000,
};

Or this one:

static const unsigned int ldo_sdio_voltages[] = {
    1160000,
    1050000,
    1100000,
    1500000,
    1800000,
    2200000,
    2910000,
    3050000,
};

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/