All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
	rtc-linux@googlegroups.com, linux-omap@vger.kernel.org,
	a.zummo@towertech.it, johan@kernel.org, tony@atomide.com,
	bcousson@baylibre.com, balbi@ti.com, akpm@linux-foundation.org,
	linux@roeck-us.net, nsekhar@ti.com, t-kristo@ti.com,
	j-keerthy@ti.com, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH V3 3/3] rtc: omap: Support regulator supply for RTC
Date: Fri, 24 Oct 2014 10:43:12 -0500	[thread overview]
Message-ID: <20141024154312.GL26941@saruman> (raw)
In-Reply-To: <544A5393.6090504@ti.com>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

On Fri, Oct 24, 2014 at 08:26:43AM -0500, Nishanth Menon wrote:
> On 10/23/2014 11:53 PM, Lokesh Vutla wrote:
> > On some Soc's RTC is powered by an external power regulator.
> SoC ? -> could you rephrase this to indicate "certain SoCs such as
> DRA7, RTC is an independent voltage domain of it's own and on
> platforms such as DRA7-evm, this may be supplied by individual
> regulator on it's own.
> 
> > e.g. RTC on DRA7 SoC. Make the OMAP RTC driver support a
> > power regulator.
> 
> Question ofcourse is what voltage would you like that regulator to be
> at? As you are aware, certain LDOs and SMPS can drive varying voltage
> and just enable/disable would do just the default voltage of the
> SMPS/LDO, right? OR am i missing something here?

just pass the correct voltage through DTS as we do for all other
regulators ? It's only tricky when we have a range of acceptable
voltages but for RTC, IIRC, it's always a set voltage (1.0V or 1.8V).

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 3/3] rtc: omap: Support regulator supply for RTC
Date: Fri, 24 Oct 2014 10:43:12 -0500	[thread overview]
Message-ID: <20141024154312.GL26941@saruman> (raw)
In-Reply-To: <544A5393.6090504@ti.com>

On Fri, Oct 24, 2014 at 08:26:43AM -0500, Nishanth Menon wrote:
> On 10/23/2014 11:53 PM, Lokesh Vutla wrote:
> > On some Soc's RTC is powered by an external power regulator.
> SoC ? -> could you rephrase this to indicate "certain SoCs such as
> DRA7, RTC is an independent voltage domain of it's own and on
> platforms such as DRA7-evm, this may be supplied by individual
> regulator on it's own.
> 
> > e.g. RTC on DRA7 SoC. Make the OMAP RTC driver support a
> > power regulator.
> 
> Question ofcourse is what voltage would you like that regulator to be
> at? As you are aware, certain LDOs and SMPS can drive varying voltage
> and just enable/disable would do just the default voltage of the
> SMPS/LDO, right? OR am i missing something here?

just pass the correct voltage through DTS as we do for all other
regulators ? It's only tricky when we have a range of acceptable
voltages but for RTC, IIRC, it's always a set voltage (1.0V or 1.8V).

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141024/9f6a78a9/attachment.sig>

  reply	other threads:[~2014-10-24 15:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  4:53 [PATCH V3 0/3] rtc: omap: Add support for regulator supply Lokesh Vutla
2014-10-24  4:53 ` Lokesh Vutla
2014-10-24  4:53 ` [PATCH V3 1/3] rtc: omap: use module_platform_driver Lokesh Vutla
2014-10-24  4:53   ` Lokesh Vutla
2014-10-24  7:33   ` Johan Hovold
2014-10-24  7:33     ` Johan Hovold
2014-10-24 15:38   ` Felipe Balbi
2014-10-24 15:38     ` Felipe Balbi
2014-10-24  4:53 ` [PATCH V3 2/3] rtc: omap: Update Kconfig for OMAP RTC Lokesh Vutla
2014-10-24  4:53   ` Lokesh Vutla
2014-10-24  4:53 ` [PATCH V3 3/3] rtc: omap: Support regulator supply for RTC Lokesh Vutla
2014-10-24  4:53   ` Lokesh Vutla
2014-10-24  7:53   ` Johan Hovold
2014-10-24  7:53     ` Johan Hovold
2014-10-24  7:57     ` Lokesh Vutla
2014-10-24  7:57       ` Lokesh Vutla
2014-10-24 15:40     ` Felipe Balbi
2014-10-24 15:40       ` Felipe Balbi
2014-10-24  8:07   ` [PATCH V4 " Lokesh Vutla
2014-10-24  8:07     ` Lokesh Vutla
2014-10-24 15:40     ` Felipe Balbi
2014-10-24 15:40       ` Felipe Balbi
2014-10-24 13:26   ` [PATCH V3 " Nishanth Menon
2014-10-24 13:26     ` Nishanth Menon
2014-10-24 15:43     ` Felipe Balbi [this message]
2014-10-24 15:43       ` Felipe Balbi
2014-10-24 15:47       ` Nishanth Menon
2014-10-24 15:47         ` Nishanth Menon
2014-10-28  9:49     ` Lokesh Vutla
2014-10-28  9:49       ` Lokesh Vutla

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=20141024154312.GL26941@saruman \
    --to=balbi@ti.com \
    --cc=a.zummo@towertech.it \
    --cc=akpm@linux-foundation.org \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=johan@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lokeshvutla@ti.com \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=rtc-linux@googlegroups.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.com \
    /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.