From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "olof@lixom.net" <olof@lixom.net>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 0/3] ARM: dt: tegra: cardhu: add entry for regulators
Date: Thu, 9 Aug 2012 16:24:56 +0530 [thread overview]
Message-ID: <50239700.5020401@nvidia.com> (raw)
In-Reply-To: <50229F6C.10802@wwwdotorg.org>
On Wednesday 08 August 2012 10:48 PM, Stephen Warren wrote:
> 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
>
This is noise from driver. The vmbch entries are optional as per
document and so should not throw warning. Either fix will go to driver
or with documentation file and then on DT. Will work on this as
independent patch, atleast not with this series.
> 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
>
The sdhci node take the gpio as power-gpio and conflict with this
regulator gpio. I dropped the vdd_sdmmc1 as sdhci driver need to change
accordingly to handle deferred probe.
Will add registration of that file later.
> ... 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.
The issue is comment was not closed. Fixed it in next patch.
> 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.
I fixed as per above details and did not observe any failure on my testing.
next prev parent reply other threads:[~2012-08-09 11:10 UTC|newest]
Thread overview: 9+ 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 ` [PATCH 1/3] ARM: dt: tegra: cardhu: add entry for PMIC TPS65911 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 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 17:18 ` [PATCH 0/3] ARM: dt: tegra: cardhu: add entry for regulators Stephen Warren
2012-08-09 10:54 ` Laxman Dewangan [this message]
2012-08-08 17:28 ` Stephen Warren
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=50239700.5020401@nvidia.com \
--to=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 \
--cc=swarren@wwwdotorg.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