[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a9adf20c-f730-a7e9-a826-59216c17f03d@roeck-us.net>
Date: Mon, 7 Oct 2019 05:36:38 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Eugen.Hristev@...rochip.com, linux-watchdog@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.or
Cc: wim@...ux-watchdog.org, robh+dt@...nel.org,
Nicolas.Ferre@...rochip.com, alexandre.belloni@...tlin.com
Subject: Re: [PATCH 2/3] watchdog: sam9x60_wdt: introduce sam9x60 watchdog
timer driver
On 10/7/19 12:58 AM, Eugen.Hristev@...rochip.com wrote:
[ ... ]
> Hello Guenter,
>
> Thank you for the feedback.
> After reviewing this, can you please guide me towards one of the
> possible two directions: merge this driver with sama5d4_wdt , and have a
> single driver with support for both hardware blocks; or, have this
> driver separately , as in this patch series?
>
I noticed the similarities. I don't know if it makes sense to reconcile
the two drivers; it seems to me the new chip uses the same basic core with
enhancements. In general, I prefer a single driver, but only if the result
doesn't end up being an if/else mess. Ultimately, it is really your call
to make.
Guenter
Powered by blists - more mailing lists