* Rong Chen [200630 00:31]:
>
>
> On 6/30/20 2:12 AM, Tony Lindgren wrote:
> > * kernel test robot [200617 17:28]:
> > > Hi Adam,
> > >
> > > Thank you for the patch! Yet something to improve:
> > >
> > > [auto build test ERROR on omap/for-next]
> > > [cannot apply to balbi-usb/testing/next]
On 6/30/20 2:12 AM, Tony Lindgren wrote:
* kernel test robot [200617 17:28]:
Hi Adam,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on omap/for-next]
[cannot apply to balbi-usb/testing/next]
[if your patch is applied to the wrong git tree, please drop us a note
* kernel test robot [200617 17:28]:
> Hi Adam,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on omap/for-next]
> [cannot apply to balbi-usb/testing/next]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system.
Hi Adam,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on omap/for-next]
[cannot apply to balbi-usb/testing/next]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify
Various OMAP3 boards have two AES blocks, but only one is currently
available, because the hwmods are only configured for one.
This patch migrates the hwmods for the AES engine to sysc-omap2
which allows the second AES crypto engine to become available.
omap-aes 480a6000.aes1: OMAP AES hw
* Adam Ford [200613 11:11]:
> Through trial and error, I think I have the right IRQ for OMAP3630 for
> the 2nd instance.
OK great.
> > > I assume the second engine uses different interrupts. I don't suppose
> > > anyone know what it should be?
> >
> > Sorry no idea, usually the secure
On Tue, May 5, 2020 at 6:34 PM Tony Lindgren wrote:
>
> * Adam Ford [200505 21:18]:
> > On Tue, May 5, 2020 at 1:42 PM Tony Lindgren wrote:
> > >
> > > * Adam Ford [200504 16:02]:
> > > > Various OMAP3 boards have two AES blocks, but only one is currently
> > > > available, because the hwmods
* Adam Ford [200505 21:18]:
> On Tue, May 5, 2020 at 1:42 PM Tony Lindgren wrote:
> >
> > * Adam Ford [200504 16:02]:
> > > Various OMAP3 boards have two AES blocks, but only one is currently
> > > available, because the hwmods are only configured for one.
> > >
> > > This patch migrates the
On Tue, May 5, 2020 at 1:42 PM Tony Lindgren wrote:
>
> * Adam Ford [200504 16:02]:
> > Various OMAP3 boards have two AES blocks, but only one is currently
> > available, because the hwmods are only configured for one.
> >
> > This patch migrates the hwmods for the AES engine to sysc-omap2
> >
* Adam Ford [200504 16:02]:
> Various OMAP3 boards have two AES blocks, but only one is currently
> available, because the hwmods are only configured for one.
>
> This patch migrates the hwmods for the AES engine to sysc-omap2
> which allows the second AES crypto engine to become available.
>
>
Various OMAP3 boards have two AES blocks, but only one is currently
available, because the hwmods are only configured for one.
This patch migrates the hwmods for the AES engine to sysc-omap2
which allows the second AES crypto engine to become available.
omap-aes 480a6000.aes1: OMAP AES hw
11 matches
Mail list logo
