From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from bh-25.webhostbox.net ([208.91.199.152]:34850 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754947AbcGHNXu (ORCPT ); Fri, 8 Jul 2016 09:23:50 -0400 Subject: Re: I/O address 0x0cd6 already in use To: ioanm@linux.com, linux-watchdog@vger.kernel.org References: <577E71D0.3030207@roeck-us.net> <20160707191600.GA9431@roeck-us.net> From: Guenter Roeck Message-ID: <577FA963.70408@roeck-us.net> Date: Fri, 8 Jul 2016 06:23:47 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-watchdog-owner@vger.kernel.org List-Id: linux-watchdog@vger.kernel.org On 07/07/2016 09:59 PM, Ioan Moldovan wrote: > Okay, but won't unloading i2c cause errors? Not loading the i2c controller would mean that you can not access any of the i2c devices connected to the i2c bus. > Or won't unloading watchdog and keeping just i2c also cause errors? Unloading (or, rather, not loading) the watchdog driver means that you won't be able to use the watchdog. Sure, both is undesirable, but unless we hear otherwise we have to assume that the change to the i2c driver was made on purpose, and there isn't really anything we can do about it. Guenter