From: Nishanth Menon <nm@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: ti-abb: Add support for interleaved LDO registers
Date: Fri, 17 Jan 2014 12:11:44 -0600 [thread overview]
Message-ID: <52D97260.1010304@ti.com> (raw)
In-Reply-To: <20140117180015.GA17314@sirena.org.uk>
On 01/17/2014 12:00 PM, Mark Brown wrote:
> On Fri, Jan 17, 2014 at 10:47:29AM -0600, Nishanth Menon wrote:
>> On 01/17/2014 10:08 AM, Mark Brown wrote:
>
>>> Is there a system controller involved here by any chance?
>
>> Nope. ABB LDO module is a standalone instance whose register set
>> happens to be part of a memory range, as I recently got to know, is a
>> favorite for our hardware designers to put "misc" modules at SoC
>> integration time - Sigh! I guess I have made more than enough stink
>> about this internally already :(.
>
> That sounds exactly like a system controller :)
Hmm.. I have considered something like PRCM in OMAP as a system
controller... anyways.. I think I miss your suggestion here. Is there
something you might suggest to improve in the patch or take an
alternative route?
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: ti-abb: Add support for interleaved LDO registers
Date: Fri, 17 Jan 2014 12:11:44 -0600 [thread overview]
Message-ID: <52D97260.1010304@ti.com> (raw)
In-Reply-To: <20140117180015.GA17314@sirena.org.uk>
On 01/17/2014 12:00 PM, Mark Brown wrote:
> On Fri, Jan 17, 2014 at 10:47:29AM -0600, Nishanth Menon wrote:
>> On 01/17/2014 10:08 AM, Mark Brown wrote:
>
>>> Is there a system controller involved here by any chance?
>
>> Nope. ABB LDO module is a standalone instance whose register set
>> happens to be part of a memory range, as I recently got to know, is a
>> favorite for our hardware designers to put "misc" modules at SoC
>> integration time - Sigh! I guess I have made more than enough stink
>> about this internally already :(.
>
> That sounds exactly like a system controller :)
Hmm.. I have considered something like PRCM in OMAP as a system
controller... anyways.. I think I miss your suggestion here. Is there
something you might suggest to improve in the patch or take an
alternative route?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-01-17 18:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 19:32 [PATCH] regulator: ti-abb: Add support for interleaved LDO registers Nishanth Menon
2014-01-16 19:32 ` Nishanth Menon
2014-01-17 16:08 ` Mark Brown
2014-01-17 16:47 ` Nishanth Menon
2014-01-17 16:47 ` Nishanth Menon
2014-01-17 18:00 ` Mark Brown
2014-01-17 18:11 ` Nishanth Menon [this message]
2014-01-17 18:11 ` Nishanth Menon
2014-01-17 18:38 ` Mark Brown
2014-01-21 18:55 ` Mark Brown
2014-01-21 20:06 ` Nishanth Menon
2014-01-21 20:06 ` Nishanth Menon
2014-01-21 21:56 ` Mark Brown
2014-01-21 22:32 ` Nishanth Menon
2014-01-21 22:32 ` Nishanth Menon
2014-01-22 20:19 ` Mark Brown
2014-01-22 20:48 ` Nishanth Menon
2014-01-22 20:48 ` Nishanth Menon
2014-01-22 22:25 ` Nishanth Menon
2014-01-22 22:25 ` Nishanth Menon
2014-01-23 12:29 ` Mark Brown
2014-01-23 16:20 ` Nishanth Menon
2014-01-23 16:20 ` Nishanth Menon
2014-01-23 16:26 ` Nishanth Menon
2014-01-23 16:26 ` Nishanth Menon
2014-01-23 16:34 ` Mark Brown
2014-01-23 17:57 ` [PATCH V4] " Nishanth Menon
2014-01-23 17:57 ` Nishanth Menon
2014-01-27 19:34 ` 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=52D97260.1010304@ti.com \
--to=nm@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.