[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <551DC94C.3060001@codeaurora.org>
Date: Thu, 02 Apr 2015 15:57:16 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Mark Brown <broonie@...nel.org>
CC: Bjorn Andersson <bjorn.andersson@...ymobile.com>,
Andy Gross <agross@...eaurora.org>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Lee Jones <lee.jones@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
Rob Herring <robh+dt@...nel.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/5] Refactor Qualcomm RPM regulator to single platform_device
On 04/02/15 15:26, Mark Brown wrote:
> On Thu, Apr 02, 2015 at 03:00:37PM -0700, Stephen Boyd wrote:
>
>> What happens with debugfs when you have multiple pmics with the same
>> named regulator? I thought that in this case we needed to make the names
>> unique somehow or we would end up with the same directory for two
>> different regulators.
> Guenther sent a patch fixing that a while back.
This one?
commit a9eaa8130707d4013fb109b80323489c0d0111ac
Author: Guenter Roeck <linux@...ck-us.net>
AuthorDate: Fri Oct 17 08:17:03 2014 -0700
Commit: Mark Brown <broonie@...nel.org>
CommitDate: Fri Mar 27 16:14:18 2015 -0700
regulator: Ensure unique regulator debugfs directory names
Ok. Seems to be only in next. I'm not sure it will work though because
in this case the parent device is the same for both regulators on
different PMICs that the RPM is controlling. I could be wrong though
because I haven't tested it.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
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