From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
LINUXKERNEL <linux-kernel@vger.kernel.org>,
LINUXWATCHDOG <linux-watchdog@vger.kernel.org>,
Wim Van Sebroeck <wim@iguana.be>,
Alessandro Zummo <a.zummo@towertech.it>,
DEVICETREE <devicetree@vger.kernel.org>,
David Dajun Chen <david.chen@diasemi.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
LINUXINPUT <linux-input@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
RTCLINUX <rtc-linux@googlegroups.com>,
Rob Herring <robh+dt@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Support Opensource <Support.Opensource@diasemi.com>
Subject: Re: [rtc-linux] RE: [PATCH V2 3/4] watchdog: da9062: DA9062 watchdog driver
Date: Mon, 18 May 2015 19:39:27 +0200 [thread overview]
Message-ID: <20150518173927.GV3338@piout.net> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB7014B22B8FE@SW-EX-MBX02.diasemi.com>
On 18/05/2015 at 16:03:06 +0000, Opensource [Steve Twiss] wrote :
> > Since the interrupt is optional, the driver should also not fail to load
> > if no interrupt is assigned to it in the first place.
>
> Yeah. I've been thinking about it and I agree now. I'll erase the handler.
>
> > On a separate note, there was a comment stating that the da9062 watchdog
> > is identical to the da9063 watchdog. If so, why can't you just use the da9063
> > watchdog driver ?
>
> Well, the short answer to this is, it's not the same. I was just in the process of
> replying to that other thread. The OnKey and RTC are functionally similar, so I
> am going to look at integrating the two drivers in some future patch sets, but
> the watchdog is definitely not based upon DA9063.
>
> I did mention this in a previous thread:
> https://lkml.org/lkml/2015/5/6/505
>
Sure, what I understand is that the base functionality is the same and
even the registers are compatible. Are you sure the new features can't
be added to the da9063 and called conditionally? Plenty of drivers are
doing that.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-18 17:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 16:43 [PATCH V2 0/4] da9062: DA9062 driver submission S Twiss
2015-05-14 16:43 ` [PATCH V2 1/4] mfd: da9062: DA9062 MFD core driver S Twiss
2015-05-16 8:53 ` [rtc-linux] " Alexandre Belloni
2015-05-19 8:34 ` Opensource [Steve Twiss]
2015-05-14 16:43 ` [PATCH V2 3/4] watchdog: da9062: DA9062 watchdog driver S Twiss
2015-05-15 2:13 ` Guenter Roeck
2015-05-15 8:13 ` Opensource [Steve Twiss]
2015-05-15 12:57 ` Guenter Roeck
2015-05-15 15:35 ` Opensource [Steve Twiss]
2015-05-15 20:20 ` Guenter Roeck
2015-05-18 14:15 ` Opensource [Steve Twiss]
2015-05-18 15:27 ` Guenter Roeck
2015-05-18 16:03 ` Opensource [Steve Twiss]
2015-05-18 17:39 ` Alexandre Belloni [this message]
2015-05-19 10:16 ` [rtc-linux] " Opensource [Steve Twiss]
2015-05-14 16:43 ` [PATCH V2 4/4] devicetree: da9062: Add bindings for DA9062 driver S Twiss
2015-05-14 16:43 ` [PATCH V2 2/4] regulator: da9062: DA9062 regulator driver S Twiss
2015-05-16 0:46 ` [rtc-linux] [PATCH V2 0/4] da9062: DA9062 driver submission Alexandre Belloni
2015-05-18 14:23 ` Opensource [Steve Twiss]
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=20150518173927.GV3338@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=Support.Opensource@diasemi.com \
--cc=a.zummo@towertech.it \
--cc=broonie@kernel.org \
--cc=david.chen@diasemi.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=stwiss.opensource@diasemi.com \
--cc=wim@iguana.be \
/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;
as well as URLs for NNTP newsgroup(s).