From: Mike Looijmans <mike.looijmans@topic.nl>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add ltc3562 voltage regulator driver
Date: Thu, 30 Oct 2014 11:53:37 +0100 [thread overview]
Message-ID: <545218B1.8030306@topic.nl> (raw)
In-Reply-To: <5452131F.9000307@topic.nl>
On 10/30/2014 11:29 AM, Mike Looijmans wrote:
> On 10/30/2014 11:15 AM, Mark Brown wrote:
>> On Thu, Oct 30, 2014 at 07:47:44AM +0100, Mike Looijmans wrote:
>>> On 10/29/2014 01:30 PM, Mark Brown wrote:
>>
>>>> A couple of problems here:
>>
>>>> - This contains DT code but no DT bindings documentation; the binding
>>>> documentation is mandatory for any new bindings.
>>
>>> Should I submit a new patch to add the DT bindings and CC to the dt mailing
>>> list, or do you want it included in this patch? I was basically waiting for
>>> feedback on the driver first.
>>
>> I'm not going to review a driver with bindings without those bindings
>> being documented, it's a well documented requirement and apart from
>> anything else it's not really possible to review the code that manages
>> the bindings without seeing the bindings.
>>
>>> The "default voltage" may not be device specific, but regulator.txt doesn't
>>> have a property that describes what we needed here, because we can't get
>>> away with specifying min=max as fixed-regulator does. We also cannot assume
>>> that default=min or default=max, because that might harm hardware connected
>>> to the other side of the IO bank.
>>
>> No, if you need a generic property add it in the generic code rather
>> than just hacking a device specific property into your driver.
>
> So I should add "regulator-default-voltage" to the generic code? That would
> indeed be better than trying to do it into this driver.
>
> But would that need a separate patch for regulator core to add the property?
Hmm, I looked into doing that, but that isn't trivial, and too many devices
will suffer.
Since default-voltage is unacceptable, I will remove it from the ltc3562
driver and just use the min==max setting in the devicetree to reach the same
effect. The driver that will match IO voltages between SOM and carrier is far
from being ready for submission anyway.
I'll submit a v2 patch with all these things reworked soon.
Mike.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax: (+31) (0) 499 33 69 70
E-mail: mike.looijmans@topic.nl
Website: www.topic.nl
Please consider the environment before printing this e-mail
Topic zoekt gedreven (embedded) software specialisten!
http://topic.nl/vacatures/topic-zoekt-software-engineers/
next prev parent reply other threads:[~2014-10-30 10:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 8:15 Add ltc3562 voltage regulator driver Mike Looijmans
2014-10-29 8:16 ` [PATCH] " Mike Looijmans
2014-10-29 12:30 ` Mark Brown
2014-10-30 6:47 ` Mike Looijmans
2014-10-30 10:15 ` Mark Brown
2014-10-30 10:29 ` Mike Looijmans
2014-10-30 10:53 ` Mike Looijmans [this message]
2014-10-30 10:58 ` Mark Brown
2014-10-30 11:31 ` Mike Looijmans
2014-10-30 12:04 ` Mark Brown
2014-10-30 11:26 ` [PATCH v2] " Mike Looijmans
2014-10-30 16:51 ` Mark Brown
2014-10-31 14:07 ` Mike Looijmans
2014-10-31 18:17 ` Mark Brown
2014-11-03 8:10 ` Mike Looijmans
2014-11-03 12:09 ` Mark Brown
2014-11-03 14:48 ` Mike Looijmans
2014-11-03 15:10 ` Mark Brown
2014-11-03 17:38 ` Mike Looijmans
2014-11-04 8:55 ` Mike Looijmans
2014-11-04 11:34 ` Mark Brown
2014-11-04 12:47 ` Mike Looijmans
2014-11-04 13:35 ` Mike Looijmans
2014-11-04 19:47 ` Mark Brown
2014-11-05 9:06 ` Krzysztof Kozlowski
2014-11-05 11:45 ` Mike Looijmans
2014-11-04 6:50 ` [PATCH v3] " Mike Looijmans
2014-11-04 20:26 ` Mark Brown
2014-11-05 11:41 ` Mike Looijmans
2014-11-05 13:34 ` Mark Brown
2014-10-29 10:03 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545218B1.8030306@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).