From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44764) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a19Ib-0006qz-Qj for qemu-devel@nongnu.org; Tue, 24 Nov 2015 03:50:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a19IY-0005so-Lu for qemu-devel@nongnu.org; Tue, 24 Nov 2015 03:50:05 -0500 Message-ID: <1448354993.4574.60.camel@kernel.crashing.org> From: Benjamin Herrenschmidt Date: Tue, 24 Nov 2015 19:49:53 +1100 In-Reply-To: <20151124032050.GG26118@voom.fritz.box> References: <1447201710-10229-1-git-send-email-benh@kernel.crashing.org> <1447201710-10229-28-git-send-email-benh@kernel.crashing.org> <20151124032050.GG26118@voom.fritz.box> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 27/77] ppc/pnv: Add XSCOM infrastructure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Gibson Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org On Tue, 2015-11-24 at 14:20 +1100, David Gibson wrote: > Hmm.. I'm thinking it probably makes sense to unify the representation > of "chip" and "xscom" since there's a 1:1 correspondance.=C2=A0 To be > QOMishly correct, I think the right way would be a SysBusDevice for > each chip, implementing the xscom MMIOs, then an array of link properti= es > under the Machine object to find the right scoms by chip id. But there is more than xscom's under each chip ... there's PHBs, LPC controllers (though those are currently under XSCOM) and possibly other completely unrelated things... To be honest I've never been a big fan of that whole QOM business and am a bit confused as to how that would all work together. Cheers, Ben.