linux-kernel - Re: [PATCH] regulator: pf8x00: Use regulator_map_voltage_ascend for pf8x00_buck7

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:   Wed, 17 Feb 2021 00:56:27 +0100
From:   Adrien Grassein <adrien.grassein@...il.com>
To:     Axel Lin <axel.lin@...ics.com>
Cc:     Mark Brown <broonie@...nel.org>,
        Jagan Teki <jagan@...rulasolutions.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] regulator: pf8x00: Use regulator_map_voltage_ascend for pf8x00_buck7_ops

Le mar. 16 févr. 2021 à 07:01, Axel Lin <axel.lin@...ics.com> a écrit :
>
> The voltages in pf8x00_sw7_voltages are in ascendant order, so use
> regulator_map_voltage_ascend.
>
> Signed-off-by: Axel Lin <axel.lin@...ics.com>
> ---
>  drivers/regulator/pf8x00-regulator.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/regulator/pf8x00-regulator.c b/drivers/regulator/pf8x00-regulator.c
> index 9b28bd63208d..5d319fb81288 100644
> --- a/drivers/regulator/pf8x00-regulator.c
> +++ b/drivers/regulator/pf8x00-regulator.c
> @@ -359,6 +359,7 @@ static const struct regulator_ops pf8x00_buck7_ops = {
>         .disable = regulator_disable_regmap,
>         .is_enabled = regulator_is_enabled_regmap,
>         .list_voltage = regulator_list_voltage_table,
> +       .map_voltage = regulator_map_voltage_ascend,
>         .set_voltage_sel = regulator_set_voltage_sel_regmap,
>         .get_voltage_sel = regulator_get_voltage_sel_regmap,
>         .get_current_limit = regulator_get_current_limit_regmap,
> --
> 2.25.1
>

Reviewed-by: Adrien Grassein <adrien.grassein@...il.com>