Re: [Ocf-linux-users] OCF for Marvell Kirkwood; probe function not called; does not init CESA

[David M. <dav...@mc...>]

Jivin ana...@wi... lays it down ...
> Hi David,
> 
> I'm using 2.6.31.8 kernel on Marvell Prestera platform.
> 
> The machine architecture chosen for the platform in /arch/arm is
> mach-feroceon-kw (/arch/arm/mach-feroceon-kw). I suppose this was
> provided by Marvell. Like in /arch/arm/Kirkwood/common.c where
> "mv_crypto" device is defined and registered, it is not done for
> mach-feroceon-kw. I copied the mv_crypto device from Kirkwood (not the
> best thing to do) and installed the mv_cesa.ko and mv_cesa_ocf_init()
> was called but also crashed. Have to figure out the correct device
> registers, sram and IRQ now.

Sounds like you are making progress.  Once you get the correct parameters in
there you should be looking much better :-)

Cheers,
Davidm


> -----Original Message-----
> From: David McCullough [mailto:dav...@mc...] 
> Sent: Wednesday, October 26, 2011 6:57 AM
> To: Anantharam V (WT01 - GMT-Telecom Equipment)
> Cc: ocf...@li...
> Subject: Re: [Ocf-linux-users] OCF for Marvell Kirkwood; probe function
> not called; does not init CESA
> 
> 
> Jivin ana...@wi... lays it down ...
> > Hi,
> > 
> > I'm trying to use OCF for Marvell's CESA. I have built ocf.ko,
> cryptodev.ko and mv_cesa.ko. I've used insmod to load them and all the
> loading works fine except for mv_cesa.ko. The function
> mv_cesa_ocf_init() does not get called. In the following code from OCF
> kirkwood's cesa_ocf_drv.c,
> > 
> > static struct platform_driver marvell_cesa = {
> >     .probe        = mv_cesa_ocf_init,
> >     .remove        = mv_cesa_ocf_exit,
> >     .driver        = {
> >         .owner    = THIS_MODULE,
> >         .name    = "mv_crypto",
> >     },
> > };
> > 
> > MODULE_ALIAS("platform:mv_crypto");
> > 
> > static int __init mv_cesa_init(void)
> > {
> >     return platform_driver_register(&marvell_cesa);
> > }
> > 
> > module_init(mv_cesa_init);
> > 
> > With insmod, the mv_cesa_init() is called but the debug in
> mv_cesa_ocf_init() is not printed. Is platform_driver_register()
> internally supposed to call the .probe function? Or when is the probe
> function supposed to be called? What can be done to call the probe
> function of marvell_cesa?
> 
> I am not sure,  what kernel version are you using and what platform are
> you
> building for ?
> 
> Have you created a custom platform of your own ?
> 
> I had a look at our marvel based platform where I know this was working
> (haven't used it for quite a while) and it all looks similar.
> 
> You may just need to work though the platform driver code until you
> figure
> out why it isn't called :-(
> 
> Cheers,
> Davidm
> 
> -- 
> David McCullough,      dav...@mc...,  Ph:+61 734352815
> McAfee - SnapGear      http://www.mcafee.com
> http://www.uCdot.org
> 
> Please do not print this email unless it is absolutely necessary. 
> 
> The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 
> 
> WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 
> 
> www.wipro.com
> 
> 

-- 
David McCullough,      dav...@mc...,  Ph:+61 734352815
McAfee - SnapGear      http://www.mcafee.com         http://www.uCdot.org