From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFT 0/4] mfd: regulator: max14577: Remove support for platform data
Date: Mon, 27 Feb 2017 16:52:36 +0100 [thread overview]
Message-ID: <4868995.DGOuKygKvi@amdc3058> (raw)
In-Reply-To: <CAJKOXPcWeZ_igNu517_BmZsykhmhzrStmBy9oqRZga5=BSKhBw@mail.gmail.com>
On Monday, February 27, 2017 05:32:37 PM Krzysztof Kozlowski wrote:
> On Mon, Feb 27, 2017 at 2:55 PM, Bartlomiej Zolnierkiewicz
> <b.zolnierkie@samsung.com> wrote:
> >
> > Hi,
> >
> > On Friday, February 17, 2017 10:01:56 PM Krzysztof Kozlowski wrote:
> >> Hi,
> >>
> >> Minor cleanup of max14577 family of drivers. The dependency inside:
> >> 1. Patch #3 and #4 depends for safeness on #1 so no one would try to
> >> run the driver on non-DT platform (such platform does not exist anyway...).
> >> 2. Patch #4 depends on patch #3 (compile time dependency).
> >>
> >> Unfortunately I do not have the boards using these drivers, so testing
> >> would be appreciated.
> >
> > Your patchset looks fine to me but I've noticed that
> > maxim,max14577 bindings are not used currently in
> > the mainline kernel.
> >
> > AFAIK MAX14577 support is needed only for Gear1 board
> > which doesn't have DTS file in the upstream kernel
> > (moreover Exynos4212 SoC support has been removed
> > recently).
> >
> > It seems that MAX14577 support should also go away
> > (unless there are some other boards using it that we
> > support in the mainline kernel).
>
> The driver supports two chipsets: max14577 and max77836. As you noted,
> the first one is for Gear 1. The second one is present on Gear2 which
> is supported by mainline. Simplifying the driver to support only
> max77836 would be a task requiring testing. I think review would be in
> such case not enough.
I think that this shouldn't be a big problem (if no one
else volunteers we can do the testing on Gear2 device).
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2017-02-27 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170217200214epcas3p4d72abd10d1ce7dbbbcd626bcf452fa37@epcas3p4.samsung.com>
2017-02-17 20:01 ` [RFT 0/4] mfd: regulator: max14577: Remove support for platform data Krzysztof Kozlowski
2017-02-17 20:01 ` [RFT 1/4] mfd: max14577: Explicitly depend on OF Krzysztof Kozlowski
2017-02-17 20:01 ` [RFT 2/4] mfd: max14577: Export OF module alias information Krzysztof Kozlowski
2017-02-17 20:01 ` [RFT 3/4] regulator: max14577: Remove support for platform data Krzysztof Kozlowski
2017-02-18 0:02 ` Mark Brown
2017-02-17 20:02 ` [RFT 4/4] mfd: max14577: Remove platform data and instantiation from I2C Krzysztof Kozlowski
2017-02-27 12:55 ` [RFT 0/4] mfd: regulator: max14577: Remove support for platform data Bartlomiej Zolnierkiewicz
2017-02-27 15:32 ` Krzysztof Kozlowski
2017-02-27 15:52 ` Bartlomiej Zolnierkiewicz [this message]
2017-02-28 9:47 ` Mark Brown
2017-02-28 11:34 ` Bartlomiej Zolnierkiewicz
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=4868995.DGOuKygKvi@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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