Andrew de Quincey writes: > > > I am doing it using the normal kernel I2C driver. > > Every I2C frontend automatically calls the I2C driver attach callback > > where the card driver can configure it accordingly. > > The frontend driver does not really need to know anything about higher > > level structures. > > Are you meaning in the case where multiple manufacturers have used the same > frontend, that the manufacturer-hardware-specific card driver should do bits > of the frontend setup?
Yes, it can tell the driver specifics about the frontend (exactly what type, other inversion, etc.) or perform other necessary initialisations of hardware connected to the frontend. > Yeah, that does seem more appropriate actually, just a bit different from how > its done right now. Anyway, it was just an idea for how to support it if the > situation arises. When/if it does, it can be sorted then. > > I assume you prefer the callback function to load firmware in dvb_adapter > method in that case. Actually, firmware loading is a little different. It always has to be done once the frontend is identified no matter which card the frontend is on. So, each callback would do almost the same and a lot of code would be copied. Somehow passing "struct driver" would probably be easier in this case. Shouldn't a frontend driver (or rather each I2C driver) even get its own "struct driver"? I'll do some digging in the 2.6.x code. Ralph -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
