From: "Valentin Vidić" <vvidic@valentin-vidic.from.hr>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "Alexander Ivanov" <amivanov@fastmail.com>,
kernelnewbies@kernelnewbies.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bjørn Mork" <bjorn@mork.no>,
"Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
"Jean Delvare" <jdelvare@suse.de>
Subject: Re: GPIO Driver for Skylake-Y PCH
Date: Thu, 29 Aug 2019 13:49:55 +0200 [thread overview]
Message-ID: <20190829114955.GH32308@valentin-vidic.from.hr> (raw)
In-Reply-To: <20190829104931.GU2680@smile.fi.intel.com>
On Thu, Aug 29, 2019 at 01:49:31PM +0300, Andy Shevchenko wrote:
> This actually should be done other way around, i.e. enabling ACPI WDAT table
> will get you watchdog and this is *highly* recommended way.
If I understand correctly you are suggesting to try the wdat_wdt driver instead?
Discussion about iTCO_wdt problem with Intel NUC is here but no solution so far:
https://www.spinics.net/lists/linux-watchdog/msg16232.html
https://www.spinics.net/lists/linux-i2c/msg41504.html
# modprobe i2c_i801
[40450.070587] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[40450.070652] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[40450.072919] iTCO_vendor_support: vendor-support=0
[40450.073485] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[40450.073546] iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]
[40450.073578] iTCO_wdt: probe of iTCO_wdt failed with error -16
--
Valentin
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-09-02 1:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 17:58 GPIO Driver for Skylake-Y PCH Alexander Ivanov
2019-06-14 18:46 ` Valdis Klētnieks
2019-06-14 19:01 ` Alexander Ivanov
2019-06-14 19:09 ` Valdis Klētnieks
2019-06-14 20:25 ` Alexander Ivanov
2019-06-14 22:40 ` Alexander Ivanov
2019-06-15 8:53 ` Bjørn Mork
2019-06-15 19:30 ` Valdis Klētnieks
2019-06-15 19:38 ` Alexander Ivanov
2019-06-15 19:56 ` Greg KH
2019-06-16 1:50 ` Valdis Klētnieks
2019-06-16 2:45 ` Alexander Ivanov
2019-06-16 8:54 ` Bjørn Mork
2019-06-17 8:06 ` Andy Shevchenko
2019-06-18 0:00 ` Alexander Ivanov
2019-06-18 8:40 ` Andy Shevchenko
2019-06-18 14:48 ` Valdis Klētnieks
2019-06-18 15:57 ` Andy Shevchenko
2019-06-18 16:17 ` Alexander Ivanov
2019-06-20 21:02 ` Alexander Ivanov
2019-06-21 10:12 ` Andy Shevchenko
2019-06-21 17:39 ` Alexander Ivanov
2019-06-24 18:39 ` Alexander Ivanov
2019-06-25 11:08 ` Andy Shevchenko
2019-06-25 14:10 ` Linus Walleij
2019-07-10 16:04 ` Andy Shevchenko
2019-08-28 21:04 ` Alexander Ivanov
2019-08-29 7:47 ` Valentin Vidić
2019-08-29 10:49 ` Andy Shevchenko
2019-08-29 11:49 ` Valentin Vidić [this message]
2019-08-29 14:59 ` Andy Shevchenko
2019-08-29 17:17 ` Valentin Vidić
2019-08-29 15:59 ` Alexander Ivanov
2019-06-14 19:12 ` Bjørn Mork
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=20190829114955.GH32308@valentin-vidic.from.hr \
--to=vvidic@valentin-vidic.from.hr \
--cc=amivanov@fastmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bjorn@mork.no \
--cc=jdelvare@suse.de \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linus.walleij@linaro.org \
--cc=valdis.kletnieks@vt.edu \
/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).