From: a0393675@ti•com (Keerthy)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH V2 2/2] ARM: dts: DRA7: Add node for RTC
Date: Tue, 15 Jul 2014 09:21:38 +0530 [thread overview]
Message-ID: <53C4A54A.1070500@ti.com> (raw)
In-Reply-To: <53C3ED02.7020206@ti.com>
On Monday 14 July 2014 08:15 PM, Lokesh Vutla wrote:
> Hi Tony,
> On Wednesday 09 July 2014 04:36 PM, Keerthy wrote:
>> On Wednesday 09 July 2014 04:30 PM, Tony Lindgren wrote:
>>> * Keerthy <a0393675@ti•com> [140709 03:59]:
>>>> On Wednesday 09 July 2014 04:20 PM, Tony Lindgren wrote:
>>>>> * Keerthy <a0393675@ti•com> [140709 03:39]:
>>>>>> On Wednesday 09 July 2014 03:39 PM, Tony Lindgren wrote:
>>>>>>> * Keerthy <a0393675@ti•com> [140709 02:36]:
>>>>>>>> On Wednesday 09 July 2014 02:42 PM, Tony Lindgren wrote:
>>>>>>>>> * Lokesh Vutla <lokeshvutla@ti•com> [140709 01:37]:
>>>>>>>>>> --- a/arch/arm/boot/dts/dra7-evm.dts
>>>>>>>>>> +++ b/arch/arm/boot/dts/dra7-evm.dts
>>>>>>>>>> @@ -249,6 +249,7 @@
>>>>>>>>>> regulator-min-microvolt = <1050000>;
>>>>>>>>>> regulator-max-microvolt = <1050000>;
>>>>>>>>>> regulator-boot-on;
>>>>>>>>>> + regulator-always-on;
>>>>>>>>>> };
>>>>>>>>> Is this regulator really always on?
>>>>>>>> This feeds on to RTC which is a free running clock. So i guess always on is
>>>>>>>> justified no?
>>>>>>> Well the dts entries should describe the hardware. If the
>>>>>>> regulator can be enabled and disabled, we should not claim it's
>>>>>>> always on.
>>>>>> From the PMIC perspective every regulator can be enabled and
>>>>>> disabled. From a Board perspective there are some which need
>>>>>> to be always on. For Ex: SMPS123 which feeds on to the MPU.
>>>>> Right, and we already have regulator-boot-on for those. Or are
>>>>> you seeing some issue with that?
>>>> regulator-boot-on describes that at boot a particular regulator is on.
>>>> It does not guarantee that it will be on for the rest of the time. The
>>>> regulator framework can go ahead and disable it if no one has requested
>>>> for it. In case of RTC we do not want that to happen.
>>> That's a bug in the RTC driver then. The driver should request a
>>> regulator if it's specified.
> In my experiments I observed that when RTC regulator is switched off and switched on, there is an abort while
> accessing RTC registers.
> After discussing with hardware team, it is confirmed that this LDO9 regulator powering RTC cannot be turned off when
> SoC is active and expected to be always on.
As confirmed by the PMIC hardware team this regulator should be an always-on
regulator.
Acked-by: Keerthy <j-keerthy@ti•com>
>
> Thanks and regards,
> Lokesh
>
>> Okay.
>>
>>> Regards,
>>>
>>> Tony
prev parent reply other threads:[~2014-07-15 3:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 12:37 [PATCH] ARM: DRA7: hwmod: add entry for RTCSS Sekhar Nori
2014-06-13 19:09 ` Paul Walmsley
2014-06-15 3:47 ` Paul Walmsley
2014-07-03 10:22 ` Rajendra Nayak
2014-07-06 0:32 ` Paul Walmsley
2014-07-09 8:35 ` [PATCH V2 0/2] ARM: DRA7: Add RTC hwmod and dt entries Lokesh Vutla
2014-07-09 8:35 ` [PATCH V2 1/2] ARM: DRA7: hwmod: Add data for RTC Lokesh Vutla
2014-07-22 10:19 ` Lokesh Vutla
2014-07-22 19:19 ` Paul Walmsley
2014-07-09 8:35 ` [PATCH V2 2/2] ARM: dts: DRA7: Add node " Lokesh Vutla
2014-07-09 9:12 ` Tony Lindgren
2014-07-09 9:32 ` Keerthy
2014-07-09 10:09 ` Tony Lindgren
2014-07-09 10:35 ` Keerthy
2014-07-09 10:50 ` Tony Lindgren
2014-07-09 10:56 ` Keerthy
2014-07-09 11:00 ` Tony Lindgren
2014-07-09 11:06 ` Keerthy
2014-07-14 14:45 ` Lokesh Vutla
2014-07-14 16:23 ` Tony Lindgren
2014-07-15 3:57 ` Keerthy
2014-07-15 4:07 ` Lokesh Vutla
2014-07-15 6:59 ` Tony Lindgren
2014-07-15 3:51 ` Keerthy [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=53C4A54A.1070500@ti.com \
--to=a0393675@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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