From: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
To: sre@kernel.org, wens@csie.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/5] AXP20x USB power supply remove use of variant IDs
Date: Sat, 18 Feb 2023 20:49:41 +0000 [thread overview]
Message-ID: <20230218204946.106316-1-aidanmacdonald.0x0@gmail.com> (raw)
The goal of this series is to remove the driver's dependence on
variant IDs, because they are hard to maintain and make it more
difficult to add support for new chip variants.
Regmap fields are used to replace ID checks and handle bits/fields
that may differ (or not exist at all) on certain variants.
Aidan MacDonald (5):
power: supply: axp20x_usb_power: Simplify USB current limit handling
power: supply: axp20x_usb_power: Use regmap fields for VBUS monitor
feature
power: supply: axp20x_usb_power: Use regmap fields for USB BC feature
power: supply: axp20x_usb_power: Use regmap field for VBUS disabling
power: supply: axp20x_usb_power: Remove variant IDs from VBUS polling
check
drivers/power/supply/axp20x_usb_power.c | 285 +++++++++++-------------
1 file changed, 130 insertions(+), 155 deletions(-)
--
2.39.2
next reply other threads:[~2023-02-18 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 20:49 Aidan MacDonald [this message]
2023-02-18 20:49 ` [PATCH v1 1/5] power: supply: axp20x_usb_power: Simplify USB current limit handling Aidan MacDonald
2023-02-18 20:49 ` [PATCH v1 2/5] power: supply: axp20x_usb_power: Use regmap fields for VBUS monitor feature Aidan MacDonald
2023-02-18 20:49 ` [PATCH v1 3/5] power: supply: axp20x_usb_power: Use regmap fields for USB BC feature Aidan MacDonald
2023-02-18 20:49 ` [PATCH v1 4/5] power: supply: axp20x_usb_power: Use regmap field for VBUS disabling Aidan MacDonald
2023-02-18 20:49 ` [PATCH v1 5/5] power: supply: axp20x_usb_power: Remove variant IDs from VBUS polling check Aidan MacDonald
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=20230218204946.106316-1-aidanmacdonald.0x0@gmail.com \
--to=aidanmacdonald.0x0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®