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>] [day] [month] [year] [list]
Message-ID: <CAFRkauBgVjtjJPM_5GdNTrzUymMEo180xajYwT4Duk=yxwOcbg@mail.gmail.com>
Date:   Fri, 8 Feb 2019 20:54:40 +0800
From:   Axel Lin <axel.lin@...ics.com>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     Beomho Seo <beomho.seo@...sung.com>,
        Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: regulator: rt5033: Question regarding define for RT5033_REGULATOR_BUCK/LOD_VOLTAGE_MAX

Hi Beomho,
The code has below defines in include/linux/mfd/rt5033-private.h
#define RT5033_REGULATOR_BUCK_VOLTAGE_MAX               3000000U
#define RT5033_REGULATOR_LDO_VOLTAGE_MAX                3000000U

However, according to current settings in rt5033 regulator driver:
For LDOs, it can support up to
RT5033_REGULATOR_LDO_VOLTAGE_MIN + RT5033_REGULATOR_LDO_VOLTAGE_STEP *
(RT5033_REGULATOR_LDO_VOLTAGE_STEP_NUM - 1)
= 1200000 + 100000 * 31
= 4300000 (This is different from the define of
RT5033_REGULATOR_LDO_VOLTAGE_MAX)

The same issue for BUCKs.

I don't find the datasheet, can you check which part is incorrect that
causes the inconsistent?

Thanks,
Axel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ