From: Guenter Roeck <linux@roeck-us.net>
To: Delphine_CC_Chiu/WYHQ/Wiwynn <Delphine_CC_Chiu@wiwynn.com>,
Conor Dooley <conor@kernel.org>
Cc: "patrick@stwcx.xyz" <patrick@stwcx.xyz>,
Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt-bindings: hwmon: Add lltc ltc4286 driver bindings
Date: Tue, 31 Oct 2023 07:14:54 -0700 [thread overview]
Message-ID: <708e84f3-01ac-455e-9b66-2f0e2be1a874@roeck-us.net> (raw)
In-Reply-To: <SG2PR04MB55438AA9A2989F406012A4D4A1A0A@SG2PR04MB5543.apcprd04.prod.outlook.com>
On 10/30/23 23:25, Delphine_CC_Chiu/WYHQ/Wiwynn wrote:
[ ... ]
>>
>> Actually, turns out there is some contradiction in the LTC4286 datasheet.
>> It mentions different coefficients in different places. It is all but impossible to
>> determine if the datasheet is wrong or if the chip uses a variety of coefficients
>> unless one has a real chip available. Sigh :-(.
> We are not the chip vendor, but we could forward your question to vendor.
> Could you point out the exact places (which pages) where are the contradiction in LTC4286 datasheet?
>
See "PMBUS COMMAND SUMMARY", default values:
"IOUT_OC_WARN_LIMIT" says "21.3 mV/RSENSE"
"PIN_OP_WARN_LIMIT" says "2.8/RSENSE"
This seems to contradict "Table 8. PMBus M, B, and R Parameters". But then,
reading it again (and again), I think it is just an odd and confusing way
of trying to describe the 0x7fff default register values. Sorry for the noise.
Guenter
next prev parent reply other threads:[~2023-10-31 14:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 8:15 [PATCH v2 0/2] LTC4286 and LTC4287 driver support Delphine CC Chiu
2023-10-26 8:15 ` [PATCH v2 1/2] dt-bindings: hwmon: Add lltc ltc4286 driver bindings Delphine CC Chiu
2023-10-26 14:25 ` Conor Dooley
2023-10-26 15:09 ` Guenter Roeck
2023-10-26 15:26 ` Conor Dooley
2023-10-26 16:48 ` Guenter Roeck
2023-10-31 6:25 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-31 14:14 ` Guenter Roeck [this message]
2023-10-31 5:59 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-31 5:57 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-31 5:54 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-27 7:20 ` kernel test robot
2023-10-26 8:15 ` [PATCH v2 2/2] hwmon: pmbus: Add ltc4286 driver Delphine CC Chiu
2023-10-26 16:27 ` Guenter Roeck
2023-10-31 6:46 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-31 13:47 ` Guenter Roeck
2023-11-07 3:08 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-11-07 3:29 ` Guenter Roeck
2023-11-15 8:42 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-11-15 22:46 ` Guenter Roeck
2023-11-21 2:37 ` Delphine_CC_Chiu/WYHQ/Wiwynn
2023-10-28 3:54 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=708e84f3-01ac-455e-9b66-2f0e2be1a874@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Delphine_CC_Chiu@wiwynn.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick@stwcx.xyz \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox