linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kishon@ti.com (Kishon Vijay Abraham I)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap5: dts: split SMPS10 dt node
Date: Fri, 16 Aug 2013 15:51:33 +0530	[thread overview]
Message-ID: <520DFD2D.9020408@ti.com> (raw)
In-Reply-To: <520DE8C1.2080406@baylibre.com>

On Friday 16 August 2013 02:24 PM, Benoit Cousson wrote:
> On 16/08/2013 07:15, Kishon Vijay Abraham I wrote:
>> Hi Benoit,
>>
>> On Tuesday 13 August 2013 08:18 PM, Benoit Cousson wrote:
>>> On 13/08/2013 16:45, Kishon Vijay Abraham I wrote:
>>>> Hi,
>>>>
>>>> On Tuesday 13 August 2013 06:51 PM, Benoit Cousson wrote:
>>>>> Hi Kishon,
>>>>>
>>>>> On 12/08/2013 11:37, Kishon Vijay Abraham I wrote:
>>>>>> SMPS10 has two outputs OUT1 and OUT2. Hence SMPS10 is modeled as
>>>>>> two regulators. The dt node is split to reflect it.
>>>>>
>>>>> Mmm, I'm curious. How is it supposed to work?
>>>>>
>>>>> Do you have dedicated control on each output?
>>>>
>>>> Yes. It can be controlled by setting different values to the same bit fields.
>>>> You can refer [1] where we actually implement SMPS10 as two different
>>>> regulators.
>>>>
>>>> [1] -> http://permalink.gmane.org/gmane.linux.kernel/1542521
>>>
>>> Great, thanks.
>>>
>>> Can we merge that one safely if the driver changed are not done yet?
>>
>> I think it shouldn't cause any issues. However Mark has already merged the
>> driver changes.
> 
> Cool. I've just applied your patch in for_3.12/dts

Thanks :-)

Regards
Kishon

      reply	other threads:[~2013-08-16 10:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12  9:37 [PATCH] arm: omap5: dts: split SMPS10 dt node Kishon Vijay Abraham I
2013-08-13 13:21 ` Benoit Cousson
2013-08-13 14:45   ` Kishon Vijay Abraham I
2013-08-13 14:48     ` Benoit Cousson
2013-08-16  5:15       ` Kishon Vijay Abraham I
2013-08-16  8:54         ` Benoit Cousson
2013-08-16 10:21           ` Kishon Vijay Abraham I [this message]

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=520DFD2D.9020408@ti.com \
    --to=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).