From: Tony Lindgren <tony@atomide.com>
To: Adam Ford <aford173@gmail.com>
Cc: Tero Kristo <t-kristo@ti.com>, Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: OMAP36 AES and SHA addresses and hwmods
Date: Tue, 5 May 2020 08:43:33 -0700 [thread overview]
Message-ID: <20200505154333.GL37466@atomide.com> (raw)
In-Reply-To: <CAHCN7xJKhtsTBnY6HS=M_TdpJuSvkCzy8yRVijE73rkUrx7p=Q@mail.gmail.com>
* Adam Ford <aford173@gmail.com> [200504 23:07]:
> I wasn't seeing both clocks, but I was able to migrate the AES from
> hwmods by referencing aes2_ick and aes1_ick.
Oh OK good to hear you got it working.
> [ 8.002349] omap-aes 480a6000.aes1: OMAP AES hw accel rev: 2.6
> [ 8.066375] omap-aes 480a6000.aes1: will run requests pump with
> realtime priority
> [ 8.425506] omap-aes 480c5000.aes2: OMAP AES hw accel rev: 2.6
> [ 8.492614] omap-aes 480c5000.aes2: will run requests pump with
> realtime priority
>
> Feel free to reject if you think I missed something. I will admit
> that I am not fully understanding the migration path, but I used the
> RNG stuff you did to help.
OK I'll check and see if it may need to be also blocked for
n900 and other HS SoCs.
> If / when this gets accepted, I'll do the same for the SHA engine, but
> I wanted to start with one first, before moving on.
>
> Tony - Is there value in doing the migration to other areas (like GPIO) as well?
Sure, for most types of devices we already have examples so they
can be updated whenever suitable.
Regards,
Tony
prev parent reply other threads:[~2020-05-05 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 15:48 OMAP36 AES and SHA addresses and hwmods Adam Ford
2020-05-04 6:28 ` Tero Kristo
2020-05-04 15:06 ` Tony Lindgren
2020-05-04 23:06 ` Adam Ford
2020-05-05 15:43 ` Tony Lindgren [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=20200505154333.GL37466@atomide.com \
--to=tony@atomide.com \
--cc=aford173@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=t-kristo@ti.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.