public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ley Foon Tan <lftan@altera.com>
To: Arnd Bergmann <arnd@arndb.de>
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: Fri, 8 Mar 2013 18:41:19 +0800	[thread overview]
Message-ID: <1362739279.2201.3.camel@leyfoon-vm> (raw)
In-Reply-To: <201303052159.36531.arnd@arndb.de>

On Tue, 2013-03-05 at 21:59 +0000, Arnd Bergmann wrote:
> On Tuesday 05 March 2013, Ley Foon Tan wrote:
> > The sysid give the unique system ID and system generation timestamp of
> > the system.
> > 
> > CASE 1:
> > SOCFPGA SoC + Sysid component in FPGA
> > 
> > CASE 2
> > Nios II soft core CPU + Sysid  (All in FPGA and no SoC is involved)
> > 
> > From example use cases above, Case 2 doesn't involve SoC component. 
> > To support both cases, do you think drivers/base/soc.c is still
> > suitable?
> 
> Yes, I think so. I would consider the second case still a SoC, because
> you have a single chip that contains the CPU and peripherals. From
> the OS point of view, it does not matter that they are in an FPGA.
> 
> 	Arnd

Thanks for your input. I will go with your suggestion.

LFTan



      reply	other threads:[~2013-03-08 10:41 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
2013-03-05 11:12         ` Ley Foon Tan
2013-03-05 21:59           ` Arnd Bergmann
2013-03-08 10:41             ` Ley Foon Tan [this message]

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=1362739279.2201.3.camel@leyfoon-vm \
    --to=lftan@altera.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --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