From: ChiYuan Huang <cy_huang@richtek.com>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND v2 2/3] power: supply: rt9756: Add Richtek RT9756 smart cap divider charger
Date: Wed, 29 Oct 2025 09:05:00 +0800 [thread overview]
Message-ID: <aQFoPKXDx2BfalXE@git-send.richtek.com> (raw)
In-Reply-To: <aM0UBoynaX7ln2Tw@git-send.richtek.com>
On Fri, Sep 19, 2025 at 04:27:50PM +0800, ChiYuan Huang wrote:
> On Fri, Sep 19, 2025 at 01:43:02AM +0200, Sebastian Reichel wrote:
> Hi, Sebastian:
> > Hi,
> >
> > On Thu, Aug 14, 2025 at 03:31:07PM +0800, cy_huang@richtek.com wrote:
> > > From: ChiYuan Huang <cy_huang@richtek.com>
> > >
> > > Add support for RT9756 smart cap divider charger.
> > >
> > > The RT9759 is a high efficiency and high charge current charger. The
> > > maximum charge current is up to 8A. It integrates a dual-phase charge
> > > pump core with ADC monitoring.
> > >
> > > Signed-off-by: ChiYuan Huang <cy_huang@richtek.com>
> > > ---
> >
> > Sorry for the delay. This looks mostly good, but I really don't like
> > the custom properties for the battery voltage and current. Instead
> > of handling via custom properties, register a second power_supply
> > device with POWER_SUPPLY_TYPE_BATTERY and use the normal
> > POWER_SUPPLY_PROP_VOLTAGE_NOW and POWER_SUPPLY_PROP_CURRENT_NOW
> > properties. Having custom properties for the watchdog and the
> > operating mode is fine with me, as these two things are quite
> > specific to the RT9756 chips.
> >
> > While you are at it, you can also add this constant property for
> > the battery device:
> >
> > POWER_SUPPLY_PROP_TECHNOLOGY = POWER_SUPPLY_TECHNOLOGY_LION
> >
> > Also the charger's power_supply_config should set the
> > .supplied_to, listing the battery device, so that the kernel
> > is aware of the link between those two devices.
> >
> Essentianly, these two attributes are only used for battery monitoring
> from charger side perspective.
>
> As you know, RT9756 is a charger, not fuelgauge. To register a second
> power supply seems weird. If what you cares is the keyword 'battery',
> I can change it to 'vout'. What do you think?
Since there's no reply for this discussion, I already followed your suggestion
for the next revision.
Thx.
>
> Regards,
> ChiYuan.
> > Greetings,
> >
> > -- Sebastian
next prev parent reply other threads:[~2025-10-29 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 7:31 [PATCH RESEND v2 0/3] Add Richtek RT9756 Smart-Cap divider charger cy_huang
2025-08-14 7:31 ` [PATCH RESEND v2 1/3] dt-bindings: power: supply: Add Richtek RT9756 smart cap " cy_huang
2025-08-14 7:31 ` [PATCH RESEND v2 2/3] power: supply: rt9756: " cy_huang
2025-09-18 23:43 ` Sebastian Reichel
2025-09-19 8:27 ` ChiYuan Huang
2025-10-29 1:05 ` ChiYuan Huang [this message]
2025-08-14 7:31 ` [PATCH RESEND v2 3/3] Documentation: power: rt9756: Document exported sysfs entries cy_huang
2025-09-02 0:19 ` [PATCH RESEND v2 0/3] Add Richtek RT9756 Smart-Cap divider charger ChiYuan Huang
2025-09-17 2:19 ` ChiYuan Huang
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=aQFoPKXDx2BfalXE@git-send.richtek.com \
--to=cy_huang@richtek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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