Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: arend@broadcom.com (Arend van Spriel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] new module for amba axi on-chip interconnect
Date: Thu, 31 Mar 2011 12:41:16 -0000	[thread overview]
Message-ID: <op.vs7j6jkw3ri7v4@arend-laptop> (raw)

On Wednesday 30 March 2011 20:08:57 +0100 Russell King - ARM Linux wrote:
> I think you're going to be waiting a very long time for that to happen.
> No SoC vendor adds device IDs to their on-chip devices to allow them to
> be automatically discovered - it's only through ARM Ltd's development of
> their Primecells, and then vendors integrating those into their SoC  
> (maybe
> with their own modifications) that we've started to see this kind of ID
> system appearing.

Actually, Broadcom does. ARM delivers the DMP plugin. This adds additional  
register space with each core and each core is identified with a vendor id  
(maintained by JEDEC to assure it is unique), a core id, and a core class.  
Another used interconnect is SSB which also offers discovery functionality.

> Outside of the Primecell stuff, I'm unaware of anyone adding any kind
> of discovery mechanism to SoC based devices.

Not sure either.

Gr. AvS
-- 
"The most merciful thing in the world, I think, is the inability of the  
human
mind to correlate all its contents." - "The Call of Cthulhu"

             reply	other threads:[~2011-03-31 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 12:41 Arend van Spriel [this message]
     [not found] <1301391619-4499-1-git-send-email-arend@broadcom.com>
     [not found] ` <20110329181947.GA18134@flint.arm.linux.org.uk>
2011-03-30 13:09   ` [PATCH 0/1] new module for amba axi on-chip interconnect Arnd Bergmann
2011-03-30 17:40     ` Russell King - ARM Linux
2011-03-30 18:24       ` Arnd Bergmann
2011-03-30 19:08         ` Russell King - ARM Linux
2011-04-01 15:40           ` Arnd Bergmann

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=op.vs7j6jkw3ri7v4@arend-laptop \
    --to=arend@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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