linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakob Hauser <jahau@rocketmail.com>
To: Sebastian Reichel <sre@kernel.org>, Lee Jones <lee@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Beomho Seo <beomho.seo@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Stephan Gerhold <stephan@gerhold.net>,
	Raymond Hackley <raymondhackley@protonmail.com>,
	Pavel Machek <pavel@ucw.cz>, Axel Lin <axel.lin@ingics.com>,
	ChiYuan Huang <cy_huang@richtek.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	Jakob Hauser <jahau@rocketmail.com>
Subject: [PATCH v3 0/8] Add RT5033 charger device driver
Date: Fri, 28 Apr 2023 01:30:03 +0200	[thread overview]
Message-ID: <cover.1682636929.git.jahau@rocketmail.com> (raw)
In-Reply-To: cover.1682636929.git.jahau.ref@rocketmail.com

This patchset adds the charger driver "rt5033-charger". It is part of the
multifunction device rt5033. The patchset is based on an older version by
Beomho Seo of March 2015. For more information on the history and setup of
the patchset see the cover sheet of version v1, there is a link further down
below the changelog.

The patchset is still based on next-20230413.

Changes in v3:
 - Drobbed v2 patch 5 "regulator: rt5033: Change regulator names to lowercase".
   It affects an existing driver, therefore the uppercase node names are
   tolerable.
 - Patch 5: In function rt5033_get_charger_state() after "if (!regmap)"
   changed "return state" to "return POWER_SUPPLY_STATUS_UNKNOWN". If the
   regmap isn't available, the status is unknown.
 - Patch 5: Changed function rt5033_charger_dt_init() to the devicetree
   "battery" node readout style.
 - Patch 5: Added dev_err() messages if the values are out of range in the
   init functions rt5033_init_const_charge(), rt5033_init_fast_charge() and
   rt5033_init_pre_charge().
 - Patch 5: In function rt5033_charger_probe() moved rt5033_charger_dt_init()
   and rt5033_charger_reg_init() behind devm_power_supply_register() because
   the power supply needs to be initiated to read out the "battery" node.
 - Patch 7: In function rt5033_battery_get_status() after "if (!charger)"
   changed "return -ENODEV" to "return POWER_SUPPLY_STATUS_UNKNOWN". If the
   charger isn't available, the status is unknown.
 - Changes on patch 8 are described in that patch below the commit message.

v1: https://lore.kernel.org/linux-pm/cover.1677620677.git.jahau@rocketmail.com/T/#t
v2: https://lore.kernel.org/linux-pm/cover.1681646904.git.jahau@rocketmail.com/T/#t

The result of the patchset v3 can be seen at:
https://github.com/Jakko3/linux/blob/rt5033-charger_v3/drivers/power/supply/rt5033_charger.c

Jakob Hauser (7):
  mfd: rt5033: Fix chip revision readout
  mfd: rt5033: Fix STAT_MASK, HZ_MASK and AICR defines
  mfd: rt5033: Apply preparatory changes before adding rt5033-charger
    driver
  power: supply: rt5033_charger: Add RT5033 charger device driver
  power: supply: rt5033_charger: Add cable detection and USB OTG supply
  power: supply: rt5033_battery: Adopt status property from charger
  dt-bindings: Add rt5033 mfd, regulator and charger

Stephan Gerhold (1):
  mfd: rt5033: Drop rt5033-battery sub-device

 .../bindings/mfd/richtek,rt5033.yaml          | 105 +++
 .../power/supply/richtek,rt5033-charger.yaml  |  63 ++
 drivers/mfd/rt5033.c                          |   8 +-
 drivers/power/supply/Kconfig                  |   8 +
 drivers/power/supply/Makefile                 |   1 +
 drivers/power/supply/rt5033_battery.c         |  24 +
 drivers/power/supply/rt5033_charger.c         | 725 ++++++++++++++++++
 include/linux/mfd/rt5033-private.h            |  64 +-
 include/linux/mfd/rt5033.h                    |  10 +-
 9 files changed, 981 insertions(+), 27 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/mfd/richtek,rt5033.yaml
 create mode 100644 Documentation/devicetree/bindings/power/supply/richtek,rt5033-charger.yaml
 create mode 100644 drivers/power/supply/rt5033_charger.c

-- 
2.39.2


       reply	other threads:[~2023-04-27 23:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1682636929.git.jahau.ref@rocketmail.com>
2023-04-27 23:30 ` Jakob Hauser [this message]
2023-04-27 23:30   ` [PATCH v3 1/8] mfd: rt5033: Drop rt5033-battery sub-device Jakob Hauser
2023-04-27 23:30   ` [PATCH v3 2/8] mfd: rt5033: Fix chip revision readout Jakob Hauser
2023-04-27 23:30   ` [PATCH v3 3/8] mfd: rt5033: Fix STAT_MASK, HZ_MASK and AICR defines Jakob Hauser
2023-04-27 23:30   ` [PATCH v3 4/8] mfd: rt5033: Apply preparatory changes before adding rt5033-charger driver Jakob Hauser
2023-04-27 23:30   ` [PATCH v3 5/8] power: supply: rt5033_charger: Add RT5033 charger device driver Jakob Hauser
2023-05-05 11:51     ` Linus Walleij
2023-04-27 23:30   ` [PATCH v3 6/8] power: supply: rt5033_charger: Add cable detection and USB OTG supply Jakob Hauser
2023-04-27 23:30   ` [PATCH v3 7/8] power: supply: rt5033_battery: Adopt status property from charger Jakob Hauser
2023-04-27 23:30   ` [PATCH v3 8/8] dt-bindings: Add rt5033 mfd, regulator and charger Jakob Hauser
2023-04-28 14:39     ` Henrik Grimler
2023-04-28 15:42       ` Jakob Hauser
2023-05-01  7:21     ` Krzysztof Kozlowski
2023-05-01 17:35       ` Jakob Hauser
2023-05-01 21:16         ` Jakob Hauser
2023-05-02 10:59           ` Krzysztof Kozlowski
2023-05-03 19:33             ` Jakob Hauser
2023-05-05 20:13               ` Rob Herring
2023-05-06 10:48                 ` Jakob Hauser
2023-05-01  9:13     ` Linus Walleij

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=cover.1682636929.git.jahau@rocketmail.com \
    --to=jahau@rocketmail.com \
    --cc=axel.lin@ingics.com \
    --cc=beomho.seo@samsung.com \
    --cc=broonie@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=cy_huang@richtek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=phone-devel@vger.kernel.org \
    --cc=raymondhackley@protonmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sre@kernel.org \
    --cc=stephan@gerhold.net \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).