Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933260Ab1CWQLR (ORCPT ); Wed, 23 Mar 2011 12:11:17 -0400 Received: from cantor.suse.de ([195.135.220.2]:40922 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933123Ab1CWQLP (ORCPT ); Wed, 23 Mar 2011 12:11:15 -0400 Date: Wed, 23 Mar 2011 09:06:24 -0700 From: Greg KH To: "Weil, Oren jer" Cc: Arnd Bergmann , "linux-kernel@vger.kernel.org" , "alan@linux.intel.com" , "david@woodhou.se" Subject: Re: [PATCH 0/7] char/mei: Intel MEI Driver Message-ID: <20110323160624.GA8972@suse.de> References: <1300791092-14319-1-git-send-email-oren.jer.weil@intel.com> <201103221750.52118.arnd@arndb.de> <20110323135126.GB16769@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1101 Lines: 27 On Wed, Mar 23, 2011 at 05:55:47PM +0200, Weil, Oren jer wrote: > >> >I suppose one of the important things to do here is integrate the > >> >watchdog part into the common watchdog infrastructure in > >> >drivers/watchdog. Maybe this driver can export a simple interface to > >> >another module that implements the watchdog device? > >> > >> Yes, this is one the ideas the Alan suggested, we are thinking about > >> this direction in the future. > > > >What's keeping you from doing this now? > > We need to change the driver to expose functions to communicate with the FW > Client (feature) > From other kernel models, the design for now is only from user space. So you need to add support to the watchdog infrastructure for this? For some reason I thought you could kick the watchdog from within kernel code, did I get this wrong? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/