From: Peter De Schrijver <pdeschrijver@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Russell King <linux@arm.linux.org.uk>,
Stephen Warren <swarren@wwwdotorg.org>,
Thierry Reding <thierry.reding@gmail.com>,
Danny Huang <dahuang@nvidia.com>,
"Prashant Gaikwad" <pgaikwad@nvidia.com>
Subject: Re: [PATCH 4/6] ARM: tegra: rework fuse.c
Date: Thu, 2 Jan 2014 16:32:21 +0200 [thread overview]
Message-ID: <20140102143221.GR26588@tbergstrom-lnx.Nvidia.com> (raw)
In-Reply-To: <CACRpkdbXc_yH-=WgpQyVwHC_TSPfbfx=tHwziNhmB6t0HuSfRw@mail.gmail.com>
On Thu, Jan 02, 2014 at 01:37:43PM +0100, Linus Walleij wrote:
> On Thu, Dec 19, 2013 at 4:54 PM, Peter De Schrijver
> <pdeschrijver@nvidia.com> wrote:
>
> > Reduce fuse.c to the minimum functionality required for the early bootstages.
> > Also export tegra_read_straps() for use by the fuse driver.
> >
> > Signed-off-by: Peter De Schrijver <pdeschrijver@nvidia.com>
>
> Aha, but why?
>
The efuse driver in patch 2 of this series, adds the randomness, so we don't
need to add it here then?
> > -static void __init tegra20_fuse_init_randomness(void)
> > -{
> > - u32 randomness[2];
> > -
> > - randomness[0] = tegra_fuse_readl(FUSE_UID_LOW);
> > - randomness[1] = tegra_fuse_readl(FUSE_UID_HIGH);
> > -
> > - add_device_randomness(randomness, sizeof(randomness));
> > -}
> > -
> > -/* Applies to Tegra30 or later */
> > -static void __init tegra30_fuse_init_randomness(void)
> > -{
> > - u32 randomness[7];
> > -
> > - randomness[0] = tegra_fuse_readl(FUSE_VENDOR_CODE);
> > - randomness[1] = tegra_fuse_readl(FUSE_FAB_CODE);
> > - randomness[2] = tegra_fuse_readl(FUSE_LOT_CODE_0);
> > - randomness[3] = tegra_fuse_readl(FUSE_LOT_CODE_1);
> > - randomness[4] = tegra_fuse_readl(FUSE_WAFER_ID);
> > - randomness[5] = tegra_fuse_readl(FUSE_X_COORDINATE);
> > - randomness[6] = tegra_fuse_readl(FUSE_Y_COORDINATE);
> > -
> > - add_device_randomness(randomness, sizeof(randomness));
> > -}
>
> We still want to get this into the random pool right? Can it not simply
> be moved to a later initcall then?
Yes, it's done in the efuse driver now, do you think that's too late?
Cheers,
Peter.
next prev parent reply other threads:[~2014-01-02 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 15:54 [PATCH 0/6] efuse driver for Tegra Peter De Schrijver
2013-12-19 15:54 ` [PATCH 1/6] ARM: tegra: export apb dma readl/writel Peter De Schrijver
2013-12-19 15:54 ` [PATCH 2/6] misc: fuse: Add efuse driver for Tegra Peter De Schrijver
2013-12-19 17:59 ` Greg KH
2013-12-19 19:20 ` Stephen Warren
2013-12-19 19:43 ` Greg KH
2013-12-19 15:54 ` [PATCH 3/6] ARM: tegra: Add efuse bindings Peter De Schrijver
2013-12-19 15:54 ` [PATCH 4/6] ARM: tegra: rework fuse.c Peter De Schrijver
2014-01-02 12:37 ` Linus Walleij
2014-01-02 14:32 ` Peter De Schrijver [this message]
2014-01-02 17:03 ` Linus Walleij
2013-12-19 15:54 ` [PATCH 5/6] ARM: Tegra: remove speedo files Peter De Schrijver
2013-12-19 15:54 ` [PATCH 6/6] misc: enable fuse drivers Peter De Schrijver
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=20140102143221.GR26588@tbergstrom-lnx.Nvidia.com \
--to=pdeschrijver@nvidia.com \
--cc=dahuang@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pgaikwad@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
/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