From: Keerthy <j-keerthy@ti.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: <linux-rtc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, Russ Dill <Russ.Dill@ti.com>
Subject: Re: [rtc-linux] Re: [PATCH] RTC: Add functionality to read/write rtc scratch registers
Date: Sun, 16 Jul 2017 19:19:26 +0530 [thread overview]
Message-ID: <10b05dc7-74fd-8fbf-6b57-5443cf9f520b@ti.com> (raw)
In-Reply-To: <20170713204355.sbtjip5skms6zwdq@piout.net>
On Friday 14 July 2017 02:13 AM, Alexandre Belloni wrote:
> Hi,
>
> On 05/05/2017 at 00:38:27 +0200, Alexandre Belloni wrote:
>> Hi,
>>
>> On 03/05/2017 at 11:39:34 +0530, Keerthy wrote:
>>> On Tuesday 18 April 2017 10:50 AM, Keerthy wrote:
>>>> From: Russ Dill <Russ.Dill@ti.com>
>>>>
>>>> Many RTCs provide scratch registers that are maintained so long as the RTC
>>>> has power. Provide a generic method to access these registers.
>>>>
>>>
>>> A gentle ping on this
>>>
>>
>> Yeah, I apologize for the delay (I know you already sent this 6-8 months
>> ago).
>> I'm not satisfied with the interface (and its name). I gave a lot of
>> thought into it and I'm currently reworking part of the subsystem to
>> create a similar feature. I'm planning to have it in 4.13.
>>
>
> So, the nvmem stuff is now in 4.13. If you can still wait a bit, I'll
> implement it myself and test on am335x.
Sure.
>
>
prev parent reply other threads:[~2017-07-16 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 5:20 [rtc-linux] [PATCH] RTC: Add functionality to read/write rtc scratch registers Keerthy
2017-05-03 6:09 ` [rtc-linux] " Keerthy
2017-05-04 22:38 ` Alexandre Belloni
2017-05-05 3:31 ` Keerthy
2017-07-13 20:43 ` Alexandre Belloni
2017-07-16 13:49 ` 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=10b05dc7-74fd-8fbf-6b57-5443cf9f520b@ti.com \
--to=j-keerthy@ti.com \
--cc=Russ.Dill@ti.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rtc@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