public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Kashperko <george@znau.edu.ua>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	"Michael Büsch" <mb@bu3sch.de>,
	"Larry Finger" <Larry.Finger@lwfinger.net>,
	"George Kashperko" <george@znau.edu.ua>,
	"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Russell King" <rmk@arm.linux.org.uk>,
	"Arnd Bergmann" <arnd@arndb.de>,
	linuxdriverproject <devel@linuxdriverproject.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] bcmai: introduce AI driver
Date: Sat, 09 Apr 2011 10:10:26 +0300	[thread overview]
Message-ID: <1302333026.18361.8.camel@dev.znau.edu.ua> (raw)
In-Reply-To: <op.vtmqm7fw3ri7v4@arend-laptop>


> On Fri, 08 Apr 2011 18:56:13 +0200, Rafał Miłecki <zajec5@gmail.com> wrote:
> 
> > 2011/4/6 Arend van Spriel <arend@broadcom.com>:
> >> 3. Device identification
> >>
> >> The cores are identified by manufacturer, core id and revision in your
> >> patch. I would not use the revision because 4 out of 5 times a revision
> >> change does indicate a hardware change but no change in programming
> >> interface. The enumeration data does contain a more selective field
> >> indicating the core class (4 bits following the core identifier). I  
> >> suggest
> >> to replace the revision field by this class field.
> >
> > Could you say something more about *class*, please? For my BCM43224 it
> > seems to be 0x0. WIll check BCM4313 in a moment.
> >
> 
> In principal the manufacturer id is unique (defined/assigned by JEDEC  
> www.jedec.org) and the chip id and chip class are defined by the  
> manufacturer. So I can only indicate what classes Broadcom uses in  
> combination with the manufacturer id BRCM, ARM and MIPS.
> 
> /* Component Classes */
> #define	CC_SIM			0
> #define	CC_EROM			1
> #define	CC_CORESIGHT		9
> #define	CC_VERIF		0xb
> #define	CC_OPTIMO		0xd
> #define	CC_GEN			0xe
> #define	CC_PRIMECELL		0xf
> 
> Looking at this it seems strange that you see a class value of 0x0. It may  
> be rarely used or for non-production chips only (for simulation, chip  
> bringup) which may require additional (debug) functions. So question is  
> whether you will need it, but it is specified by ARM and it is up to  
> manufacturers to use it. So I it is better to be safe than sorry and have  
> this in the device id.
> 
> Gr. AvS
When parsing bcm4716 EROM I have
cia & CIA_CCL_MASK equal to 0 for all 9 cores

You mentioned ARM DMP (Device Management Plugin) several times in
earlier messages some time ago but I can't find anything relevant about
that at ARM infocenter. Any chance you can point more precise location
for any DMP reference?

Have nice day,
George




  parent reply	other threads:[~2011-04-09  7:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1302033463-1846-1-git-send-email-zajec5@gmail.com>
     [not found] ` <1302032137.3969.10.camel@Joe-Laptop>
     [not found]   ` <BANLkTimTmqop-xzFsWr1=2RXv5z6iTre4Q@mail.gmail.com>
     [not found]     ` <1302035106.1923.7.camel@maggie>
2011-04-05 22:30       ` [PATCH] ssb: Use pr_fmt and pr_<level>, remove CONFIG_SSB_SILENT Joe Perches
2011-04-06 14:18 ` [RFC][PATCH] bcmai: introduce AI driver Arend van Spriel
2011-04-06 18:02   ` Rafał Miłecki
2011-04-06 20:25     ` Arend van Spriel
2011-04-06 20:40       ` Rafał Miłecki
2011-04-06 20:42         ` Rafał Miłecki
2011-04-06 20:57           ` Michael Büsch
2011-04-06 21:01             ` Rafał Miłecki
2011-04-06 21:08               ` Michael Büsch
2011-04-06 21:12                 ` Rafał Miłecki
2011-04-06 21:18                   ` George Kashperko
2011-04-06 23:20                     ` Rafał Miłecki
2011-04-07  0:00                       ` George Kashperko
2011-04-07  0:54                         ` Rafał Miłecki
2011-04-07  1:02                           ` George Kashperko
2011-04-07  7:54                           ` Michael Büsch
2011-04-07  8:58                             ` Arend van Spriel
2011-04-07 18:50                               ` George Kashperko
2011-04-07  9:55                             ` Rafał Miłecki
2011-04-07 18:36                               ` George Kashperko
2011-04-06 21:20                   ` Michael Büsch
2011-04-08 16:56   ` Rafał Miłecki
2011-04-08 17:09     ` Rafał Miłecki
2011-04-08 17:14       ` Rafał Miłecki
2011-04-08 17:24     ` Arend van Spriel
2011-04-08 17:27       ` Rafał Miłecki
2011-04-08 17:28         ` Arend van Spriel
2011-04-08 17:31           ` Rafał Miłecki
2011-04-09  7:10       ` George Kashperko [this message]
2011-04-09 11:01         ` Arend van Spriel
2011-04-10  8:01   ` Pavel Machek
2011-04-10  8:05     ` Rafał Miłecki
2011-04-10  8:24       ` Pavel Machek
2011-04-10  8:30         ` Rafał Miłecki
2011-04-10  9:33           ` Arend van Spriel
2011-04-10 11:32             ` Rafał Miłecki
2011-04-10 14:36               ` Arend van Spriel
2011-04-10 16:11             ` George Kashperko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1302333026.18361.8.camel@dev.znau.edu.ua \
    --to=george@znau.edu.ua \
    --cc=Larry.Finger@lwfinger.net \
    --cc=arend@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=b43-dev@lists.infradead.org \
    --cc=devel@linuxdriverproject.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=rmk@arm.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox