[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5192017D.6060108@ti.com>
Date: Tue, 14 May 2013 14:48:53 +0530
From: Kishon Vijay Abraham I <kishon@...com>
To: Mark Brown <broonie@...nel.org>, <gg@...mlogic.co.uk>
CC: <myungjoo.ham@...sung.com>, <cw00.choi@...sung.com>,
<balbi@...com>, <ldewangan@...dia.com>,
<devicetree-discuss@...ts.ozlabs.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <grant.likely@...aro.org>,
<rob.herring@...xeda.com>, <rob@...dley.net>, <ruchika@...com>,
<tony@...mide.com>, <sameo@...ux.intel.com>
Subject: Re: [PATCH v4] extcon: Palmas Extcon Driver
On Tuesday 07 May 2013 04:15 PM, Mark Brown wrote:
> On Tue, May 07, 2013 at 03:17:08PM +0530, Kishon Vijay Abraham I wrote:
>> On Tuesday 07 May 2013 01:28 PM, Mark Brown wrote:
>
>>>> The platform can provide it's own vbus control in which case this is
>>>> not needed.
>
>>> So why is there no interaction with this external VBUS control and how
>>> does the driver distinguish between that and an error getting the
>>> regulator?
>
>> The platform specifies if it provides its own VBUS control by the dt
>> property ti,no_control_vbus. So the driver will give an error only
>> when *ti,no_control_vbus* is not set. Graeme?
>
> That doesn't answer the question about why there's no interaction with
> the external control...
>
Graeme?
-Kishon
--
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