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: <20190610135258.GA7976@xo-6d-61-c0.localdomain>
Date:   Mon, 10 Jun 2019 15:52:58 +0200
From:   Pavel Machek <pavel@....cz>
To:     Angus Ainslie <angus@...ea.ca>
Cc:     Shawn Guo <shawnguo@...nel.org>, angus.ainslie@...i.sm,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        NXP Linux Team <linux-imx@....com>,
        Lucas Stach <l.stach@...gutronix.de>,
        Abel Vesa <abel.vesa@....com>,
        Andrey Smirnov <andrew.smirnov@...il.com>,
        Carlo Caione <ccaione@...libre.com>,
        Guido Günther <agx@...xcpu.org>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v15 0/3] Add support for the Purism Librem5 devkit

On Wed 2019-06-05 06:48:05, Angus Ainslie wrote:
> On 2019-06-05 03:03, Shawn Guo wrote:
> >On Tue, May 28, 2019 at 05:57:44AM -0700, Angus Ainslie (Purism) wrote:
> >>The Librem5 devkit is based on the imx8mq from NXP. This is a default
> >>devicetree to boot the board to a command prompt.
> >>
> >>Changes since v14:
> >>
> >>Add regulator-always-on for the SNVS regulators.
> >>Added pgc nodes.
> >>Fixed charger pre-current.
> >
> >Since Pavel was reviewing your patches, you should copy him on the new
> >version.  Has this version addressed all his review comments?
> >
> 
> Sorry I had meant to include him in the CC.
> 
> I believe so but don't want to speak for him so we should see if he
> has anymore.

I did not check the code, sorry.

I still believe your shutdown voltage is too low; try that. Battery will go down from 3V
to 2.8V in seconds, so you don't really gain anything by using lower threshold, and you
may not even have enough time to shutdown the system if you set it too low.

Normally something like 3.0V, 3.2V is reasonable shutdown voltage.

Best regards,
										Pavel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ