From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [GIT PULL] omap changes for v2.6.39 merge window Date: Thu, 7 Apr 2011 03:44:44 +0200 Message-ID: <201104070344.44568.arnd@arndb.de> References: <1302079304.8718.7.camel@e102109-lin.cambridge.arm.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: Received: from moutng.kundenserver.de ([212.227.126.187]:62445 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754396Ab1DGBqC (ORCPT ); Wed, 6 Apr 2011 21:46:02 -0400 In-Reply-To: <1302079304.8718.7.camel@e102109-lin.cambridge.arm.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Catalin Marinas Cc: Linus Walleij , Linus Torvalds , Will Deacon , Ingo Molnar , david@lang.hm, Russell King - ARM Linux , Nicolas Pitre , Tony Lindgren , lkml , "H. Peter Anvin" , David Brown , linux-omap@vger.kernel.org, Thomas Gleixner , linux-arm-kernel@lists.infradead.org On Wednesday 06 April 2011, Catalin Marinas wrote: > On Wed, 2011-04-06 at 00:19 +0100, Linus Walleij wrote: > > 2011/4/1 Linus Torvalds : > > Basically it requires you to get the physical address and size of > > each peripheral, then at offset -0x10 from the end address (usually > > at even 4K pages), if you find the magic number 0xB105F00D > > (ARM has a sense of humour, obviously) you can find something > > alike the PCI IDs at offset -0x20, manufacturer ID, version number > > and revision of the hardware. > > I don't think this was ever part of the AMBA specification. It was just > some convention used within ARM for the PrimeCell peripherals. Other > AMBA licensees did something else so it's not a reliable mechanism (I > think ARM gave up on this as well in recent peripherals). Do you think there is a way to get ARM ltd to make a better effort at this with a future specification? I suppose it would be extremely helpful if there was a way to specify more of the required information, and to require everybody to fill in correct data, in the same way that architecture compliance gets enforced on the CPU core. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Thu, 7 Apr 2011 03:44:44 +0200 Subject: [GIT PULL] omap changes for v2.6.39 merge window In-Reply-To: <1302079304.8718.7.camel@e102109-lin.cambridge.arm.com> References: <1302079304.8718.7.camel@e102109-lin.cambridge.arm.com> Message-ID: <201104070344.44568.arnd@arndb.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wednesday 06 April 2011, Catalin Marinas wrote: > On Wed, 2011-04-06 at 00:19 +0100, Linus Walleij wrote: > > 2011/4/1 Linus Torvalds : > > Basically it requires you to get the physical address and size of > > each peripheral, then at offset -0x10 from the end address (usually > > at even 4K pages), if you find the magic number 0xB105F00D > > (ARM has a sense of humour, obviously) you can find something > > alike the PCI IDs at offset -0x20, manufacturer ID, version number > > and revision of the hardware. > > I don't think this was ever part of the AMBA specification. It was just > some convention used within ARM for the PrimeCell peripherals. Other > AMBA licensees did something else so it's not a reliable mechanism (I > think ARM gave up on this as well in recent peripherals). Do you think there is a way to get ARM ltd to make a better effort at this with a future specification? I suppose it would be extremely helpful if there was a way to specify more of the required information, and to require everybody to fill in correct data, in the same way that architecture compliance gets enforced on the CPU core. Arnd