From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Sebastian Reichel <sre@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Emil Velikov <emil.velikov@collabora.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com,
Sebastian Reichel <sebastian.reichel@collabora.com>
Subject: [PATCHv2 0/2] SBS battery PEC support
Date: Sat, 6 Jun 2020 01:06:23 +0200 [thread overview]
Message-ID: <20200605230625.192427-1-sebastian.reichel@collabora.com> (raw)
Hi,
Second try to enable PEC for SBS battery. Mainline currently
has 3 different platforms using sbs-battery with an I2C driver
not implementing I2C_M_RECV_LEN:
* i2c-exynos5
* i2c-rk3x
* i2c-tegra
On those platforms PEC will be temporarly disabled for SBS
functions requesting strings. I considered moving the emulation
to I2C core, but it's specific to the SBS battery. The hack
only works because the strings are constant.
Changes since PATCHv1:
* dropped all applied changes
* rebased on top of power-supply's for-next branch
* keep existing string reading method as fallback
-- Sebastian
Sebastian Reichel (2):
power: supply: sbs-battery: use i2c_smbus_read_block_data()
power: supply: sbs-battery: add PEC support"
drivers/power/supply/sbs-battery.c | 89 +++++++++++++++++++++++++++++-
1 file changed, 87 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-06-05 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200605230641eucas1p199386d808ad8ce83006092da23e48bb5@eucas1p1.samsung.com>
2020-06-05 23:06 ` Sebastian Reichel [this message]
2020-06-05 23:06 ` [PATCHv2 1/2] power: supply: sbs-battery: use i2c_smbus_read_block_data() Sebastian Reichel
2020-06-05 23:06 ` [PATCHv2 2/2] power: supply: sbs-battery: add PEC support Sebastian Reichel
2020-06-08 6:23 ` [PATCHv2 0/2] SBS battery " Marek Szyprowski
2020-06-19 16:42 ` 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=20200605230625.192427-1-sebastian.reichel@collabora.com \
--to=sebastian.reichel@collabora.com \
--cc=emil.velikov@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.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;
as well as URLs for NNTP newsgroup(s).