[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <545CF02A.9060500@collabora.co.uk>
Date: Fri, 07 Nov 2014 17:15:38 +0100
From: Javier Martinez Canillas <javier.martinez@...labora.co.uk>
To: Mark Brown <broonie@...nel.org>
CC: Kukjin Kim <kgene.kim@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Olof Johansson <olof@...om.net>,
Chris Zhong <zyw@...k-chips.com>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
Abhilash Kesavan <kesavan.abhilash@...il.com>,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v5 5/5] regulator: of: Add support for parsing initial
and suspend modes
On 11/07/2014 04:47 PM, Mark Brown wrote:
> On Fri, Nov 07, 2014 at 02:00:05PM +0100, Javier Martinez Canillas wrote:
>
>> + if (!of_property_read_u32(np, "regulator-initial-mode", &pval)) {
>> + if (desc && desc->map_modes)
>> + constraints->initial_mode = desc->map_modes(pval);
>> + else
>> + pr_warn("%s: failed to parse regulator-initial-mode\n",
>> + np->name);
>> + }
>
> This is ignoring any error return from map_modes(), it's possible the DT
> might have an invalid value. The error message could also use some
> improvement, it's more that the kernel doesn't understand how to parse
> it even if it is valid.
>
Right, as I mentioned to Krzysztof in a previous email, I'll remove the
warning message and add an error message instead if the map mode callback
function fails and also show the error code as you suggest.
Best regards,
Javier
--
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