public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: hwrng: picoxcell: PICOXCELL_PC3X3?
Date: Wed, 15 May 2013 10:51:11 +0100	[thread overview]
Message-ID: <20130515095111.GB16346@page> (raw)
In-Reply-To: <1368568977.1350.142.camel@x61.thuisdomein>

Hi Paul,

On Wed, May 15, 2013 at 12:02:57AM +0200, Paul Bolle wrote:
> 0) Support for "Picochip picoXcell true random number generator[s]" was
> added in commit 5efb94ee14 ("hwrng: pixocell - add support for picoxcell
> TRNG"). Its Kconfig symbol (HW_RANDOM_PICOXCELL) depends on
> PICOXCELL_PC3X3. But that symbol is not included in mainline. I found no
> trace of it ever since support for this TRNG got added in v2.6.39. This
> means this code has never been buildable in mainline.
> 
> Why does this code depend on PICOXCELL_PC3X3?

The driver went in before the machine support itself, which got reworked 
for device tree.  There's still some work needed to make the clocks work 
properly so that the driver can use them (they're currently maintained 
out of tree by Mindspeed, Picochip's new owner).

> 1) Slightly related: by what magic are picoxcell-pc7302-pc3x3.dts and
> picoxcell-pc3x3.dtsi hooked into the build system? Or are dts and dtsi
> files, well, special and not directly linked into the build system?

There isn't a defconfig at the moment - I've just done my dts builds 
manually.

Jamie

      reply	other threads:[~2013-05-15  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 22:02 hwrng: picoxcell: PICOXCELL_PC3X3? Paul Bolle
2013-05-15  9:51 ` Jamie Iles [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=20130515095111.GB16346@page \
    --to=jamie@jamieiles.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