From: Lee Jones <lee.jones@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Sebastian Reichel <sre@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Beomho Seo <beomho.seo@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH v2 3/3] mfd: rt5033: Drop rt5033-battery sub-device
Date: Wed, 19 May 2021 15:46:30 +0100 [thread overview]
Message-ID: <20210519144630.GC2549456@dell> (raw)
In-Reply-To: <20210517105113.240379-4-stephan@gerhold.net>
On Mon, 17 May 2021, Stephan Gerhold wrote:
> The fuel gauge in the RT5033 PMIC (rt5033-battery) has its own I2C bus
> and interrupt lines. Therefore, it is not part of the MFD device
> and needs to be specified separately in the device tree.
>
> Cc: Beomho Seo <beomho.seo@samsung.com>
> Cc: Chanwoo Choi <cw00.choi@samsung.com>
> Fixes: 0b271258544b ("mfd: rt5033: Add Richtek RT5033 driver core.")
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> drivers/mfd/rt5033.c | 3 ---
> 1 file changed, 3 deletions(-)
Acked-by: Lee Jones <lee.jones@linaro.org>
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2021-05-19 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 10:51 [PATCH v2 0/3] Fix RT5033 battery device tree probing Stephan Gerhold
2021-05-17 10:51 ` [PATCH v2 1/3] dt-bindings: power: supply: Add DT schema for richtek,rt5033-battery Stephan Gerhold
2021-05-19 18:57 ` Rob Herring
2021-05-17 10:51 ` [PATCH v2 2/3] power: supply: rt5033_battery: Fix device tree enumeration Stephan Gerhold
2021-05-17 10:51 ` [PATCH v2 3/3] mfd: rt5033: Drop rt5033-battery sub-device Stephan Gerhold
2021-05-19 14:46 ` Lee Jones [this message]
2021-06-14 16:47 ` Stephan Gerhold
2021-06-04 10:34 ` [PATCH v2 0/3] Fix RT5033 battery device tree probing 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=20210519144630.GC2549456@dell \
--to=lee.jones@linaro.org \
--cc=beomho.seo@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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).