From owner-freebsd-current  Wed Jun 26 20:29:23 2002
Delivered-To: freebsd-current@freebsd.org
Received: from axe-inc.co.jp (axegw.axe-inc.co.jp [61.199.217.66])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1895B37B407; Wed, 26 Jun 2002 20:21:14 -0700 (PDT)
Received: from axe-inc.co.jp (takawata@[192.47.224.47])
	by axe-inc.co.jp (8.9.3+3.2W/3.7W) with ESMTP id MAA26662;
	Thu, 27 Jun 2002 12:20:56 +0900 (JST)
Message-Id: <200206270320.MAA26662@axe-inc.co.jp>
To: Willem van Engen <wvengen@stack.nl>
Cc: current@freebsd.org, nsouch@freebsd.org
Subject: Re: smbalert# hook for smbus childs
In-reply-to: Your message of "Mon, 24 Jun 2002 14:59:21 +0200."
             <20020624145921.463108fc.wvengen@stack.nl>
Date: Thu, 27 Jun 2002 12:21:19 +0900
From: Takanori Watanabe <takawata@axe-inc.co.jp>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

In message <20020624145921.463108fc.wvengen@stack.nl>, Willem van Engen wrote:

>Hello,
>
>there already is some code for smbalert# handling on intpm
>(ENABLE_ALART), but there is no support for handling it in a driver. O2
>AudioDJ (OZ162) chips use this signal to indicate that a button was
>pressed. So I need a way for a driver to be notified when smbalert#
>occurs.

I have never tested the code, though. 

>Of course I thought immediately about bus_(setup|teardown)_intr. I wrote
>something like that for smbus: bus_(setup|teardown)_alart (see patch),
>that works now. But is this The Right Way to do it? I do have some
>thoughts on it, but maybe someone more knowledgeable than me could comment
>on it.

I thought about ACPI embedded controller SMBus device driver and 
this mechanism will be needed for implement event notification mechanism. 

>It might be better to use bus_*_intr instead of bus_*_alart, but one
>would need to bus_alloc_resource a slave address and pass that to
>bus_setup_intr. But then it makes sense to use those slave address
>resources to send smbus commands, right? But how would that fit into the
>bus_space_* functions?

*I* think it is fit to smbus specific function.

>p.s. I hope I'm clear, english isn't my native language.
So am I (T_T).


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message