[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131211225116.GC11044@sirena.org.uk>
Date: Wed, 11 Dec 2013 22:51:16 +0000
From: Mark Brown <broonie@...nel.org>
To: Krzysztof Kozlowski <k.kozlowski@...sung.com>
Cc: Sangbeom Kim <sbkim73@...sung.com>,
Liam Girdwood <lgirdwood@...il.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
Jiri Kosina <trivial@...nel.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Kyungmin Park <kyungmin.park@...sung.com>,
Marek Szyprowski <m.szyprowski@...sung.com>
Subject: Re: [PATCH 2/2] regulator: s5m8767: Fix driver probe fail on BUCK7/8
regulators
On Tue, Dec 10, 2013 at 10:09:43AM +0100, Krzysztof Kozlowski wrote:
> The BUCK7 and BUCK8 were not supported by s5m8767 driver. If they were
> configured in DTS then the driver probing would fail with EINVAL:
> [ 0.288474] VCC_SUB_1.35V: failed to apply 1350000uV constraint
> [ 0.288671] s5m8767-pmic s5m8767-pmic: regulator init failed for 35
> [ 0.294931] s5m8767-pmic: probe of s5m8767-pmic failed with error -22
> This patch adds support for BUCK7 and BUCK8 regulators using standard
> regmap get/set voltage sel functions.
I've applied these but this changelog doesn't entirely add up so I
rewrote it a bit. The patch is implementing the get and set voltage
operations, the regulators were actually supported. The errors were
being caused by the DT attempting to set the voltage for a fixed voltage
regulator which obviously won't work - I suspect that the DTs might not
be ideal, it seems common to overspecify voltages in DTs for some
reason.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists