public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Ley Foon Tan <lftan@altera.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	Rob Landley <rob@landley.net>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers/misc: Add Altera System ID driver
Date: Mon, 4 Mar 2013 12:55:41 +0000	[thread overview]
Message-ID: <201303041255.42142.arnd@arndb.de> (raw)
In-Reply-To: <1362390111.3066.11.camel@leyfoon-vm>

On Monday 04 March 2013, Ley Foon Tan wrote:
> This IP core is not in the SoC. This core is in the FPGA and can be
> accessed by the Nios II processor or accessed by SOCFPGA processor (ARM
> based) via its interface to FPGA. Due to this, I think it shouldn't use
> infrastructure in drivers/base/soc.c.
> What do you think?

The sysid component gives a version for the entire FPGA part and all
components inside it, right?

I think you should use the drivers/base/soc.c interface to describe the
SOCFPGA SoC components as well as the actual FPGA. You basically
end up having one device node that acts as the parent for the SoC
components, and a way to retrieve version information about it.

Depending on how it fits the actual hardware layout more closely,
you could have one node as the parent for all devices, or the
FPGA SoC node as a child of the main one, or two SoC nodes side by
side from the top-level.

	Arnd

  reply	other threads:[~2013-03-04 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  3:11 [PATCH 1/1] drivers/misc: Add Altera System ID driver Ley Foon Tan
2013-03-04  3:32 ` Arnd Bergmann
2013-03-04  3:44   ` Greg Kroah-Hartman
2013-03-04  9:41     ` Ley Foon Tan
2013-03-04 12:55       ` Arnd Bergmann [this message]
2013-03-05 11:12         ` Ley Foon Tan
2013-03-05 21:59           ` Arnd Bergmann
2013-03-08 10:41             ` Ley Foon Tan

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=201303041255.42142.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=lftan@altera.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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