From owner-freebsd-hackers@freebsd.org Wed Aug 24 07:58:31 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D45BBC223A for ; Wed, 24 Aug 2016 07:58:31 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from mr11p00im-asmtp004.me.com (mr11p00im-asmtp004.me.com [17.110.69.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 00CF61D4C for ; Wed, 24 Aug 2016 07:58:31 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from process-dkim-sign-daemon.mr11p00im-asmtp004.me.com by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OCE00O00LRDBS00@mr11p00im-asmtp004.me.com> for freebsd-hackers@freebsd.org; Wed, 24 Aug 2016 07:58:30 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=4d515a; t=1472025510; bh=ZFifROKAfgVTWMRss+9APQVuR9qfXhT71uVkPFPVwkc=; h=Date:Subject:From:To:Message-id:MIME-version:Content-type; b=XEl0sXwPxu2sf72SXyjNnjosCRxiGQ+IuOSzgVb5wVmn8UNf2wjtrV2tTLZCwPsDg f0EyqxVH8r/qXy+iNgyU3FIXubCGNToVwdT864mIyNESILKXhFny+GZN3+LoPfGyo5 dJaqvaIXmPHrYgodZCISl3k72WQuPS3KmXfrdUWGnSrJfLwGEYESDTMUnsEFnYi4Gg 0EoPKVnlqu9C6TzZ45T7YEZjHmoG1nnBYL8vL9bTKB4MeYso0urom/ywQEAd/MsxRB EjGAPuUR9hlneUo41L94wJQu6QrkiN2JGNTWy8ZesrwUyoB/XpO2l7E1Zss3MLxjTp 61JHbJgPUSLWw== Received: from [192.168.1.4] (c-67-188-225-23.hsd1.ca.comcast.net [67.188.225.23]) by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OCE0073MM5G9E10@mr11p00im-asmtp004.me.com>; Wed, 24 Aug 2016 07:58:30 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-08-24_04:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1608240072 User-Agent: Microsoft-MacOutlook/f.19.0.160817 Date: Wed, 24 Aug 2016 00:58:27 -0700 Subject: Re: problem attaching driver at LPC bus From: Ravi Pokala Sender: "Pokala, Ravi" To: "karu.pruun" Cc: Warner Losh , "freebsd-hackers@freebsd.org" Message-id: Thread-topic: problem attaching driver at LPC bus References: <20A27669-0B16-4199-853F-46D84E876AE9@panasas.com> <082EEC89-4BFF-48B9-84DA-C971D396A6CD@panasas.com> In-reply-to: MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Aug 2016 07:58:31 -0000 -----Original Message----- From: "karu.pruun" Date: 2016-08-24, Wednesday at 00:49 To: Ravi Pokala Cc: Warner Losh , "freebsd-hackers@freebsd.org" Subject: Re: problem attaching driver at LPC bus > Hi Ravi > > Thanks for these suggestions. I'll study the spec and try implement this. Question: the XXX_base in bus_set_resource --- did you find this address from the spec? I suppose in my case this is the one I see in the acpi tables, 0x0700. Yes, I got them from the specs. For the embedded controller, the chipset spec defined which registers in the bridge to look at, which held the LPC address of the embedded GPIO controller. For the discrete controller, the controller spec documented a default and an alternate LPC address, and the BIOS developers told us which one they used. > Another question: on my naive thinking, the acpi subsystem scans the acpi tables and populates the entries in the device tree, setting aside the address ranges (IO and mem) for which there is no driver. The handle items in the tree (e.g. \_SB_.PCI0.LPCB.GMUX) look very similar to the ones in the acpi tables. So I thought the driver then later claims these resource using the bus_alloc_resource(). Does this sound like anything that is actually happening? I know almost nothing about ACPI, so I'll leave that someone who knows more about it than I do. :-) > > Thanks again > > Peeter Glad to help. -Ravi (rpokala@)