On Thu, 2010-07-08 at 12:37 +0200, Sean Kelvin Preston wrote: > Hi Philby > > > You are right, the platform_match() does not succeed based on a simple > > string comparison. platform_match() defined in platform.c drivers/base, > > does a string comparison of the driver and device name variable. If there > is a > > name mismatch platform_match() bails out and the probe fails. > > > > Try setting the ".name" variable in your platform driver and device to be > the > > same. > > The names are the same as I have not changed that code at all. As I was > just testing the new NAND I did not change the drivers except to add an > additional ID to the drivers/mtd/nand/nand_ids.c file. Otherwise I just > replaced the actual chip on the EVM board. This is why I was wondering if > there was something else going on when the platform_probe is done or maybe > before that which is failing because I need to change or add something > elsewhere to identify the new chip. >
Okay, then how about here, where a check is first done to see if there is a match between the device and driver id if (drv->bus->match && !drv->bus->match(dev, drv)) Regards, Philby _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
