Re: OMAP36 AES and SHA addresses and hwmods

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Adam Ford <aford173@xxxxxxxxx> [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



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux