Date: Mon, 7 Feb 2005 12:00:40 -0500 (EST)
From: linux-os <linux-os@analogic.com>
Reply-To: linux-os@analogic.com
To: "Randy.Dunlap" <rddunlap@osdl.org>
cc: Charles-Edouard Ruault <ce@idtect.com>,
       Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: IO port conflict between timer & watchdog on PCISA-C800EV board
 ?
In-Reply-To: <420797DE.6030904@osdl.org>
Message-ID: <Pine.LNX.4.61.0502071157520.22576@chaos.analogic.com>
References: <420734DC.4020900@idtect.com> <420797DE.6030904@osdl.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2347
Lines: 55

On Mon, 7 Feb 2005, Randy.Dunlap wrote:

> Charles-Edouard Ruault wrote:
>> Hi All,
>> 
>> i wrote a driver for the watchdog timer provided by a small form factor 
>> board from IEI ( the PCISA-C800EV : 
>> http://www.iei.com.tw/en/product_IPC.asp?model=PCISA-C800 ).
>> This board has a Via Apollo PLE133 ( VT8601A and VT82C686B ) chipset.
>> The watchdog uses two registers at addresses 0x43 and 0x443, therefore my 
>> driver tries to get bot addresses for its own use calling
>> request_region(0x43, 1, "watchdog" ) and request_region(0x443, 1, 
>> "watchdog").
>> The first call to request 0x43 fails because the address has already been 
>> allocated to the timer ( /proc/ioports shows 0040-005f : timer ).
>> 
>> So my questions are :
>> - Why is the generic timer using this address ? isn't it reserving a too 
>> wide portion of IO ports ? Should it be modified for this board ?
>> -  If there's a good reason for the timer to request this address, is 
>> there a clean way to share it with the timer ?
>
> Missing kernel version.... must be "not the current/latest",
> so early 2.6 or more likely 2.4 (just guessing)?
>
> /proc/ioports timer assignments have now been split up like this:
> 0040-0043 : timer0
> 0050-0053 : timer1
>
> However, port 0x43 is still assigned to timer0, so your request_region
> call will still fail.  What system board timer resource assignments
> should be used for that VIA chipset?  If the chipset timer only needs
> 0x40-0x42, e.g., leaving 0x43 available, then it would be possible
> to do some kind of workaround (maybe not real clean, but possible).
>
> -- 
> ~Randy

The driver can still R/W registers that it hasn't allocated.
There is no hardware trap preventing this. I suggest that,
as a temporary work-around, just don't allocate the low
port, but attempt to use it. I think the watchdog probably
just looks for read at that address.


Cheers,
Dick Johnson
Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
  Notice : All mail here is now cached for review by Dictator Bush.
                  98.36% of all statistics are fiction.
-
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/