From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"andrei.stefanescu@microchip.com"
<andrei.stefanescu@microchip.com>,
"heiko@sntech.de" <heiko@sntech.de>,
"rafael@kernel.org" <rafael@kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"brendanhiggins@google.com" <brendanhiggins@google.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"kholk11@gmail.com" <kholk11@gmail.com>,
"hsin-hsiung.wang@mediatek.com" <hsin-hsiung.wang@mediatek.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"axel.lin@ingics.com" <axel.lin@ingics.com>,
"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"krzk@kernel.org" <krzk@kernel.org>,
"m.reichl@fivetechno.de" <m.reichl@fivetechno.de>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"wens@csie.org" <wens@csie.org>,
"andreas@kemnade.info" <andreas@kemnade.info>,
"agross@kernel.org" <agross@kernel.org>,
"Laine, Markus" <Markus.Laine@fi.rohmeurope.com>,
"Adam.Thomson.Opensource@diasemi.com"
<Adam.Thomson.Opensource@diasemi.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"mazziesaccount@gmail.com" <mazziesaccount@gmail.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"rf@opensource.cirrus.com" <rf@opensource.cirrus.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"sre@kernel.org" <sre@kernel.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"support.opensource@diasemi.com" <support.opensource@diasemi.com>,
"baolin.wang@linaro.org" <baolin.wang@linaro.org>,
"sbkim73@samsung.com" <sbkim73@samsung.com>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Mutanen, Mikko" <Mikko.Mutanen@fi.rohmeurope.com>,
"b.zolnierkie@samsung.com" <b.zolnierkie@samsung.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v8 00/10] Support ROHM BD99954 charger IC
Date: Fri, 3 Apr 2020 14:02:10 +0300 [thread overview]
Message-ID: <20200403110210.GO1922688@smile.fi.intel.com> (raw)
In-Reply-To: <50797a6ac6cda4647f9a396dab0ad08017e3138b.camel@fi.rohmeurope.com>
On Fri, Apr 03, 2020 at 10:07:41AM +0000, Vaittinen, Matti wrote:
> On Fri, 2020-04-03 at 11:36 +0300, Matti Vaittinen wrote:
> > Support ROHM BD99954 Battery Management IC
> >
> > ROHM BD99954 is a Battery Management IC for 1-4 cell Lithium-Ion
> > secondary battery. BD99954 is intended to be used in space-constraint
> > equipment such as Low profile Notebook PC, Tablets and other
> > applications.
> >
> > Series extracts a "linear ranges" helper out of the regulator
> > framework. Linear ranges helper is intended to help converting
> > real-world values to register values when conversion is linear. I
> > suspect this is useful also for power subsystem and possibly for clk.
>
> I see Mark has acked/reviewed both the regulator changes and
> linear_ranges code. Do you think Mark should take the linear_ranges and
> regulator changes in his tree? I don't know Sebastian's schedule or
> when the charger portion is good to go - but I know that each new
> regulator driver which is added to regulator tree has a chance of using
> the struct regulator_linear_range - which will break when this series
> is applied. Or what would be the best way to avoid breaking regulators?
>
> OTOH, if Mark takes linear_ranges in his tree, then this power portion
> of the series will depend on linear_ranges stuff that is in regulator
> tree. I guess this must be pretty standard stuff for you and you
> probably know how to handle it but I just wanted to point out the risk
> of breaking regulator build without visible merge conflicts.
>
> Please let me know if I should split the series and rebase
> linear_ranges / regulator stuff on top of regulator tree.
From my point of view, you need to wait till rc1 is out and rebase the series.
The cross-subsystem changes can be handled by maintainers in a form of
immutable branches / tags. On your side you may recommend them how to proceed,
but the final decision is by them.
--
With Best Regards,
Andy Shevchenko
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
"andrei.stefanescu@microchip.com"
<andrei.stefanescu@microchip.com>,
"heiko@sntech.de" <heiko@sntech.de>,
"rafael@kernel.org" <rafael@kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"brendanhiggins@google.com" <brendanhiggins@google.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"kholk11@gmail.com" <kholk11@gmail.com>,
"hsin-hsiung.wang@mediatek.com" <hsin-hsiung.wang@mediatek.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"axel.lin@ingics.com" <axel.lin@ingics.com>,
"gregory.clement@bootlin.com" <gregory.clement@bootlin.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"krzk@kernel.org" <krzk@kernel.org>,
"m.reichl@fivetechno.de" <m.reichl@fivetechno.de>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
"wens@csie.org" <wens@csie.org>,
"andreas@kemnade.info" <andreas@kemnade.info>,
"agross@kernel.org" <agross@kernel.org>,
"Laine, Markus" <Markus.Laine@fi.rohmeurope.com>,
"Adam.Thomson.Opensource@diasemi.com"
<Adam.Thomson.Opensource@diasemi.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"ckeepax@opensource.cirrus.com" <ckeepax@opensource.cirrus.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"mazziesaccount@gmail.com" <mazziesaccount@gmail.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"rf@opensource.cirrus.com" <rf@opensource.cirrus.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"sre@kernel.org" <sre@kernel.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"support.opensource@diasemi.com" <support.opensource@diasemi.com>,
"baolin.wang@linaro.org" <baolin.wang@linaro.org>,
"sbkim73@samsung.com" <sbkim73@samsung.com>,
"patches@opensource.cirrus.com" <patches@opensource.cirrus.com>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Mutanen, Mikko" <Mikko.Mutanen@fi.rohmeurope.com>,
"b.zolnierkie@samsung.com" <b.zolnierkie@samsung.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v8 00/10] Support ROHM BD99954 charger IC
Date: Fri, 3 Apr 2020 14:02:10 +0300 [thread overview]
Message-ID: <20200403110210.GO1922688@smile.fi.intel.com> (raw)
In-Reply-To: <50797a6ac6cda4647f9a396dab0ad08017e3138b.camel@fi.rohmeurope.com>
On Fri, Apr 03, 2020 at 10:07:41AM +0000, Vaittinen, Matti wrote:
> On Fri, 2020-04-03 at 11:36 +0300, Matti Vaittinen wrote:
> > Support ROHM BD99954 Battery Management IC
> >
> > ROHM BD99954 is a Battery Management IC for 1-4 cell Lithium-Ion
> > secondary battery. BD99954 is intended to be used in space-constraint
> > equipment such as Low profile Notebook PC, Tablets and other
> > applications.
> >
> > Series extracts a "linear ranges" helper out of the regulator
> > framework. Linear ranges helper is intended to help converting
> > real-world values to register values when conversion is linear. I
> > suspect this is useful also for power subsystem and possibly for clk.
>
> I see Mark has acked/reviewed both the regulator changes and
> linear_ranges code. Do you think Mark should take the linear_ranges and
> regulator changes in his tree? I don't know Sebastian's schedule or
> when the charger portion is good to go - but I know that each new
> regulator driver which is added to regulator tree has a chance of using
> the struct regulator_linear_range - which will break when this series
> is applied. Or what would be the best way to avoid breaking regulators?
>
> OTOH, if Mark takes linear_ranges in his tree, then this power portion
> of the series will depend on linear_ranges stuff that is in regulator
> tree. I guess this must be pretty standard stuff for you and you
> probably know how to handle it but I just wanted to point out the risk
> of breaking regulator build without visible merge conflicts.
>
> Please let me know if I should split the series and rebase
> linear_ranges / regulator stuff on top of regulator tree.
From my point of view, you need to wait till rc1 is out and rebase the series.
The cross-subsystem changes can be handled by maintainers in a form of
immutable branches / tags. On your side you may recommend them how to proceed,
but the final decision is by them.
--
With Best Regards,
Andy Shevchenko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-03 11:02 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 8:36 [PATCH v8 00/10] Support ROHM BD99954 charger IC Matti Vaittinen
2020-04-03 8:36 ` Matti Vaittinen
2020-04-03 8:41 ` [PATCH v8 01/10] dt-bindings: battery: add new battery parameters Matti Vaittinen
2020-04-03 8:41 ` Matti Vaittinen
2020-04-05 3:28 ` Sebastian Reichel
2020-04-05 3:28 ` Sebastian Reichel
2020-04-03 8:45 ` [PATCH v8 02/10] dt_bindings: ROHM BD99954 Charger Matti Vaittinen
2020-04-03 8:45 ` Matti Vaittinen
2020-04-05 3:30 ` Sebastian Reichel
2020-04-05 3:30 ` Sebastian Reichel
2020-04-03 8:45 ` [PATCH v8 03/10] lib: add linear ranges helpers Matti Vaittinen
2020-04-03 8:45 ` Matti Vaittinen
2020-04-03 9:37 ` Andy Shevchenko
2020-04-03 9:37 ` Andy Shevchenko
2020-04-03 8:46 ` [PATCH v8 04/10] lib/test_linear_ranges: add a test for the 'linear_ranges' Matti Vaittinen
2020-04-03 8:46 ` Matti Vaittinen
2020-04-03 8:46 ` [PATCH v8 05/10] power: supply: bd70528: rename linear_range to avoid collision Matti Vaittinen
2020-04-03 8:46 ` Matti Vaittinen
2020-04-05 3:33 ` Sebastian Reichel
2020-04-05 3:33 ` Sebastian Reichel
2020-04-06 9:21 ` Vaittinen, Matti
2020-04-06 9:21 ` Vaittinen, Matti
2020-04-03 8:46 ` [PATCH v8 06/10] regulator: use linear_ranges helper Matti Vaittinen
2020-04-03 8:46 ` Matti Vaittinen
2020-04-03 8:47 ` [PATCH v8 07/10] power: supply: bd70528: use linear ranges Matti Vaittinen
2020-04-03 8:47 ` Matti Vaittinen
2020-04-05 3:37 ` Sebastian Reichel
2020-04-05 3:37 ` Sebastian Reichel
2020-04-03 8:47 ` [PATCH v8 08/10] power: supply: add battery parameters Matti Vaittinen
2020-04-03 8:47 ` Matti Vaittinen
2020-04-05 3:35 ` Sebastian Reichel
2020-04-05 3:35 ` Sebastian Reichel
2020-04-03 8:48 ` [PATCH v8 09/10] power: supply: Support ROHM bd99954 charger Matti Vaittinen
2020-04-03 8:48 ` Matti Vaittinen
2020-04-03 9:41 ` Andy Shevchenko
2020-04-03 9:41 ` Andy Shevchenko
2020-04-05 3:22 ` Sebastian Reichel
2020-04-05 3:22 ` Sebastian Reichel
2020-04-06 9:59 ` Vaittinen, Matti
2020-04-06 9:59 ` Vaittinen, Matti
2020-04-03 8:48 ` [PATCH v8 10/10] power: supply: Fix Kconfig help text indentiation Matti Vaittinen
2020-04-03 8:48 ` Matti Vaittinen
2020-04-05 3:35 ` Sebastian Reichel
2020-04-05 3:35 ` Sebastian Reichel
2020-04-03 10:07 ` [PATCH v8 00/10] Support ROHM BD99954 charger IC Vaittinen, Matti
2020-04-03 10:07 ` Vaittinen, Matti
2020-04-03 11:02 ` andriy.shevchenko [this message]
2020-04-03 11:02 ` andriy.shevchenko
2020-04-03 11:13 ` Vaittinen, Matti
2020-04-03 11:13 ` Vaittinen, Matti
2020-04-03 11:50 ` andriy.shevchenko
2020-04-03 11:50 ` andriy.shevchenko
2020-04-03 11:51 ` andriy.shevchenko
2020-04-03 11:51 ` andriy.shevchenko
2020-04-03 12:01 ` Mark Brown
2020-04-03 12:01 ` Mark Brown
2020-04-03 12:30 ` Vaittinen, Matti
2020-04-03 12:30 ` Vaittinen, Matti
2020-04-03 12:31 ` Mark Brown
2020-04-03 12:31 ` Mark Brown
2020-04-05 3:27 ` Sebastian Reichel
2020-04-05 3:27 ` Sebastian Reichel
2020-04-06 5:22 ` Vaittinen, Matti
2020-04-06 5:22 ` 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=20200403110210.GO1922688@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=Markus.Laine@fi.rohmeurope.com \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=Mikko.Mutanen@fi.rohmeurope.com \
--cc=agross@kernel.org \
--cc=andreas@kemnade.info \
--cc=andrei.stefanescu@microchip.com \
--cc=axel.lin@ingics.com \
--cc=b.zolnierkie@samsung.com \
--cc=baolin.wang@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=bjorn.andersson@linaro.org \
--cc=brendanhiggins@google.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=heiko@sntech.de \
--cc=hsin-hsiung.wang@mediatek.com \
--cc=kholk11@gmail.com \
--cc=krzk@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.reichl@fivetechno.de \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mazziesaccount@gmail.com \
--cc=patches@opensource.cirrus.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rf@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
--cc=sbkim73@samsung.com \
--cc=sre@kernel.org \
--cc=support.opensource@diasemi.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.