From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Fu Wei <fu.wei@linaro.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@iguana.be>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
linux-watchdog@vger.kernel.org
Subject: Re: Additional patches in my watchdog-next branch
Date: Wed, 30 Dec 2015 15:02:00 +0100 [thread overview]
Message-ID: <20151230150200.3d960807@free-electrons.com> (raw)
In-Reply-To: <CADyBb7tsyKgS4=r+KaAE22BgoRhhHJuMv_4R0TaSaLKd7wT34w@mail.gmail.com>
Hello,
On Wed, 30 Dec 2015 21:30:08 +0800, Fu Wei wrote:
> > Maybe we should enforce that all users of the driver use two Device
> > Tree compatible strings:
> >
> > compatible = "<vendor>,sbsa-gwdt", "arm,sbsa-gwdt";
> >
> > So that the SBSA watchdog driver can implement vendor specific quirks
> > if needed. Though it is true that the HW has some identification
> > registers that should allow to differentiate between the implementation.
>
> I think the implementation can be different, but all the SBSA watchdog
> should be able to use the same driver.
Yes, they *should*, but as Guenter said, since the specification is not
very clear, it is quite likely that some HW implementations will not
behave exactly like others, so the driver will likely need to have some
quirks to adapt to those subtle differences between implementations.
> > For now, I'm personally fine with a SBSA driver that does not support
> > the pretimeout. Is anyone working on submitting something like this ?
>
> I am working on a new non-pretimeout SBSA driver.
Ok, great. Can you Cc: me when you send this new version ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-30 14:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 15:23 Additional patches in my watchdog-next branch Guenter Roeck
2015-12-28 15:27 ` Wim Van Sebroeck
2015-12-28 21:57 ` Guenter Roeck
2015-12-28 22:54 ` Wim Van Sebroeck
2015-12-28 23:17 ` Vladimir Zapolskiy
2015-12-29 7:17 ` Wim Van Sebroeck
2015-12-29 16:04 ` Guenter Roeck
2015-12-29 16:37 ` Thomas Petazzoni
2015-12-29 17:28 ` Guenter Roeck
2015-12-30 9:44 ` Thomas Petazzoni
2015-12-30 13:30 ` Fu Wei
2015-12-30 14:02 ` Thomas Petazzoni [this message]
2015-12-30 15:01 ` Fu Wei
2015-12-30 15:03 ` Thomas Petazzoni
2015-12-30 15:06 ` Fu Wei
2015-12-30 11:44 ` Fu Wei
2015-12-30 11:30 ` Fu Wei
2016-01-03 22:49 ` Vladimir Zapolskiy
2015-12-29 0:08 ` Guenter Roeck
2015-12-29 7:21 ` Wim Van Sebroeck
2015-12-29 16:02 ` Guenter Roeck
2015-12-29 20:01 ` Wim Van Sebroeck
2015-12-29 21:20 ` Guenter Roeck
2015-12-30 10:06 ` Wim Van Sebroeck
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=20151230150200.3d960807@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=fu.wei@linaro.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=vladimir_zapolskiy@mentor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.