[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOesGMiMiqk1mKcVF8SwePhUS-8cAmM3Ut3f+qRvjz27iw7CTA@mail.gmail.com>
Date: Thu, 1 May 2014 11:17:58 -0700
From: Olof Johansson <olof@...om.net>
To: Doug Anderson <dianders@...omium.org>
Cc: Lee Jones <lee.jones@...aro.org>, Mark Brown <broonie@...nel.org>,
Anton Vorontsov <anton@...msg.org>,
Sachin Kamat <sachin.kamat@...aro.org>,
AJAY KUMAR RAMAKRISHNA SHYMALAMMA <ajaykumar.rs@...sung.com>,
linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
Simon Glass <sjg@...omium.org>,
Michael Spang <spang@...omium.org>,
Sean Paul <seanpaul@...omium.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Randy Dunlap <rdunlap@...radead.org>,
Liam Girdwood <lgirdwood@...il.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Stephen Warren <swarren@...dotorg.org>
Subject: Re: [PATCH v3 4/5] regulator: tps65090: Allow setting the overcurrent
wait time
Lee, Doug,
I've bisected a boot failure on Tegra Dalmore (which has a tps65090)
down to this patch. It started in -next 0501, so I guess Lee might
have pushed some patches out now even though the commit date is a
little while back?
The commit is:
commit 60e91b51b515b20f85697fcd397911fdb97bbdca
Author: Doug Anderson <dianders@...omium.org>
AuthorDate: Wed Apr 16 16:12:28 2014 -0700
Commit: Lee Jones <lee.jones@...aro.org>
CommitDate: Wed Apr 23 12:34:01 2014 +0100
regulator: tps65090: Allow setting the overcurrent wait time
The tps65090 regulator allows you to specify how long you want it to
wait before detecting an overcurrent condition. Allow specifying that
through the device tree (or through platform data).
Signed-off-by: Doug Anderson <dianders@...omium.org>
Acked-by: Simon Glass <sjg@...omium.org>
Acked-by: Michael Spang <spang@...omium.org>
Acked-by: Sean Paul <seanpaul@...omium.org>
Acked-by: Mark Brown <broonie@...nel.org>
Signed-off-by: Lee Jones <lee.jones@...aro.org>
Panic is line 309:
303 for (num = 0; num < TPS65090_REGULATOR_MAX; num++) {
304 tps_pdata = tps65090_pdata->reg_pdata[num];
305
306 ri = &pmic[num];
307 ri->dev = &pdev->dev;
308 ri->desc = &tps65090_regulator_desc[num];
309 ri->overcurrent_wait_valid =
tps_pdata->overcurrent_wait_valid;
310 ri->overcurrent_wait = tps_pdata->overcurrent_wait;
so it looks like tps_pdata is NULL. Should likely be a check for it?
-Olof
On Wed, Apr 23, 2014 at 8:48 AM, Doug Anderson <dianders@...omium.org> wrote:
> Lee,
>
> On Wed, Apr 23, 2014 at 4:51 AM, Lee Jones <lee.jones@...aro.org> wrote:
>>> The tps65090 regulator allows you to specify how long you want it to
>>> wait before detecting an overcurrent condition. Allow specifying that
>>> through the device tree (or through platform data).
>>>
>>> Signed-off-by: Doug Anderson <dianders@...omium.org>
>>> Signed-off-by: Simon Glass <sjg@...omium.org>
>>> Signed-off-by: Michael Spang <spang@...omium.org>
>>> Signed-off-by: Sean Paul <seanpaul@...omium.org>
>>> ---
>>> Changes in v3:
>>> - Fixed kernel-doc notation for return
>>>
>>> Changes in v2:
>>> - Separated the overcurrent and retries changes into two patches.
>>> - Now set overcurrent at probe time since it doesn't change.
>>>
>>> .../devicetree/bindings/regulator/tps65090.txt | 4 ++
>>> drivers/regulator/tps65090-regulator.c | 56 ++++++++++++++++++++++
>>> include/linux/mfd/tps65090.h | 5 ++
>>> 3 files changed, 65 insertions(+)
>>
>> Applied, thanks.
>
> Ummmm, Mark said that he had already applied this patch to his tree (I
> mentioned it in my recent summary and you can see it in this thread
> too). I don't see it on git.kernel.org though
> <https://git.kernel.org/cgit/linux/kernel/git/broonie/regulator.git/log/?h=for-next>
>
> I'm worried this will cause a merge conflict if you both apply it.
>
> -Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists