From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Iskren Chernev <me@iskren.info>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Matheus Castello <matheus@castello.eng.br>,
Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/4] dt-bindings: power: supply: maxim,max17040: update properties
Date: Wed, 8 Mar 2023 11:53:32 +0100 [thread overview]
Message-ID: <d0d0617d-8a2e-7a71-f4fe-f69896f84ede@linaro.org> (raw)
In-Reply-To: <CAPVz0n3sKH_7x=aNVLaHVN0F1FWLVRW+MGoj9qBO9V=TDuv_jQ@mail.gmail.com>
On 08/03/2023 11:51, Svyatoslav Ryhel wrote:
> ср, 8 бер. 2023 р. о 12:44 Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> пише:
>>
>> On 08/03/2023 10:15, Svyatoslav Ryhel wrote:
>>
>>>> max17040 does not have ADC temperature input... so is it system
>>>> configuration?
>>>>
>>>
>>> yes, I own a device (LG Optimus Vu P895) which uses max17043
>>> coupled with ADC thermal sensor
>>>
>>>>> +
>>>>> + io-channel-names:
>>>>> + items:
>>>>> + - const: temp
>>>>
>>>> Drop the names property, not needed for one item.
>>>>
>>>
>>> Alright, but driver patch expects temp name. I will look if this
>>> is adjustable.
>>
>> I think I saw cases without names.
>>
>
> There is no io-channel without a name. And io-channels are mostly used
> by power supply devices.
>
>>>
>>>>> +
>>>>> wakeup-source:
>>>>> type: boolean
>>>>> description: |
>>>>> @@ -95,3 +109,26 @@ examples:
>>>>> wakeup-source;
>>>>> };
>>>>> };
>>>>> + - |
>>>>> + #include <dt-bindings/interrupt-controller/irq.h>
>>>>> + i2c0 {
>>>>> + #address-cells = <1>;
>>>>> + #size-cells = <0>;
>>>>> +
>>>>> + fuel-gauge@36 {
>>>>> + compatible = "maxim,max17043";
>>>>> + reg = <0x36>;
>>>>> +
>>>>> + interrupt-parent = <&gpio>;
>>>>> + interrupts = <144 IRQ_TYPE_EDGE_FALLING>;
>>>>> +
>>>>> + monitored-battery = <&battery>;
>>>>> + power-supplies = <&charger>;
>>>>
>>>> But here you suggests something else than VDD... The hardware does not
>>>> take charger as input. It takes power supply - vdd.
>>>>
>>>
>>> Power system allows passing properties from other power devices.
>>> In this case battery health and status are passed from charger.
>>
>> So this is not an input to device? Then it does not really look like
>> property of this hardware. Fuel gauge does not control the charger, also
>> from system configuration point of view.
>>
>
> It is not controlling charger, the charger provides the status and
> health of the battery to the fuel gauge. This option is also used in
> other fuel gauges.
How regulator provides health and status of the battery? I don't understand.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-08 10:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 8:44 [PATCH v1 0/4] Add optional properties to MAX17040 Svyatoslav Ryhel
2023-03-08 8:44 ` [PATCH v1 1/4] dt-bindings: power: supply: maxim,max17040: update properties Svyatoslav Ryhel
2023-03-08 9:04 ` Krzysztof Kozlowski
2023-03-08 9:15 ` Svyatoslav Ryhel
2023-03-08 10:44 ` Krzysztof Kozlowski
2023-03-08 10:51 ` Svyatoslav Ryhel
2023-03-08 10:53 ` Krzysztof Kozlowski [this message]
2023-03-08 11:06 ` Svyatoslav Ryhel
2023-03-08 11:12 ` Krzysztof Kozlowski
2023-05-15 22:17 ` Sebastian Reichel
2023-03-08 8:44 ` [PATCH v1 2/4] power: max17040: add simple battery cell support Svyatoslav Ryhel
2023-05-15 22:21 ` Sebastian Reichel
2023-03-08 8:44 ` [PATCH v1 3/4] power: max17040: add passing props from supplier Svyatoslav Ryhel
2023-05-15 22:41 ` Sebastian Reichel
2023-03-08 8:44 ` [PATCH v1 4/4] power: max17040: get thermal data from adc if available Svyatoslav Ryhel
2023-03-08 9:08 ` Krzysztof Kozlowski
2023-03-08 9:23 ` Svyatoslav Ryhel
2023-03-08 10:46 ` Krzysztof Kozlowski
2023-03-09 0:24 ` kernel test robot
2023-03-09 0:24 ` kernel test robot
2023-03-09 0:45 ` kernel test robot
2023-05-15 22:39 ` Sebastian Reichel
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=d0d0617d-8a2e-7a71-f4fe-f69896f84ede@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=clamor95@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=matheus@castello.eng.br \
--cc=me@iskren.info \
--cc=robh+dt@kernel.org \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).