From: "Jean-François Dagenais" <jeff.dagenais@gmail.com>
To: sameo@linux.intel.com
Cc: alexander.stein@systec-electronic.com, denis@compulab.co.il,
linux-kernel@vger.kernel.org,
"Jean-François Dagenais" <jeff.dagenais@gmail.com>
Subject: [PATCH] mfd: lpc_sch - tolerate f/w disabled WDT
Date: Fri, 11 May 2012 15:15:22 -0400 [thread overview]
Message-ID: <1336763722-11535-1-git-send-email-jeff.dagenais@gmail.com> (raw)
(Observed while running on Kontron nano-TT module.)
Certain BIOS/boot firmware may disable the tunnelcreek watchdog. Perhaps
because the mainboard or module provides it's own watchdog mechanism. In these
cases, lpc_sch should just go on and still provide the rest of the cells
it declares (GPIO and SMBus). The same logic could be applied to the other
resources, but I'll leave it to others to decide that.
This change makes the probe function tolerate the I/O range being disabled,
but not if the base address inside the register is not configured.
Cc: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Denis Turischev <denis@compulab.co.il>
Signed-off-by: Jean-François Dagenais <jeff.dagenais@gmail.com>
---
drivers/mfd/lpc_sch.c | 39 ++++++++++++++++++++-------------------
1 files changed, 20 insertions(+), 19 deletions(-)
diff --git a/drivers/mfd/lpc_sch.c b/drivers/mfd/lpc_sch.c
index ea1169b..6621cd3 100644
--- a/drivers/mfd/lpc_sch.c
+++ b/drivers/mfd/lpc_sch.c
@@ -127,26 +127,27 @@ static int __devinit lpc_sch_probe(struct pci_dev *dev,
if (id->device == PCI_DEVICE_ID_INTEL_ITC_LPC) {
pci_read_config_dword(dev, WDTBASE, &base_addr_cfg);
- if (!(base_addr_cfg & (1 << 31))) {
- dev_err(&dev->dev, "Decode of the WDT I/O range disabled\n");
- ret = -ENODEV;
- goto out_dev;
+ if (base_addr_cfg & (1 << 31)) {
+ base_addr = (unsigned short)base_addr_cfg;
+ if (base_addr == 0) {
+ dev_err(&dev->dev,
+ "I/O space for WDT uninitialized\n");
+ ret = -ENODEV;
+ goto out_dev;
+ }
+
+ wdt_sch_resource.start = base_addr;
+ wdt_sch_resource.end = base_addr + WDT_IO_SIZE - 1;
+
+ for (i = 0; i < ARRAY_SIZE(tunnelcreek_cells); i++)
+ tunnelcreek_cells[i].id = id->device;
+
+ ret = mfd_add_devices(&dev->dev, 0, tunnelcreek_cells,
+ ARRAY_SIZE(tunnelcreek_cells), NULL, 0);
+ } else {
+ dev_warn(&dev->dev, "Decode of the WDT I/O range disabled, tunnelcreek watchdog timer maybe disabled by firmware or BIOS");
+ return 0;
}
- base_addr = (unsigned short)base_addr_cfg;
- if (base_addr == 0) {
- dev_err(&dev->dev, "I/O space for WDT uninitialized\n");
- ret = -ENODEV;
- goto out_dev;
- }
-
- wdt_sch_resource.start = base_addr;
- wdt_sch_resource.end = base_addr + WDT_IO_SIZE - 1;
-
- for (i = 0; i < ARRAY_SIZE(tunnelcreek_cells); i++)
- tunnelcreek_cells[i].id = id->device;
-
- ret = mfd_add_devices(&dev->dev, 0, tunnelcreek_cells,
- ARRAY_SIZE(tunnelcreek_cells), NULL, 0);
}
return ret;
--
1.7.9
next reply other threads:[~2012-05-11 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 19:15 Jean-François Dagenais [this message]
2012-05-14 6:37 ` Alexander Stein
2012-05-14 12:17 ` Jean-Francois Dagenais
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=1336763722-11535-1-git-send-email-jeff.dagenais@gmail.com \
--to=jeff.dagenais@gmail.com \
--cc=alexander.stein@systec-electronic.com \
--cc=denis@compulab.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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
all inboxes | Powered by JetHome®