From: <harald@ccbib.org>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: <rtc-linux@googlegroups.com>, Wolfram Sang <wsa@the-dreams.de>,
Wim Van Sebroeck <wim@iguana.be>,
<linux-watchdog@vger.kernel.org>
Subject: Re: [rtc-linux] [PATCH] watchdog: stmp3xxx: Implement GETBOOTSTATUS
Date: Mon, 20 Apr 2015 09:11:02 +0200 [thread overview]
Message-ID: <480bd3b38b87b44913868cbd2f3e24c6@imap.cosmopool.net> (raw)
In-Reply-To: <20150419153743.GA4353@piout.net>
Hi Alexandre,
On Sun, 19 Apr 2015 17:37:43 +0200, Alexandre Belloni
<alexandre.belloni@free-electrons.com> wrote:
> On 19/04/2015 at 15:41:42 +0200, harald@ccbib.org wrote :
>> > - use syscon instead of passing callbacks to the watchdog driver
>>
>> I will put looking into this onto my todo list, but I'm not familiar
>> with syscon yet and it is not obvious to me how to port the rtc driver
>> to syscon without breaking devicetree backwards compatibility. So I'd
>> like to defer this for later unless somebody gives me some guidance.
>>
>
> As the rtc driver is the one instantiating the watchdog driver, there is
> no reason why the DT ABI would be broken. You simply have to create
> the syscon in the RTC driver and then pass it to the watchdog driver,
> the same way it is done with the callbacks.
Ok, this is less invasive than what I have been thinking. This makes
sense.
> I can have a look at doing it as I have some i.mx28 platforms.
If you can point me to a driver that is a good reference for your model,
then I can do this myself. Otherwise I'd prefer if you wrote the code.
I can do the testing though, if this helps.
Thanks,
Harald
next prev parent reply other threads:[~2015-04-20 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 19:45 [PATCH] watchdog: stmp3xxx: Implement GETBOOTSTATUS Harald Geyer
2015-04-17 9:30 ` [rtc-linux] " Alexandre Belloni
2015-04-19 13:41 ` harald
2015-04-19 15:37 ` Alexandre Belloni
2015-04-20 7:11 ` harald [this message]
2015-05-05 9:40 ` Alexandre Belloni
2015-10-01 17:20 ` harald
2015-10-01 18:31 ` Alexandre Belloni
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=480bd3b38b87b44913868cbd2f3e24c6@imap.cosmopool.net \
--to=harald@ccbib.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=wim@iguana.be \
--cc=wsa@the-dreams.de \
/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