Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: mpm@selenic.com
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
	linux-kernel@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH] TXx9: Add TX4939 RNG support
Date: Mon, 01 Jun 2009 01:57:55 +0900 (JST)	[thread overview]
Message-ID: <20090601.015755.21367568.anemo@mba.ocn.ne.jp> (raw)
In-Reply-To: <1243350141-883-2-git-send-email-anemo@mba.ocn.ne.jp> <1243642882.8020.9.camel@calx>

: This is a reply for comments from Matt Mackall via mm-commit mail.

On Fri, 29 May 2009 19:21:22 -0500, Matt Mackall <mpm@selenic.com> wrote:
> > +++ a/arch/mips/txx9/generic/setup_tx4939.c
> > @@ -494,6 +494,24 @@ void __init tx4939_aclc_init(void)
> >  			       TXX9_IRQ_BASE + TX4939_IR_ACLC, 1, 0, 1);
> >  }
> >  
> > +#define TX4939_RNG_REG	((TX4939_CRYPTO_REG & 0xfffffffffULL) + 0xb0)
> 
> This isn't the best place for this define?

Well, I can move it to include/asm/txx9/tx4939.h.

> > +++ a/arch/mips/txx9/rbtx4939/setup.c
> > @@ -501,6 +501,7 @@ static void __init rbtx4939_device_init(
> >  	tx4939_dmac_init(0, 2);
> >  	tx4939_aclc_init();
> >  	platform_device_register_simple("txx9aclc-generic", -1, NULL, 0);
> > +	tx4939_rng_init();
> >  }
> >  
> >  static void __init rbtx4939_setup(void)
> 
> Not clear to me how this works when this is a module?

This patch add a registration of a platform device for RNG to vmlinux.
And the other patch add a driver module for the RNG.  This strategy is
fairly common for SoCs or embedded platforms.

---
Atsushi Nemoto

  parent reply	other threads:[~2009-05-31 16:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 15:02 [PATCH] TXx9: Add TX4939 RNG support Atsushi Nemoto
     [not found] ` <1243642882.8020.9.camel@calx>
2009-05-31 16:57   ` Atsushi Nemoto [this message]
2009-05-31 17:01     ` Matt Mackall
2009-05-31 17:23       ` Atsushi Nemoto
2009-05-31 17:32         ` Matt Mackall
2009-06-02 14:13           ` Atsushi Nemoto

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=20090601.015755.21367568.anemo@mba.ocn.ne.jp \
    --to=anemo@mba.ocn.ne.jp \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mpm@selenic.com \
    --cc=ralf@linux-mips.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