On Thu, 11 Jun 2009, arm-kernel@xxxxxxxxxxxxxxxx wrote: > From: Sebastian Andrzej Siewior <sebastian@xxxxxxxxxxxxx> > > use the new driver for the crypto engine > > Signed-off-by: Sebastian Andrzej Siewior <sebastian@xxxxxxxxxxxxx> Since the crypto engine is part of the SOC, this is not a board specific thing. Hence this should be initialized for all targets and not only the TS209, just like the watchdog driver is. > --- > arch/arm/mach-orion5x/ts209-setup.c | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/arch/arm/mach-orion5x/ts209-setup.c b/arch/arm/mach-orion5x/ts209-setup.c > index 9d68905..fbea307 100644 > --- a/arch/arm/mach-orion5x/ts209-setup.c > +++ b/arch/arm/mach-orion5x/ts209-setup.c > @@ -302,6 +302,7 @@ static void __init qnap_ts209_init(void) > orion5x_uart0_init(); > orion5x_uart1_init(); > orion5x_xor_init(); > + orion5x_crypto_init(); > > platform_device_register(&qnap_ts209_button_device); > > -- > 1.6.0.6 > -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
