From: Henrik Grimler <henrik.grimler@axis.com>
To: "Sebastian Reichel" <sre@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Pali Rohár" <pali@kernel.org>, "Andrew F. Davis" <afd@ti.com>,
"Chris Lapa" <chris@lapa.com.au>, "Dan Murphy" <dmurphy@ti.com>
Cc: <linux-pm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
<kernel@axis.com>, Henrik Grimler <henrik.grimler@axis.com>
Subject: [PATCH v2 0/3] power: supply: bq27xxx: add bq27z746
Date: Tue, 18 Aug 2026 11:48:19 +0200 [thread overview]
Message-ID: <20260818-bq27z746-v2-0-0371e206665f@axis.com> (raw)
bq27z746 is similar to bq27z561 but with additional protection
functionality. The standard register set is identical, but the
extended registers accessed through AltManufacturerAccess has
differences.
While working on the series I also noticed that bq27z561 supports
interrupts, but the dt binding marks it as unsupported. Fix while at
it.
For reference the TRMs for the affected bq chips can be found at these
direct links:
- bq27z746: https://ti.com/lit/ug/sluuca6/sluuca6.pdf
- bq27z561: https://ti.com/lit/ug/sluubo7/sluubo7.pdf
Signed-off-by: Henrik Grimler <henrik.grimler@axis.com>
---
Changes in v2:
- Rebase and drop applied patches
- Add patch to add interrupt support for bq27z561, issue found thanks
to that Sashiko commented on it
- Describe differences between bq27z746 and bq27z561 in more detail
- Link to v1: https://lore.kernel.org/r/20260811-bq27z746-v1-0-3a4fa38205cc@axis.com
---
Henrik Grimler (3):
dt-bindings: power: bq27xxx: bq27z561: allow interrupts property
dt-bindings: power: bq27xxx: document bq27z746
power: supply: bq27xxx: add support for bq27z746
Documentation/devicetree/bindings/power/supply/bq27xxx.yaml | 2 +-
drivers/power/supply/bq27xxx_battery.c | 6 ++++++
drivers/power/supply/bq27xxx_battery_i2c.c | 2 ++
include/linux/power/bq27xxx_battery.h | 1 +
4 files changed, 10 insertions(+), 1 deletion(-)
---
base-commit: 2da28b059e0ddcd2e1956eeae383246207965573
change-id: 20260709-bq27z746-8dc4c2ec0948
Best regards,
--
Henrik Grimler <henrik.grimler@axis.com>
next reply other threads:[~2026-08-18 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 9:48 Henrik Grimler [this message]
2026-08-18 9:48 ` [PATCH v2 1/3] dt-bindings: power: bq27xxx: bq27z561: allow interrupts property Henrik Grimler
2026-08-19 9:52 ` Krzysztof Kozlowski
2026-08-18 9:48 ` [PATCH v2 2/3] dt-bindings: power: bq27xxx: document bq27z746 Henrik Grimler
2026-08-19 9:52 ` Krzysztof Kozlowski
2026-08-18 9:48 ` [PATCH v2 3/3] power: supply: bq27xxx: add support for bq27z746 Henrik Grimler
2026-08-19 13:46 ` Andrew Davis
2026-09-09 21:23 ` [PATCH v2 0/3] power: supply: bq27xxx: add bq27z746 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=20260818-bq27z746-v2-0-0371e206665f@axis.com \
--to=henrik.grimler@axis.com \
--cc=afd@ti.com \
--cc=chris@lapa.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=kernel@axis.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali@kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--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