From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: olof@lixom.net, linux@arm.linux.org.uk,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: dt: tegra: cardhu: add entry for regulators
Date: Wed, 08 Aug 2012 11:18:36 -0600 [thread overview]
Message-ID: <50229F6C.10802@wwwdotorg.org> (raw)
In-Reply-To: <1344408527-32051-1-git-send-email-ldewangan@nvidia.com>
On 08/08/2012 12:48 AM, Laxman Dewangan wrote:
> This patch series add the PMIC and fixed regulators for
> cardhu board. There is multiple versions of cardhu baord named
> as A01, A02, A03..and so on. Cardhu A01 and A03 are not supported.
> Cardhu A02 and A04 have different sets of GPIO for regualtors.
> The cardhu A04 is compatible for A05, A06 and A07 in GPIOs.
> This patch series split the cardhu dts file to cardhu-a02 and
> carchu-a04 and then add entry for different fixed regualtors.
With this series, I see the following warnings:
tps65910 4-002d: VMBCH-Threshold not specified
tps65910 4-002d: VMBCH2-Threshold not specified
I also see the following error:
vdd_sdmmc1: Failed to request enable GPIO31: -16
reg-fixed-voltage c.regulator: Failed to register regulator: -16
reg-fixed-voltage: probe of c.regulator failed with error -16
... because both the existing SDHCI node and the new "vdd_sdmmc1_reg:
regulator@12" node both use the same GPIO.
I also don't see "pex_hvdd_3v3_reg: regulator@5" being created, for
reasons I haven't tracked down.
Note that I have a Cardhu A02, although all the issues are with
regulators in the common file.
Can you please fix these, roll in the fixes for the board ID comment
issues I mentioned before, retest to ensure there are no errors and that
all regulators get created as expected, and resubmit.
Thanks.
next prev parent reply other threads:[~2012-08-08 17:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 6:48 [PATCH 0/3] ARM: dt: tegra: cardhu: add entry for regulators Laxman Dewangan
2012-08-08 6:48 ` Laxman Dewangan
2012-08-08 6:48 ` [PATCH 1/3] ARM: dt: tegra: cardhu: add entry for PMIC TPS65911 Laxman Dewangan
2012-08-08 6:48 ` Laxman Dewangan
2012-08-08 6:48 ` [PATCH 2/3] ARM: dt: tegra: cardhu: split dts file for support multiple board versions Laxman Dewangan
2012-08-08 6:48 ` Laxman Dewangan
[not found] ` <1344408527-32051-3-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-08 16:30 ` Stephen Warren
2012-08-08 16:30 ` Stephen Warren
2012-08-08 6:48 ` [PATCH 3/3] ARM: tegra: cardhu: add dt entry for fixed regulators Laxman Dewangan
2012-08-08 6:48 ` Laxman Dewangan
2012-08-08 17:18 ` Stephen Warren [this message]
[not found] ` <50229F6C.10802-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-09 10:54 ` [PATCH 0/3] ARM: dt: tegra: cardhu: add entry for regulators Laxman Dewangan
2012-08-09 10:54 ` Laxman Dewangan
[not found] ` <1344408527-32051-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-08 17:28 ` Stephen Warren
2012-08-08 17:28 ` Stephen Warren
[not found] ` <5022A1DA.5000203-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-09 10:59 ` Laxman Dewangan
2012-08-09 10:59 ` Laxman Dewangan
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=50229F6C.10802@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
/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.