From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: tegra: enable ams AS3722 drivers
Date: Fri, 13 Dec 2013 11:54:10 +0530 [thread overview]
Message-ID: <52AAA80A.7010905@nvidia.com> (raw)
In-Reply-To: <52AA2FD1.3020000@wwwdotorg.org>
On Friday 13 December 2013 03:21 AM, Stephen Warren wrote:
> On 12/12/2013 02:20 PM, Stephen Warren wrote:
>> On 12/12/2013 06:31 AM, Laxman Dewangan wrote:
>>> ams AS3722 is the system power manager module IC for the Tegra124 based
>>> Venice2 platform. Enable configs for gpio, pincontrol, rtc, regulator
>>> support from this device.
>> I've squashed patch 1/2 into Tegra's for-3.14/defconfig branch.
>>
>> I've applied patch 2/2 to Tegra's for-3.14/dt branch.
> Actually, I'm dropping patch 2/2 since it causes a whole bunch of error
> spew during boot:
>
>> [ 0.628315] tegra124-pinctrl 70000868.pinmux: invalid group "dap2_dout_pp2" for function "rsvd4"
>> [ 0.635309] tegra124-pinctrl 70000868.pinmux: does not have pin group dap2_dout_pp2
>> [ 0.642999] tegra124-pinctrl 70000868.pinmux: could not map group config for "dap2_dout_pp2"
>> [ 0.731176] as3722-pinctrl as3722-pinctrl: pin gpio0 already requested by as3722-pinctrl; cannot claim for as3722-regulator
>> [ 0.742312] as3722-pinctrl as3722-pinctrl: pin-0 (as3722-regulator) status -22
>> [ 0.749526] as3722-pinctrl as3722-pinctrl: could not request pin 0 (gpio0) from group gpio0 on device as3722-pinctrl
>> [ 0.760133] as3722-regulator as3722-regulator: Error applying setting, reverse things back
>> [ 0.835838] as3722-regulator as3722-regulator: Failed to find supply vin-ldo1-6
>> [ 0.843312] as3722-regulator as3722-regulator: regulator 8 register failed -517
>> [ 0.852263] platform as3722-regulator: Driver as3722-regulator requests probe deferral
>> [ 0.984920] as3722-pinctrl as3722-pinctrl: pin gpio0 already requested by as3722-pinctrl; cannot claim for as3722-rtc
>> [ 0.995537] as3722-pinctrl as3722-pinctrl: pin-0 (as3722-rtc) status -22
>> [ 1.002244] as3722-pinctrl as3722-pinctrl: could not request pin 0 (gpio0) from group gpio0 on device as3722-pinctrl
>> [ 1.012848] as3722-rtc as3722-rtc: Error applying setting, reverse things back
I did not observe this issue in my log, probably overlooked.
I will repro this and fix/update the issue/patch.
Thanks,
laxman
prev parent reply other threads:[~2013-12-13 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 13:31 [PATCH 1/2] ARM: tegra: enable ams AS3722 drivers Laxman Dewangan
2013-12-12 13:31 ` [PATCH 2/2] ARM: tegra: add ams AS3722 device to Venice2 DT Laxman Dewangan
2013-12-12 21:20 ` [PATCH 1/2] ARM: tegra: enable ams AS3722 drivers Stephen Warren
2013-12-12 21:51 ` Stephen Warren
2013-12-13 6:24 ` 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=52AAA80A.7010905@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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