From: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
To: "sebastian.reichel@collabora.com" <sebastian.reichel@collabora.com>
Cc: "alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mazziesaccount@gmail.com" <mazziesaccount@gmail.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"Mutanen, Mikko" <Mikko.Mutanen@fi.rohmeurope.com>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
"Haikola, Heikki" <Heikki.Haikola@fi.rohmeurope.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v14 7/8] power: supply: Initial support for ROHM BD70528 PMIC charger block
Date: Fri, 3 May 2019 05:29:53 +0000 [thread overview]
Message-ID: <322fa765ddd72972aba931c706657661ca685afa.camel@fi.rohmeurope.com> (raw)
In-Reply-To: <20190502195049.brysexbyyq7khtr4@earth.universe>
Hello Sebastian,
On Thu, 2019-05-02 at 21:50 +0200, Sebastian Reichel wrote:
> Hi,
>
> On Thu, May 02, 2019 at 12:17:12PM +0300, Matti Vaittinen wrote:
> > ROHM BD70528 PMIC includes battery charger block. Support charger
> > staus queries and doing few basic settings like input current limit
> > and charging current.
> >
> > Signed-off-by: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
> > Acked-by: Sebastian Reichel <sebastian.reichel@collabora.com>
>
> Please only add Acked-by when you receive one, especially when you
> do not implement all requested changes :)
Sorry. This is my bad. I translated your: "Otherwise looks ok to me."
- to an ack. And I was pretty sure you didn't want to staticize the
local array. I should've known better. I should have waited for your Ok
to leaving the static out before adding an ack.
>
> > +static int bd70528_get_irqs(struct platform_device *pdev,
> > + struct bd70528_psy *bdpsy)
> > +{
> > + int irq, i, ret;
> > + unsigned int mask;
> > + const struct irq_name_pair bd70528_chg_irqs[] = {
> > + { .n = "bd70528-bat-ov-res", .h =
> > BD_IRQ_HND(BAT_OV_RES) },
> > + { .n = "bd70528-bat-ov-det", .h =
> > BD_IRQ_HND(BAT_OV_DET) },
> > + { .n = "bd70528-bat-dead", .h = BD_IRQ_HND(DBAT_DET) },
> > + { .n = "bd70528-bat-warmed", .h = BD_IRQ_HND(COLD_RES)
> > },
> > + { .n = "bd70528-bat-cold", .h = BD_IRQ_HND(COLD_DET) },
> > + { .n = "bd70528-bat-cooled", .h = BD_IRQ_HND(HOT_RES)
> > },
> > + { .n = "bd70528-bat-hot", .h = BD_IRQ_HND(HOT_DET) },
> > + { .n = "bd70528-chg-tshd", .h = BD_IRQ_HND(CHG_TSD) },
> > + { .n = "bd70528-bat-removed", .h = BD_IRQ_HND(BAT_RMV)
> > },
> > + { .n = "bd70528-bat-detected", .h = BD_IRQ_HND(BAT_DET)
> > },
> > + { .n = "bd70528-dcin2-ov-res", .h =
> > BD_IRQ_HND(DCIN2_OV_RES) },
> > + { .n = "bd70528-dcin2-ov-det", .h =
> > BD_IRQ_HND(DCIN2_OV_DET) },
> > + { .n = "bd70528-dcin2-removed", .h =
> > BD_IRQ_HND(DCIN2_RMV) },
> > + { .n = "bd70528-dcin2-detected", .h =
> > BD_IRQ_HND(DCIN2_DET) },
> > + { .n = "bd70528-dcin1-removed", .h =
> > BD_IRQ_HND(DCIN1_RMV) },
> > + { .n = "bd70528-dcin1-detected", .h =
> > BD_IRQ_HND(DCIN1_DET) },
> > + };
>
> Please also make it static. That will move the whole thing to
> read-only (because of const) data section. This improves the
> security and the required cpu time at the same time (no need
> to copy values to the stack).
Ok. I see your point and it sounds reasonable.
> But this can be changed later, so no need to block the whole
> patchset just because of this. If Lee wants to merge this for
> 5.2, that would be fine with me. But please add it directly in
> a new patch revision if the patch does not make it into 5.2.
It would be great to get this in, it has been respinned quite a few
times already... I hope Lee takes the series in when he's back from his
leave - but it is not a problem for me to change this with later patch
(or change this in the series if it still needs to be reworked).
Br,
Matti Vaittinen
next prev parent reply other threads:[~2019-05-03 5:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 9:11 [PATCH v14 0/8] support ROHM BD70528 PMIC Matti Vaittinen
2019-05-02 9:12 ` [PATCH v14 1/8] mfd: regulator: clk: split rohm-bd718x7.h Matti Vaittinen
2019-05-02 9:13 ` [PATCH v14 2/8] mfd: bd70528: Support ROHM bd70528 PMIC - core Matti Vaittinen
2019-05-08 11:24 ` Lee Jones
2019-05-02 9:13 ` [PATCH v14 3/8] clk: bd718x7: Support ROHM BD70528 clk block Matti Vaittinen
2019-05-02 9:14 ` [PATCH v14 4/8] dt-bindings: mfd: Document first ROHM BD70528 bindings Matti Vaittinen
2019-05-08 11:25 ` Lee Jones
2019-05-02 9:15 ` [PATCH v14 5/8] gpio: Initial support for ROHM bd70528 GPIO block Matti Vaittinen
2019-05-02 9:15 ` [PATCH v14 6/8] rtc: bd70528: Initial support for ROHM bd70528 RTC Matti Vaittinen
2019-05-02 9:17 ` [PATCH v14 7/8] power: supply: Initial support for ROHM BD70528 PMIC charger block Matti Vaittinen
2019-05-02 19:50 ` Sebastian Reichel
2019-05-03 5:29 ` Vaittinen, Matti [this message]
2019-05-02 9:17 ` [PATCH v14 8/8] watchdog: bd70528: Initial support for ROHM BD70528 watchdog block Matti Vaittinen
2019-05-21 11:01 ` [PATCH v14 0/8] support ROHM BD70528 PMIC Vaittinen, Matti
2019-05-21 11:41 ` Alexandre Belloni
2019-05-21 12:24 ` Vaittinen, Matti
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=322fa765ddd72972aba931c706657661ca685afa.camel@fi.rohmeurope.com \
--to=matti.vaittinen@fi.rohmeurope.com \
--cc=Heikki.Haikola@fi.rohmeurope.com \
--cc=Mikko.Mutanen@fi.rohmeurope.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=mazziesaccount@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=wim@linux-watchdog.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).