From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752746Ab0CXPti (ORCPT ); Wed, 24 Mar 2010 11:49:38 -0400 Received: from earthlight.etchedpixels.co.uk ([81.2.110.250]:43954 "EHLO www.etchedpixels.co.uk" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751747Ab0CXPth (ORCPT ); Wed, 24 Mar 2010 11:49:37 -0400 Date: Wed, 24 Mar 2010 15:51:51 +0000 From: Alan Cox To: Giel van Schijndel Cc: Hans de Goede , Jean Delvare , Jonathan Cameron , Laurens Leemans , lm-sensors@lm-sensors.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 4/4] [RFC] hwmon: f71882fg: Add watchdog API for F71808E and F71889 Message-ID: <20100324155151.2482952f@lxorguk.ukuu.org.uk> In-Reply-To: <20100324153550.GK6368@salidar.me.mortis.eu> References: <20100323141718.GA23172@salidar.me.mortis.eu> <1269385936-3440-1-git-send-email-me@mortis.eu> <1269385936-3440-2-git-send-email-me@mortis.eu> <1269385936-3440-3-git-send-email-me@mortis.eu> <1269385936-3440-4-git-send-email-me@mortis.eu> <4BA9CF57.4030504@redhat.com> <20100324093651.GG6368@salidar.me.mortis.eu> <4BA9EA5C.9060506@redhat.com> <20100324153550.GK6368@salidar.me.mortis.eu> X-Mailer: Claws Mail 3.7.4 (GTK+ 2.18.6; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > hold on the SIO port range. This would thus interfere with the operation > of the f71882fg driver. I.e. it would prevent the device probing stage > from working, thus preventing it from loading *after* my in-development > watchdog driver. There are two ways to deal with that really 1. Add a multi-function driver - it finds the chip and claims the port regions and then provides methods for locked access to them as well as creating other device instances that the drivers map to (probably platform devices ?) which in turn trigger the loading/binding of the relevant low level devices. 2. Fix the kernel request_resource stuff to support a sleeping non exclusive resource so request/free of regions can be used as a resource semaphore by co-operative devices. #2 is actually not hard but when I did the patch originally it then wasn't needed by the driver I had in mind for other reasons. See http://groups.google.com/group/linux.kernel/msg/1425fc2aad32e6ea Maybe its worth resurrecting ? Alan