On Sat, Apr 11, 2015 at 01:41:34PM +0530, Sudip Mukherjee wrote: > On Sat, Apr 11, 2015 at 09:27:16AM +0200, Greg KH wrote: > > On Sat, Apr 11, 2015 at 10:56:51AM +0530, Sudip Mukherjee wrote: > well, as of now one question. I am planning like this : > > sys > _______________|_____________ > | | | | | > bus > ________|______ > | > parport > _______|_____ > | | > devices drivers- lp, ppdev, panel etc.. > _____|________ > | | > parport0 parport1 > > > I can understand that drivers need to be binded to one device, so > suppose ppdev wants to use parport0, how that binding will be done? > do i need mark the driver in the parport->ddev.driver ? > I think that should have been automatically done if i have a probe > function for the bus... > somehow I am missing this step in the other drivers codes.
i think i got the missing link, let me try first. regards sudip -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
