From owner-freebsd-arch@FreeBSD.ORG  Mon Jan 26 17:06:33 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3D2F416A4CE
	for <arch@freebsd.org>; Mon, 26 Jan 2004 17:06:33 -0800 (PST)
Received: from root.org (root.org [67.118.192.226])
	by mx1.FreeBSD.org (Postfix) with SMTP id AC35243D8D
	for <arch@freebsd.org>; Mon, 26 Jan 2004 17:05:18 -0800 (PST)
	(envelope-from nate@root.org)
Received: (qmail 30513 invoked by uid 1000); 27 Jan 2004 01:03:58 -0000
Date: Mon, 26 Jan 2004 17:03:58 -0800 (PST)
From: Nate Lawson <nate@root.org>
To: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20040126.151728.133912536.imp@bsdimp.com>
Message-ID: <20040126165523.W30461@root.org>
References: <20040126140100.T29680@root.org>
	<20040126.151728.133912536.imp@bsdimp.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: arch@freebsd.org
Subject: Re: newbus ioport usage
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2004 01:06:33 -0000

On Mon, 26 Jan 2004, M. Warner Losh wrote:
> In message: <20040126140100.T29680@root.org>
>             Nate Lawson <nate@root.org> writes:
> : I have a driver that knows the IO port it wants.  It's not set up by a
> : parent bus, so I can't use bus_set_resource().  This call returns NULL.
> : Any idea how to debug why newbus is rejecting this request?  The io port
> : is not in use and the rid is unique.
> :
> :   bus_alloc_resource(dev, SYS_RES_IOPORT, rid, 0x101c, 0x101c, 1,
> :     RF_ACTIVE);
>
> Ummm, you can use bus_set_resource() in the driver to do this (I've
> done it before).  bus_set_resource() should return 0 to indicate
> success.  bus_alloc_resource should then succeed.  There may be one
> other step to do as well to make this work, but I'm not sure if it is
> an internal convention or actually required.  The pci bus code does a
> resource_list_add for each of the resources the child uses, but I
> think that's an internal thing to the pci bus (that other busses do
> also).

Ok, I'm doing the set/alloc and it works.  However, one weird thing.  If I
allocate all ports at boot time, it succeeds.  My driver goes through
multiple release/allocate cycles and it all works as expected.  However if
I boot and attach to only one of the registers, subsequent attempts to
attach the second one fail.  The resources are 2 IO ports, 0x101c and
0x101d.  Both are 1 byte.

-Nate