[Ksummit-2013-discuss] [ARM ATTEND] Describing complex, non-probable system topologies
tony at atomide.com
Mon Aug 5 03:37:30 EDT 2013
* Greg KH <greg at kroah.com> [130805 00:16]:
> On Sun, Aug 04, 2013 at 11:55:35PM -0700, Tony Lindgren wrote:
> > But for things that are completely bus specific for various SoCs, how
> > would you like to handle those?
> > For example, we are currently using platform bus and bus notifiers and
> > then the runtime PM calls from device driver trigger the bus specific
> > things.
> > Would you prefer to instead use a custom bus instead of extending
> > the platform bus for things like that?
> Yes I would. I would really like to only use the platform bus for very
> few things, if any at all.
OK. How would you prefer to set up things from driver point of view
so the device drivers don't need to care which bus it's connected to?
That is, for the let's say 10 - 15 slightly different types of busses
that are currently handled as platform bus?
Should we have some generic replacement for struct platform_driver
that can bind to let's say SoC specific bus implementation?
More information about the linux-arm-kernel