lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52AAA80A.7010905@nvidia.com>
Date:	Fri, 13 Dec 2013 11:54:10 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Stephen Warren <swarren@...dotorg.org>
CC:	"thierry.reding@...il.com" <thierry.reding@...il.com>,
	"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] ARM: tegra: enable ams AS3722 drivers

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

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ