From: "Pali Rohár" <pali.rohar@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Tony Lindgren <tony@atomide.com>, Nishanth Menon <nm@ti.com>,
Felipe Balbi <balbi@ti.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Sebastian Reichel <sre@kernel.org>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: Nokia N900: omap aes is broken
Date: Wed, 25 Feb 2015 11:18:22 +0100 [thread overview]
Message-ID: <201502251118.22991@pali> (raw)
In-Reply-To: <20150225095000.GB24627@amd>
[-- Attachment #1: Type: Text/Plain, Size: 2018 bytes --]
On Wednesday 25 February 2015 10:50:00 Pavel Machek wrote:
> On Tue 2015-02-24 09:37:34, Tony Lindgren wrote:
> > * Pali Rohár <pali.rohar@gmail.com> [150224 09:42]:
> > > On Tuesday 24 February 2015 18:25:12 Tony Lindgren wrote:
> > > > * Pali Rohár <pali.rohar@gmail.com> [150218 16:03]:
> > > > > --- a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
> > > > > +++ b/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
> > > > > @@ -3938,8 +3938,9 @@ int __init
> > > > > omap3xxx_hwmod_init(void)
> > > > >
> > > > > if (r < 0)
> > > > >
> > > > > return r;
> > > > >
> > > > > - /* Register GP-only hwmod links. */
> > > > > - if (h_gp && omap_type() == OMAP2_DEVICE_TYPE_GP) {
> > > > > +// /* Register GP-only hwmod links. */
> > > > > +// if (h_gp && omap_type() == OMAP2_DEVICE_TYPE_GP) {
> > > > > + if (h_gp) {
> > > > >
> > > > > r = omap_hwmod_register_links(h_gp);
> > > > > if (r < 0)
> > > > >
> > > > > return r;
> > > > >
> > > > > aes hwmod is defined in GP-only hwmod...
> > > >
> > > > Doesn't this depend on the bootloader version of n900 to
> > > > work?
> > > >
> > > > Regards,
> > > >
> > > > Tony
> > >
> > > Ok, it looks like second patch (omap_hwmod_3xxx_data.c)
> > > needs that aes-enabled bootloader.
> >
> > OK we need some runtime detection somehow for what's
> > enabled..
> >
> > > But first patch (omap3.dtsi) is needed for proper
> > > definitions. Otherwise omap-aes driver will never work on
> > > DT systems.
> >
> > Yeah that one makes sense to me, I guess you'll do a proper
> > fix for that one.
>
> If this depends on bootloader... would command line parameter
> be right solution here?
> Pavel
Problem is that we need to disable AES in:
* DT file
* hwmod source code
* ... and maybe on other places too ...
So I think it make sense to check if AES is disabled in DT and
add this check to other parts of kernel source code where needed.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-02-25 10:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 12:21 Nokia N900: omap aes is broken Pali Rohár
2015-02-18 21:02 ` Pali Rohár
2015-02-18 21:27 ` Pali Rohár
2015-02-24 17:25 ` Tony Lindgren
2015-02-24 17:25 ` Tony Lindgren
2015-02-24 17:38 ` Pali Rohár
2015-02-24 17:37 ` Tony Lindgren
2015-02-24 17:37 ` Tony Lindgren
2015-02-24 17:49 ` Pali Rohár
2015-02-24 17:50 ` Tony Lindgren
2015-02-25 9:50 ` Pavel Machek
2015-02-25 10:18 ` Pali Rohár [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=201502251118.22991@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.