From: Lee Jones <lee@kernel.org>
To: Jakob Hauser <jahau@rocketmail.com>
Cc: Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
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>,
Henrik Grimler <henrik@grimler.se>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v6 00/10 RESEND] Add RT5033 charger device driver
Date: Thu, 1 Jun 2023 15:00:49 +0100 [thread overview]
Message-ID: <20230601140049.GF449117@google.com> (raw)
In-Reply-To: <a308cd6f-0f72-6a12-aa34-ce06290ce0bb@rocketmail.com>
On Wed, 31 May 2023, Jakob Hauser wrote:
> Dear all,
>
> On 15.05.23 22:57, Jakob Hauser wrote:
> > 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.
> >
> > RESEND: Sorry for spamming. The first try of sending v6 got interrupted and
> > was split into two threads on the lore list. Therefore sending it again.
> >
> > Changes in v6:
> > - Patch 5: In function rt5033_charger_probe() after
> > calling rt5033_charger_dt_init() replaced the return value from "-ENODEV"
> > to "PTR_ERR(charger->chg)", as suggested by Christophe.
> > - Patch 9: Changed the patch from adding "power-supplies: true" to replacing
> > "additionalProperties: false" by "unevaluatedProperties: false", as
> > suggested by Krzysztof.
> >
> > 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
> > v3: https://lore.kernel.org/linux-pm/cover.1682636929.git.jahau@rocketmail.com/T/#t
> > v4: https://lore.kernel.org/linux-pm/20230506155435.3005-1-jahau@rocketmail.com/T/#t
> > v5: https://lore.kernel.org/linux-pm/20230514123130.41172-1-jahau@rocketmail.com/T/#t
> >
> > The result of the patchset v6 can be seen at:
> > https://github.com/Jakko3/linux/blob/rt5033-charger_v6/drivers/power/supply/rt5033_charger.c
>
> What's missing on this patchset? I'm not familiar with the procedures. If
> all patches need ack's, then the ones for mfd (patches 2 & 4) and for
> dt-bindings (patch 10) are missing.
You're waiting on me. I will apply all of the patches and submit a PR.
You're in the queue - please stand-by.
> Link to the current patchset v6:
> - on lore: https://lore.kernel.org/linux-pm/cover.1684182964.git.jahau@rocketmail.com/T/#t
> - on patchwork: https://patchwork.kernel.org/project/linux-pm/list/?series=747771&state=%2A&archive=both
>
> > Jakob Hauser (9):
> > 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: Move struct rt5033_battery to battery
> > driver
> > power: supply: rt5033_battery: Adopt status property from charger
> > dt-bindings: power: supply: rt5033-battery: Apply
> > unevaluatedProperties
> > dt-bindings: Add rt5033 mfd, regulator and charger
> >
> > Stephan Gerhold (1):
> > mfd: rt5033: Drop rt5033-battery sub-device
> >
> > .../bindings/mfd/richtek,rt5033.yaml | 138 ++++
> > .../power/supply/richtek,rt5033-battery.yaml | 2 +-
> > .../power/supply/richtek,rt5033-charger.yaml | 65 ++
> > drivers/mfd/rt5033.c | 8 +-
> > drivers/power/supply/Kconfig | 8 +
> > drivers/power/supply/Makefile | 1 +
> > drivers/power/supply/rt5033_battery.c | 38 +-
> > drivers/power/supply/rt5033_charger.c | 744 ++++++++++++++++++
> > include/linux/mfd/rt5033-private.h | 64 +-
> > include/linux/mfd/rt5033.h | 24 -
> > 10 files changed, 1034 insertions(+), 58 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
>
> Kind regards,
> Jakob
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2023-06-01 14:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1684182964.git.jahau.ref@rocketmail.com>
2023-05-15 20:57 ` [PATCH v6 00/10 RESEND] Add RT5033 charger device driver Jakob Hauser
2023-05-15 20:57 ` [PATCH v6 01/10 RESEND] mfd: rt5033: Drop rt5033-battery sub-device Jakob Hauser
2023-05-15 20:57 ` [PATCH v6 02/10 RESEND] mfd: rt5033: Fix chip revision readout Jakob Hauser
2023-05-15 20:57 ` [PATCH v6 03/10 RESEND] mfd: rt5033: Fix STAT_MASK, HZ_MASK and AICR defines Jakob Hauser
2023-05-15 20:57 ` [PATCH v6 04/10 RESEND] mfd: rt5033: Apply preparatory changes before adding rt5033-charger driver Jakob Hauser
2023-05-25 10:44 ` Lee Jones
2023-05-25 17:16 ` Jakob Hauser
2023-05-15 20:57 ` [PATCH v6 05/10 RESEND] power: supply: rt5033_charger: Add RT5033 charger device driver Jakob Hauser
2023-05-15 20:57 ` [PATCH v6 06/10 RESEND] power: supply: rt5033_charger: Add cable detection and USB OTG supply Jakob Hauser
2023-08-17 9:38 ` (subset) " Lee Jones
2023-08-22 7:07 ` Lee Jones
2023-08-22 21:29 ` Sebastian Reichel
2023-09-03 12:43 ` Jakob Hauser
2023-09-04 14:27 ` Lee Jones
2023-05-15 20:57 ` [PATCH v6 07/10 RESEND] power: supply: rt5033_battery: Move struct rt5033_battery to battery driver Jakob Hauser
2023-05-15 20:57 ` [PATCH v6 08/10 RESEND] power: supply: rt5033_battery: Adopt status property from charger Jakob Hauser
2023-05-15 20:57 ` [PATCH v6 09/10 RESEND] dt-bindings: power: supply: rt5033-battery: Apply unevaluatedProperties Jakob Hauser
2023-05-15 21:30 ` Sebastian Reichel
2023-05-16 21:28 ` Conor Dooley
2023-05-15 20:57 ` [PATCH v6 10/10 RESEND] dt-bindings: Add rt5033 mfd, regulator and charger Jakob Hauser
[not found] ` <a308cd6f-0f72-6a12-aa34-ce06290ce0bb@rocketmail.com>
2023-06-01 14:00 ` Lee Jones [this message]
2023-06-08 17:19 ` [PATCH v6 00/10 RESEND] Add RT5033 charger device driver Lee Jones
2023-06-09 6:47 ` [GIT PULL] Immutable branch between MFD and Power due for the v6.5 merge window Lee Jones
2023-06-16 20:02 ` Jakob Hauser
2023-06-19 10:35 ` Lee Jones
2023-07-30 17:58 ` Jakob Hauser
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=20230601140049.GF449117@google.com \
--to=lee@kernel.org \
--cc=axel.lin@ingics.com \
--cc=beomho.seo@samsung.com \
--cc=broonie@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=henrik@grimler.se \
--cc=jahau@rocketmail.com \
--cc=krzysztof.kozlowski+dt@linaro.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).