From owner-freebsd-arch@FreeBSD.ORG  Mon Jun 23 15:52:13 2014
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B991499D
 for <freebsd-arch@freebsd.org>; Mon, 23 Jun 2014 15:52:13 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9188C263E
 for <freebsd-arch@freebsd.org>; Mon, 23 Jun 2014 15:52:13 +0000 (UTC)
Received: from jhbbsd.localnet (unknown [209.249.190.124])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7F715B98E;
 Mon, 23 Jun 2014 11:52:12 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-arch@freebsd.org
Subject: Re: How to properly handle several fonctions provided by the Winbond
 SuperIO chip?
Date: Mon, 23 Jun 2014 09:56:48 -0400
User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; )
References: <1118241087.138096.1403180509132.JavaMail.zimbra@arkoon-netasq.com>
 <201406190919.04443.jhb@freebsd.org>
 <750618593.166408.1403191319583.JavaMail.zimbra@arkoon-netasq.com>
In-Reply-To: <750618593.166408.1403191319583.JavaMail.zimbra@arkoon-netasq.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <201406230956.48220.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Mon, 23 Jun 2014 11:52:12 -0400 (EDT)
Cc: Emeric POUPON <emeric.poupon@arkoon-netasq.com>
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Mon, 23 Jun 2014 15:52:13 -0000

On Thursday, June 19, 2014 11:21:59 am Emeric POUPON wrote:
> Thanks for your answer!
> 
> I was thinking about calling some parent device functions from the children 
devices in order to perform IO accesses.
> But I imagine it would be "better" to expose a kind of bus interface from 
the main driver?
> However, I'm not sure the extra work induced is worth it. What do you think?

I think it's fine to have them call each other directly if they are going to 
all live in the same module.

-- 
John Baldwin