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: <20241104100019.1fbc38d8@akair>
Date: Mon, 4 Nov 2024 10:00:19 +0100
From: Andreas Kemnade <andreas@...nade.info>
To: Rob Herring <robh@...nel.org>
Cc: lee@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 mazziesaccount@...il.com, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, sre@...nel.org
Subject: Re: [PATCH] dt-bindings: mfd: bd71828: Use charger resistor in mOhm
 instead of MOhm

Am Fri, 1 Nov 2024 14:27:05 -0500
schrieb Rob Herring <robh@...nel.org>:

> On Tue, Oct 29, 2024 at 12:11:12PM +0100, Andreas Kemnade wrote:
> > Apparently there was some confusion regarding milliohm vs. megaohm.
> > (m/M). Use microohms to be able to properly specify the charger
> > resistor like other drivers do. This is not used yet by mainline
> > code yet. Specify a current sense resistor in milliohms range
> > rathes then megaohms range in the examples.  
> 
> milliohms?
> 
hmm, do not understand what you are after: Milliohms range:
I mean a value well expressed in milliohm (like 10-50mohm) in the
examples, but we use microohms to specify it like we often to, having
room for some unexpected precision requirements as we do in other
places also (microvolts for values more in mV/V range)

> rathes?

ok, simple typo: rather

Regards,
Andreas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ