On 12/30/2014 02:54 AM, Ash Charles wrote: > Hello, > > I'm trying to get add support for a wl18xx wireless device to my > omap3-based board running a 3.2 kernel. Using backports (package, not > direct integration), I can compile the required drivers and load them > onto my system. The driver needs some platform-specific data to > control the wireless device. Normally, I'd pass this as platform data > from a board file (I'm not using device tree on this 3.2 kernel) but > as the required structures come from the backport, I can't. How can I > provide this data to the module? > > Things that come to mind but don't seem quite right: > 1. Hard-code this setup data into the driver for my particular board > (seem a little heavy-handed) > 2. Add a backport to support a board file/pdata-quirks. (nothing else > in the arch tree is backported...seems to indicate this is not the > right way) > 3. Use the backports with direct integration as I think I could just > make the changes to the board file directly in this case (I'm using a > TI backport tree that doesn't support integration yet) > 4. Add a device tree blob or some shim such that the target kernel can > provide the module the data. > > Many thanks in advance for any advice or insight. You could remove the platform data header file from backports and use the one from your kernel, just delete the header file in backports. If this version does not have all the needed members just copy the header file from backpots into your kernel. Then you can register the device like any other device in your board file and fill the platform data with the needed data. Hauke -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
