From: Laxman Dewangan <ldewangan@nvidia.com>
To: Thierry Reding <treding@nvidia.com>
Cc: <robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <linus.walleij@linaro.org>,
<gnurou@gmail.com>, <lee.jones@linaro.org>, <broonie@kernel.org>,
<a.zummo@towertech.it>, <alexandre.belloni@free-electrons.com>,
<lgirdwood@gmail.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<rtc-linux@googlegroups.com>, <swarren@nvidia.com>,
<k.kozlowski@samsung.com>
Subject: Re: [PATCH V8 0/8] Add support for MAXIM MAX77620/MAX20024 PMIC
Date: Tue, 1 Mar 2016 17:04:16 +0530 [thread overview]
Message-ID: <56D57E38.2060804@nvidia.com> (raw)
In-Reply-To: <20160225161510.GB1903@ulmo.nvidia.com>
On Thursday 25 February 2016 09:45 PM, Thierry Reding wrote:
> On Sat, Feb 20, 2016 at 10:10:56AM +0530, Laxman Dewangan wrote:
>> On Tuesday 16 February 2016 09:30 PM, Thierry Reding wrote:
>>> On Thu, Feb 11, 2016 at 05:26:26PM +0530, Laxman Dewangan wrote:
>>>> Add SW support for MAXIM Semiconductor's Power Management
>>>> IC (PMIC) MAX77620/MAX20024. This PMIC supports DC-DC/LDOS, GPIOs,
>>>> RTC, watchdog, clocks etc.
>>> Hi Laxman,
>>>
>>> This series is starting to look pretty good. Do you have patches in the
>>> works to add the corresponding DT content for the various boards that we
>>> support? I think the Jetson TX1 patch would be most interesting since
>>> that's what people can get their hands on.
>>>
>> Yes, I am just waiting for this series to be concluded and applied. Once it
>> is done, I will immediately post the patches to enable this driver in config
>> and dt entry for the Jetson-TX1.
> Why hold back on the patches? I'm currently having trouble testing
> your stash here on Jetson TX1 and I suspect that I'm using the wrong
> device tree content (it was derived from downstream many moons ago).
> There's nothing wrong with posting patches that depend on patches on
> the list. Typically you'd note the dependency in the cover letter to
> make it easier for people to find what belongs together.
>
OK, posted patches as:
[PATCH 2/2] arm64: tegra: Jetson-TX1: Add DT entry for system PMIC MAX77620
[PATCH 1/2] arm64: tegra: Add DT entry for keys used in Jetson-TX1
[PATCH 1/1] arm64: defconfig: Enable Maxim PMIC max77620 config
Currently, the execution is crashing with this series + above patches as
MFD_CELLS are not correctly defined.
Discussion is going on with patch from Rhyland Klein
[PATCH] mfd: Fix MACRO for commonly declared MFD cell attributes
Once MFD_CELL defines get fixed, either series need to be revisit or
automatically fix the issue.
prev parent reply other threads:[~2016-03-01 11:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 11:56 [PATCH V8 0/8] Add support for MAXIM MAX77620/MAX20024 PMIC Laxman Dewangan
2016-02-11 11:56 ` [PATCH V8 1/8] mfd: add device-tree binding doc for PMIC max77620/max20024 Laxman Dewangan
2016-02-11 11:56 ` [PATCH V8 2/8] mfd: max77620: add core driver for MAX77620/MAX20024 Laxman Dewangan
2016-02-11 11:56 ` [PATCH V8 3/8] pinctrl: add DT binding doc for pincontrol of PMIC max77620/max20024 Laxman Dewangan
2016-02-15 23:16 ` Linus Walleij
2016-03-01 9:37 ` Laxman Dewangan
2016-02-11 11:56 ` [PATCH V8 4/8] pinctrl: max77620: add pincontrol driver for MAX77620/MAX20024 Laxman Dewangan
2016-02-11 11:56 ` [PATCH V8 5/8] gpio: add DT binding doc for gpio of PMIC max77620/max20024 Laxman Dewangan
2016-02-15 23:15 ` Linus Walleij
2016-02-11 11:56 ` [PATCH V8 6/8] gpio: max77620: add gpio driver for MAX77620/MAX20024 Laxman Dewangan
2016-02-15 23:18 ` Linus Walleij
2016-02-20 4:54 ` Laxman Dewangan
2016-02-11 11:56 ` [PATCH V8 7/8] regulator: add DT binding doc for regulator of PMIC max77620/max20024 Laxman Dewangan
2016-02-11 11:56 ` [PATCH V8 8/8] regulator: max77620: add regulator driver for max77620/max20024 Laxman Dewangan
2016-02-16 16:00 ` [PATCH V8 0/8] Add support for MAXIM MAX77620/MAX20024 PMIC Thierry Reding
2016-02-20 4:40 ` Laxman Dewangan
2016-02-25 16:15 ` Thierry Reding
2016-03-01 11:34 ` Laxman Dewangan [this message]
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=56D57E38.2060804@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=swarren@nvidia.com \
--cc=treding@nvidia.com \
/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).